Brought to you by SLGO, the St. Lawrence regional association of CIOOS    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  Données de courants de surface du fleuve et de l'estuaire | Surface Currents
of the St. Lawrence River, Estuary
Subscribe RSS
Institution:  Fisheries and Oceans Canada   (Dataset ID: mpoStleCourants)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?     specify just 1 value →
    |< - >|
< <
latitude (degrees_north) ?
    +
    -
< slider >
longitude (degrees_east) ?
    +
    -
< slider >
 
Graph Settings
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:
[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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.7305956e+9, 1.7311968e+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 units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 46.0, 49.5;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -72.6, -68.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  u {
    String long_name "velocity Positive toward East";
    Float32 missing_value 99999.0;
    String units "m/s";
  }
  v {
    String long_name "velocity Positive toward North";
    Float32 missing_value 99999.0;
    String units "m/s";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String Conventions "CF-1.10, COARDS, ACDD-1.3";
    String description "Description text";
    Float64 Easternmost_Easting -68.0;
    Float64 geospatial_lat_max 49.5;
    Float64 geospatial_lat_min 46.0;
    Float64 geospatial_lat_resolution 0.0025017869907076485;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -68.0;
    Float64 geospatial_lon_min -72.6;
    Float64 geospatial_lon_resolution 0.004003481288076583;
    String geospatial_lon_units "degrees_east";
    String history 
"Created from .text file on 05/11/24
2024-11-05T16:34:16Z (local files)
2024-11-05T16:34:16Z https://erddap.ogsl.ca/griddap/mpoStleCourants.das";
    String infoUrl "https://ogsl.ca/";
    String institution "Fisheries and Oceans Canada";
    String institution_fr "Pêches et Océans Canada";
    String keywords "sea surface current velocity, u, v";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    Float64 Northernmost_Northing 49.5;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 46.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Surface current forecasts accessed through Fisheries and Oceans Canada (DFO) with resolution of 400m.";
    String summary_fr "Prévisions de courants de surface issues d'un modèle de Pêches et Océans Canada avec une résolution de 400m.";
    String time_coverage_end "2024-11-10T00:00:00Z";
    String time_coverage_start "2024-11-03T01:00:00Z";
    String title "Données de courants de surface du fleuve et de l'estuaire | Surface Currents of the St. Lawrence River, Estuary";
    Float64 Westernmost_Easting -72.6;
  }
}

 

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its projection 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.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.


 
ERDDAP, Version 2.24
Disclaimers | Privacy Policy | Contact