BIOPOLIS ERDDAP
Easier access to scientific data
| ?    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Coupled Coastal Temperature and Biodiversity Observation Network (CCTBON),
Intertidal Rock Substrate Temperatures, Raw Data, 2020-present, Hourly
Subscribe RSS
Institution:  CIBIO/BIOPOLIS   (Dataset ID: cctbon_raw_hourly)
Range: longitude = -8.728272 to -8.728178°E, latitude = 41.26652 to 41.2666°N, time = 2022-11-08T10:00:01Z to 2024-01-11T08:00:16Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
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.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.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: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.667901601e+9, 1.704960016e+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";
  }
  temp {
    Float32 actual_range 9.4, 24.0;
    String ioos_category "Temperature";
    String long_name "Temperature";
  }
  serial_number {
    String ioos_category "Statistics";
    String long_name "Serial Number";
  }
  sensor_id {
    String ioos_category "Identifier";
    String long_name "Sensor Id";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 41.266522, 41.266602;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -8.728272, -8.728178;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  country {
    String ioos_category "Location";
    String long_name "Country";
  }
  location {
    String ioos_category "Location";
    String long_name "Location";
  }
  tide_level {
    String ioos_category "Sea Level";
    String long_name "Tide Level";
  }
  solar_exposure {
    String ioos_category "Unknown";
    String long_name "Solar Exposure";
  }
  replicate {
    String ioos_category "Unknown";
    String long_name "Replicate";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Citation "Citation";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String DOI "DOI";
    Float64 Easternmost_Easting -8.728178;
    String featureType "Point";
    Float64 geospatial_lat_max 41.266602;
    Float64 geospatial_lat_min 41.266522;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -8.728178;
    Float64 geospatial_lon_min -8.728272;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-19T07:23:05Z (local files)
2024-09-19T07:23:05Z http://localhost:8080/tabledap/cctbon_raw_hourly.das";
    String infoUrl "URL";
    String institution "CIBIO/BIOPOLIS";
    String keywords "temperature, temperature_in_water_column, time";
    String license "CC-BY 4.0";
    Float64 Northernmost_Northing 41.266602;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 41.266522;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "serial_number, sensor_id, latitude, longitude";
    String summary "Intertidal Rock Substrate Temperatures collected with static temperature logger with NFC technology in Citizen Scinece campaigns";
    String testOutOfDate "now-9days";
    String time_coverage_end "2024-01-11T08:00:16Z";
    String time_coverage_start "2022-11-08T10:00:01Z";
    String title "Coupled Coastal Temperature and Biodiversity Observation Network (CCTBON), Intertidal Rock Substrate Temperatures, Raw Data, 2020-present, Hourly";
    Float64 Westernmost_Easting -8.728272;
  }
}

 

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.

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.23
Disclaimers | Privacy Policy | Contact