Make A Graph

Dataset Title:	Fluorometry data from a Turner Designs C3 sensor at OBSEA's Besos Buoy (30min average)
Institution:	Universitat Politècnica de Catalunya (Dataset ID: OBSEA_Besos_Buoy_C3_fluorometer_30min)
Range:	time = 2022-08-02T10:30:00Z to 2024-05-16T12:00:00Z
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.6594362e+9, 1.7158608e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date/Time";
    String source_name "Date/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";
  }
  TEMP {
    Float64 actual_range 12.2, 29.9;
    String long_name "sea_water_temperature";
    String sdn_parameter "https://vocab.nerc.ac.uk/collection/P01/current/TEMPST01";
    String sdn_parameter_urn "SDN:P01::TEMPST01";
    String sdn_units "https://vocab.nerc.ac.uk/collection/P06/current/UPAA";
    String sdn_units_urn "SDN:P06::UPAA";
    String standard_name "sea_water_temperature";
    String units "degrees Celsius";
  }
  TEMP_qc {
    Int32 actual_range 1, 3;
    String long_name "TEMP quality control flag";
  }
  RFUL {
    Float64 actual_range 1.0, 199.4;
    String long_name "refined_fuels";
    String sdn_parameter "refined_fuels";
    String sdn_units "https://vocab.nerc.ac.uk/collection/P06/current/UPPM";
    String sdn_units_urn "SDN:P06::UPPM";
    String standard_name "refined_fuels";
    String units "parts per million";
  }
  RFUL_qc {
    Int32 actual_range 1, 1;
    String long_name "RFUL quality control flag";
  }
  COIL {
    Float64 actual_range 5.4, 989.4;
    String long_name "crude_oil";
    String sdn_parameter "crude_oil";
    String sdn_units "https://vocab.nerc.ac.uk/collection/P06/current/UPPB";
    String sdn_units_urn "SDN:P06::UPPB";
    String standard_name "crude_oil";
    String units "parts per billion";
  }
  COIL_qc {
    Int32 actual_range 1, 1;
    String long_name "COIL quality control flag";
  }
  CDOM {
    Float64 actual_range 0.0, 750.9;
    String long_name "coloured_dissolved_organic_matter_";
    String sdn_parameter "https://vocab.nerc.ac.uk/collection/P01/current/CDOMZZ01";
    String sdn_parameter_urn "SDN:P01::CDOMZZ01";
    String sdn_units "https://vocab.nerc.ac.uk/collection/P06/current/UPPB";
    String sdn_units_urn "SDN:P06::UPPB";
    String standard_name "coloured_dissolved_organic_matter_";
    String units "parts per billion";
  }
  CDOM_qc {
    Int32 actual_range 1, 3;
    String long_name "CDOM quality control flag";
  }
 }
  NC_GLOBAL {
    String area "NW Mediterranean Sea";
    String author "Enoc Martinez";
    String average_period "30min";
    String cdm_data_type "Other";
    String contact "enoc.martinez@upc.edu";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String geospatial_lat_max "41.18212";
    String geospatial_lat_min "41.18212";
    String geospatial_lon_max "1.75257";
    String geospatial_lon_min "1.75257";
    String history 
"2024-11-10T19:46:51Z (local files)
2024-11-10T19:46:51Z https://data.obsea.es/tabledap/OBSEA_Besos_Buoy_C3_fluorometer_30min.das";
    String infoUrl "https://www.obsea.es";
    String institution "Universitat Politècnica de Catalunya";
    String institution_edmo_code "2150";
    String institution_references "https://www.obsea.es";
    String instrument_model "C3";
    String license "Creative Commons Attribution 4.0 International (CC-BY-4.0)";
    String pi_name "Joaquín del Río";
    String platform_code "OBSEA_Besos_Buoy";
    String processing_level "data acquired from sensor, quality control procedure applied following QARTOD guidelines, data averaged in periods of 30min";
    String quality_control_flags "1:good data, 2:QC not applied, 3:suspicious data, 4:bad data, 9:missing data";
    String quality_control_methods "QARTOD, https://ioos.noaa.gov/project/qartod";
    String sdn_instrument_type "SDN:L05::113";
    String sensor_depth "1";
    String site_code "OBSEA_Besos_Buoy";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Data collected by a Turner Designs C3 fluorometer mounted at the Besos Buoy, on top of the OBSEA observatory, 30min average";
    String testOutOfDate "now-1day";
    String time_coverage_end "2024-05-16T12:00:00Z";
    String time_coverage_start "2022-08-02T10:30:00Z";
    String title "Fluorometry data from a Turner Designs C3 sensor at OBSEA's Besos Buoy (30min average)";
  }
}

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