NOAA ERDDAP
Easier access to scientific data
log in | ?    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  NRL HYCOM+NCODA, GLBu0.08/expt 91.1, Global, 1/12 deg, 2014-2016, Time Subscribe RSS
Institution:  Naval Oceanographic Office   (Dataset ID: nrlHycomGLBu008e911T)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    |< - +
    -
< slider >
 
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.3968288e+9, 1.4609376e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Valid Time";
    Int32 NAVO_code 13;
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  tau {
    String ioos_category "Time";
    String long_name "Tau (hours since analysis)";
    Int32 NAVO_code 56;
    String time_origin "2016-04-17 00:00:00";
    String units "hours";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String classification_authority "not applicable";
    String classification_level "UNCLASSIFIED";
    String Conventions "CF-1.6, NAVO_netcdf_v1.0, COARDS, ACDD-1.3";
    String creator_email "hycomdata@coaps.fsu.edu";
    String creator_name "Naval Oceanographic Office";
    String creator_type "institution";
    String creator_url "https://www.hycom.org";
    String distribution_statement "Approved for public release. Distribution unlimited.";
    String downgrade_date "not applicable";
    String field_type "instantaneous";
    String history 
"archv2ncdf2d
2024-03-29T12:01:43Z https://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_91.1
2024-03-29T12:01:43Z http://coastwatch.pfeg.noaa.gov/griddap/nrlHycomGLBu008e911T.das";
    String infoUrl "https://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_91.1.html";
    String institution "Naval Oceanographic Office";
    String keywords "data, glbu, naval, oceanographic, office, tau, tds.hycom.org, thredds, time";
    String license 
"Approved for public release. Distribution unlimited.
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 source "HYCOM archive file";
    String sourceUrl "https://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_91.1";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "HYbrid Coordinate Ocean Model (HYCOM) + NCODA, GLBu0.08/expt 91.1, Global, 1/12 deg, from the U.S. Navy's Naval Research Laboratory (NRL). The hybrid coordinate is one that is isopycnal in the open, stratified ocean, but smoothly reverts to a terrain-following coordinate in shallow coastal regions, and to z-level coordinates in the mixed layer and/or unstratified seas. The hybrid coordinate extends the geographic range of applicability of traditional isopycnic coordinate circulation models (the basis of the present hybrid code), such as the Miami Isopycnic Coordinate Ocean Model (MICOM) and the Navy Layered Ocean Model (NLOM), toward shallow coastal seas and unstratified parts of the world ocean.";
    String time_coverage_end "2016-04-18T00:00:00Z";
    String time_coverage_start "2014-04-07T00:00:00Z";
    String title "NRL HYCOM+NCODA, GLBu0.08/expt 91.1, Global, 1/12 deg, 2014-2016, Time";
  }
}

 

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