IADC Italian Arctic Data Center ERDDAP
Easier access to scientific data
log in    
Brought to you by CNR-ISP IADC Portal    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CTD data set from mooring S1 @ 1000 m Subscribe RSS
Institution:  OGS - National Institute of Oceanography and Applied Geophysics   (Dataset ID: s1_ctd_timeseries_1)
Range: longitude = 13.9484 to 13.9484°E, latitude = 76.4381 to 76.4381°N, depth = 1003.0 to 1017.0m, time = 2014-06-09T06:30:00Z to 2021-03-10T11:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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 {
  station_id {
    String cf_role "timeseries_id";
    String long_name "Id of the station in the TimeSeries";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 13.9484, 13.9484;
    String axis "X";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Location";
    String long_name "longitude position of the station";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 76.4381, 76.4381;
    String axis "Y";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Location";
    String long_name "latitude position of the station";
    String standard_name "latitude";
    String units "degrees_north";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1003.0, 1017.0;
    String axis "Z";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Location";
    String long_name "vertical distance below the surface";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.4022954e+9, 1.615374e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date and time of the measurement";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Temperature {
    Float32 actual_range -0.9493, 2.8042;
    String coverage_content_type "physicalMeasurement";
    String long_name "Time series of sea water temperature at 1000 m nominal depth from mooring S1";
    String standard_name "sea water temperature";
    String units "degree_C";
  }
  sea_water_practical_salinity {
    Float32 actual_range 34.8687, 35.0043;
    String coverage_content_type "physicalMeasurement";
    String long_name "Time series of sea water salinity at 1000 m nominal depth from mooring S1";
    String standard_name "sea water practical salinity";
    String units "PSS-78";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id,latitude,longitude";
    String Conventions "Attribute Convention for Data Discovery 1-3; Ocean Data Standards - IOC V. 1, 2019";
    Float64 Easternmost_Easting 13.9484;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 76.4381;
    Float64 geospatial_lat_min 76.4381;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 13.9484;
    Float64 geospatial_lon_min 13.9484;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 1017.0;
    Float64 geospatial_vertical_min 1003.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-03-29T02:29:22Z (local files)
2024-03-29T02:29:22Z https://data.iadc.cnr.it/tabledap/s1_ctd_timeseries_1.das";
    String infoUrl "https://metadata.iadc.cnr.it/geonetwork/srv/api/records/2298c267-0e42-4bb8-8196-d2076fdf6d8e";
    String institution "OGS - National Institute of Oceanography and Applied Geophysics";
    String keywords "Marine Sediments, Ocean Temperature, Oceans, salinity, Salinity/density, Turbidity, Water Temperature";
    String keywords_vocabulary "Science Key Words Earth Science Ocean; Keyword Version: 9.1.5";
    String license "CC BY-NC: This license allows reusers to distribute, remix, adapt, and build upon the material in any medium or format for noncommercial purposes only, and only so long as attribution is given to the creator.";
    Float64 Northernmost_Northing 76.4381;
    String project "CTD data set from mooring S1 @ 1000 m";
    String project_URL "https://iadc.cnr.it";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 76.4381;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Timeseries recorded at the mooring S1, at nominal depth of 1000 m during different deployments. The scope of the measurements is to study the temporal variability of the thermohaline properties of the Norvegian Deep Water, and assosiated deep flow.";
    String time_coverage_end "2021-03-10T11:00:00Z";
    String time_coverage_start "2014-06-09T06:30:00Z";
    String title "CTD data set from mooring S1 @ 1000 m";
    Float64 Westernmost_Easting 13.9484;
  }
}

 

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