Make A Graph

Dataset Title:	NAUTILOS - Microplastic Detector for yellow fluorescent microplastic particles - CSEM
Institution:	CSEM (Dataset ID: sunamips_detector_yellow_fluorescence_csem)
Range:	time = 2025-01-30T14:37:40Z to 2025-01-30T14:37:40Z
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

Constraints	Optional Constraint #1		Optional Constraint #2

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

Y Axis Minimum:

Maximum:

(Please be patient. It may take a while to get the data.)

Optional:
Then set the File Type: (File Type information)
and

or view the URL:
(Documentation / Bypass this form

)

Time range:

[The graph you specified. Please be patient.]

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.73824786e+9, 1.73824786e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Measurement_Date {
    String long_name "Measurement Date";
  }
  Measurement_Time {
    String long_name "Measurement Time";
  }
  Measurement_Duration {
    String long_name "Measurement Duration";
  }
  Particles {
    String long_name "Particles";
  }
  Sample_Concentration {
    String long_name "Sample Concentration";
  }
  Sample_Volume {
    String long_name "Sample Volume";
  }
  Flow_Rate {
    String long_name "Flow Rate";
  }
  Laser_Power {
    String long_name "Laser Power";
  }
  event {
    Int16 _FillValue 32767;
    Int16 actual_range 1, 3239;
    String description "consecutive number of event";
    String long_name "Event";
  }
  Channel_1_width {
    Float64 actual_range 13.949407, 100.34812;
    String description "extracted width of the identified peak in the units of \"number of samples\" from channel 1";
    String long_name "Channel 1 Width";
    String units "number of samples";
  }
  Channel_1_height {
    Float64 actual_range 80.0877, 307.44873;
    String description "extracted height of the identified peak in the units of \"ADC resolution/range\" from channel 1";
    String long_name "Channel 1 Height";
    String units "ADC resolution/range";
  }
  Channel_2_width {
    Float64 actual_range 12.814142, 97.76122;
    String description "extracted width of the identified peak in the units of \"number of samples\" from channel 2";
    String long_name "Channel 2 Width";
    String units "number of samples";
  }
  Channel_2_height {
    Float64 actual_range 63.126442, 352.37747;
    String description "extracted height of the identified peak in the units of \"ADC resolution/range\" from channel 2";
    String long_name "Channel 2 Height";
    String units "ADC resolution/range";
  }
  Channel_3_width {
    Float64 actual_range 14.046274, 112.982414;
    String description "extracted width of the identified peak in the units of \"number of samples\" from channel 3";
    String long_name "Channel 3 Width";
    String units "number of samples";
  }
  Channel_3_height {
    Float64 actual_range 272.0335, 3136.8438;
    String description "extracted height of the identified peak in the units of \"ADC resolution/range\" from channel 3";
    String long_name "Channel 3 Height";
    String units "ADC resolution/range";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String channel_filters "Green, Red Green";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String history 
"2025-05-10T01:37:27Z (local files)
2025-05-10T01:37:27Z https://data-nautilos-h2020.eu/tabledap/sunamips_detector_yellow_fluorescence_csem.das";
    String infoUrl "https://nautilos-h2020.eu/";
    String inspire "Oceanographic geographical features";
    String institution "CSEM";
    String institution_country "CH";
    String institution_edmo_code "6052";
    String license "CC-BY 4.0";
    String naming_authority "NAUTILOS";
    String project_code "NAUTILOS";
    String Project_DOI "https://doi.org/10.3030/101000825";
    String project_edmerp "13720";
    String project_id "101000825";
    String project_name "New Approach to Underwater Technologies for Innovative, Low-cost Ocean obServation";
    String project_statement "This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 101000825 (NAUTILOS). This output reflects only the author's view and the European Union cannot be held responsible for any use that may be made of the information contained therein";
    String sampling_frequence "5kHz";
    String sensor_nautilos "Microplastic Detector - CSEM";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Data from a local source.";
    String time_coverage_end "2025-01-30T14:37:40Z";
    String time_coverage_start "2025-01-30T14:37:40Z";
    String title "NAUTILOS - Microplastic Detector for yellow fluorescent microplastic particles - CSEM";
    String varaibles "event, identified peak width, identified peak height";
  }
}

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its selection constraints (external link)

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.

ERDDAP, Version 2.18
Disclaimers | Privacy Policy | Contact