Logo ISMAR CNR-ISMAR
Access to maritime scientific data 		   
This server instance is funded by ITINERIS project

ERDDAP > griddap > Make A Graph ?

Dataset Title:  adriatic tiresias Subscribe RSS
Institution:  ISMAR-CNR, Venice, Italy   (Dataset ID: VE_Delta_Po_2010_2011_CWC_UV)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    |< - +
    - >|
< slider >
node (count) ?     specify just 1 value →
    |< -
< <
depth (m) ?     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.262304e+9, 1.2649752e+9;
    String axis "T";
    String calendar "standard";
    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";
  }
  node {
    Int32 actual_range 0, 38903;
    String long_name "Node";
    String units "count";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1.0, 34.0;
    String axis "Z";
    String description "bottom of vertical layers";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String source_name "level";
    String standard_name "depth";
    String units "m";
  }
  u_velocity {
    Float32 _FillValue -999.0;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String long_name "Eastward Sea Water Velocity";
    String standard_name "eastward_sea_water_velocity";
    String units "m s-1";
    Float32 valid_max 10.0;
    Float32 valid_min -10.0;
  }
  v_velocity {
    Float32 _FillValue -999.0;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String long_name "Northward Sea Water Velocity";
    String standard_name "northward_sea_water_velocity";
    String units "m s-1";
    Float32 valid_max 10.0;
    Float32 valid_min -10.0;
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String comment "Data restriction: for academic research use only";
    String contact "email: georg.umgiesser@ismar.cnr.it";
    String Conventions "CF-1.10, COARDS, ACDD-1.3";
    String creator_email "georg.umgiesser@ismar.cnr.it";
    String creator_name "Georg Umgiesser";
    String creator_type "person";
    String history 
"created on 2020-03-17 17:06:38 MET
2024-11-10T01:59:08Z (local files)
2024-11-10T01:59:08Z http://erddap-danubius.ve.ismar.cnr.it/griddap/VE_Delta_Po_2010_2011_CWC_UV.das";
    String infoUrl "???";
    String institution "ISMAR-CNR, Venice, Italy";
    String keywords "adriatic, circulation, cnr, council, currents, data, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, eastward, eastward_sea_water_velocity, ismar, ismar-cnr, italy, level, national, node, northward, northward_sea_water_velocity, ocean, oceans, research, science, sea, seawater, time, tiresias, u_velocity, v_velocity, velocity, venice, 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 references "Model info: http://www.ismar.cnr.it/shyfem";
    String source "Model data produced by SHYFEM at ISMAR-CNR";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Data restriction: for academic research use only";
    String time_coverage_end "2010-01-31T22:00:00Z";
    String time_coverage_start "2010-01-01T00:00:00Z";
    String title "adriatic tiresias";
  }
}

 

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