EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in|?   
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  ARICE CRUISE Subscribe RSS
Institution:  ???   (Dataset ID: ARICE_CRUISE)
Range: longitude = -165.534 to 177.4368°E, latitude = -70.52964 to 81.19036°N, time = 2022-03-23T18:16:00Z to 2023-02-01T09:57:00Z
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 {
  cruise {
    String long_name "Cruise";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.64805936e+9, 1.67524542e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date";
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -70.52964, 81.19036;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value NaN;
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -165.534, 177.4368;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 missing_value NaN;
    String standard_name "longitude";
    String units "degrees_east";
  }
  timestamp {
    Float64 actual_range 1.649251784139e+9, 1.675252092764e+9;
    String comment "The values in this column are added by ERDDAP to identify when each row of data was added to the data file. NOTE! This is an unusual dataset in that the data files are actually log files. Normally, when you request data from this dataset, ERDDAP processes the insert (command=0) and delete (command=1) commands in the log files to return data from the current version of this dataset. However, if you make a request which includes &timestamp<= , then ERDDAP will return the dataset as it was at that point in time. Or, if you make a request which includes &timestamp> (or >= or =), e.g., &timestamp>0, then ERDDAP will return the raw data from the log files.";
    String ioos_category "Time";
    String long_name "Timestamp";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00.000Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  author {
    String comment "The values in this column identify the author who added each row of data to the dataset.";
    String ioos_category "Identifier";
    String long_name "Author";
  }
  command {
    String _Unsigned "false";
    Byte actual_range 0, 0;
    String comment "This is an unusual dataset in that the data files are actually log files. Normally, when you request data from this dataset, ERDDAP processes the insert (command=0) and delete (command=1) commands in the log files to return data from the current version of this dataset. However, if you make a request which includes &timestamp<= , then ERDDAP will return the dataset as it was at that point in time. Or, if you make a request which includes &timestamp> (or >= or =), e.g., &timestamp>0, then ERDDAP will return the raw data from the log files.";
    String flag_meanings "insert delete";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "Command";
    Byte missing_value 127;
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 177.4368;
    Float64 geospatial_lat_max 81.19036;
    Float64 geospatial_lat_min -70.52964;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 177.4368;
    Float64 geospatial_lon_min -165.534;
    String geospatial_lon_units "degrees_east";
    String history 
"2023-02-01T12:18:53Z (local files)
2023-02-01T12:18:53Z https://erddap.emodnet-physics.eu/tabledap/ARICE_CRUISE.das";
    String httpGetDirectoryStructure "cruise/1years";
    String httpGetRequiredVariables "cruise,time,latitude,longitude";
    String infoUrl "???";
    String institution "???";
    String keywords "author, command, cruise, identifier, latitude, local, longitude, source, time, timestamp";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    Float64 Northernmost_Northing 81.19036;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -70.52964;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "cruise";
    String summary "ARICE CRUISE";
    String testOutOfDate "now-1day";
    String time_coverage_end "2023-02-01T09:57:00Z";
    String time_coverage_start "2022-03-23T18:16:00Z";
    String title "ARICE CRUISE";
    Float64 Westernmost_Easting -165.534;
  }
}

 

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