| ?    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  SYROCO Danube-mouths hourly U grid variables Subscribe RSS
Institution:  seamod.ro   (Dataset ID: DANUBE_1h_grid_U)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    |< - +
    - >|
< slider >
depth (m) ?     specify just 1 value →
    |< -
< <
gridY (grid points) ?     specify just 1 value →
    |< -
< <
gridX (grid points) ?     specify just 1 value →
    |< -
< <
 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6726212e+9, 1.7325792e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Time axis";
    String source_name "time_counter";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.2546195, 70.14085;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String name "depthu";
    String positive "down";
    String source_name "depthu";
    String standard_name "depth";
    String units "m";
  }
  gridY {
    Int16 actual_range 0, 567;
    String long_name "grid Y";
    String source_name "y";
    String standard_name "y";
    String units "grid points";
  }
  gridX {
    Int16 actual_range 0, 392;
    String long_name "grid X";
    String source_name "x";
    String standard_name "x";
    String units "grid points";
  }
  u_velocity {
    Float32 _FillValue 1.0e+20;
    String cell_methods "time: point";
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String interval_operation "1 h";
    String interval_write "1 h";
    String long_name "ocean current along i-axis";
    Float32 missing_value 1.0e+20;
    String online_operation "instant";
    String standard_name "sea_water_x_velocity";
    String units "m/s";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator "seamod.ro";
    String description "ocean U grid variables";
    String history 
"2024-11-21T23:19:11Z (local files)
2024-11-21T23:19:11Z http://seamod.ro:8080/griddap/DANUBE_1h_grid_U.das";
    String infoUrl "http://seamod.ro/syroco.html";
    String institution "seamod.ro";
    String keywords "along, axis, circulation, counter, current, currents, data, depthu, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, grid, i-axis, ocean, oceans, science, sea, sea_water_x_velocity, seawater, time, time_counter, u, velocity, water";
    String keywords_vocabulary "GCMD Science Keywords";
    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.";
    String name "2_out/DANUBE_1h_20241110_20241110_grid_U";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "SYROCO Danube-mouths hourly U grid variables.";
    String testOutOfDate "now+3days";
    String time_coverage_end "2024-11-26T00:00:00Z";
    String time_coverage_start "2023-01-02T01:00:00Z";
    String timeStamp "2024-Nov-16 11:40:22 GMT";
    String title "SYROCO Danube-mouths hourly U grid variables";
    String type "analysis with era5t";
  }
}

 

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