Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  COAMPS 3D Air Temperature, 3km Subscribe RSS
Institution:  Naval Research Lab   (Dataset ID: COAMPS_3KM_AGG_AIR_TEMP)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
Dimensions ?    Start ?    Stop ?
time (UTC) ?     specify just 1 value →
    |< -
< <
height (m) ?     specify just 1 value →
    |< -
< <
y (km) ?
< slider >
x (km) ?
< slider >
Graph Settings
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    [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 {
    UInt32 _ChunkSizes 1;
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.346328e+9, 1.3802832e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "forecast date time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  height {
    UInt32 _ChunkSizes 6;
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "up";
    Float64 actual_range 111.0, 11775.0;
    String ioos_category "Location";
    String long_name "height above sea level";
    String standard_name "projection_z_coordinate";
    String units "m";
  y {
    UInt32 _ChunkSizes 319;
    String _CoordinateAxisType "GeoY";
    Float64 actual_range -2857.9903142744797, -1903.9903142744797;
    String grid_spacing "3.0 km";
    String ioos_category "Location";
    String long_name "y coordinate of projection";
    String standard_name "projection_y_coordinate";
    String units "km";
  x {
    UInt32 _ChunkSizes 220;
    String _CoordinateAxisType "GeoX";
    Float64 actual_range -202.9049131166666, 454.0950868833334;
    String grid_spacing "3.0 km";
    String ioos_category "Location";
    String long_name "x coordinate of projection";
    String standard_name "projection_x_coordinate";
    String units "km";
  air_temperature {
    UInt32 _ChunkSizes 1, 3, 319, 220;
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum -10.0;
    Int32 GRIB_center_id 58;
    Int32 GRIB_level_type 100;
    Int32 GRIB_param_id 1, 58, 3, 11;
    String GRIB_param_name "air_temperature";
    Int32 GRIB_param_number 11;
    String GRIB_param_short_name "var11";
    String GRIB_product_definition_type "Initialized analysis product";
    Int32 GRIB_table_id 3;
    String GRIB_VectorComponentFlag "easterlyNortherlyRelative";
    String grid_mapping "Lambert_Conformal";
    String ioos_category "Temperature";
    String long_name "air_temperature @ isobaric";
    Float64 missing_value -9999.0;
    String standard_name "air_temperature";
    String units "degree_Celsius";
    String _CoordinateModelRunDate "2012-08-30T12:00:00Z";
    String _CoordSysBuilder "ucar.nc2.internal.dataset.conv.CF1Convention";
    String cdm_data_type "Grid";
    String CF_feature_type "GRID";
    String Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    String creator_email "";
    String creator_name "Naval Research Lab";
    String creator_url "";
    String date_issued "2013-09-27";
    String file_format "GRIB-1";
    String history 
"Direct read of GRIB-1 into NetCDF-Java 4 API
2023-03-28T08:57:43Z (local files)
    String infoUrl "";
    String institution "Naval Research Lab";
    String keywords "3km, air, air_temperature, atmosphere, atmospheric, coamps, Earth Science > Atmosphere > Atmospheric Temperature > Air Temperature, Earth Science > Atmosphere > Atmospheric Temperature > Surface Air Temperature, isobaric, lab, naval, research, surface, temperature";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "Equivalent to Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA).  Read the full text of NRL's use agreement at Learn more about Creative Commons licenses at";
    String location "/mnt/gluster/data/netCDF/coamps/mbay_3km/air_temp/762m/";
    String Metadata_Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    String metadata_link "";
    String Originating_center "U.S. Navy Fleet Numerical Meteorology and Oceanography Center (58)";
    String Product_Type "Forecast/Uninitialized Analysis/Image Product";
    String publisher_email "";
    String publisher_name "Central and Northern California Ocean Observing System";
    String publisher_url "";
    String source "Forecast/Uninitialized Analysis/Image Product";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Names Vocabulary V27";
    String summary "Aggregated air temperature at altitude from historical 48-hour weather forecasts from the CeNCOOS COAMPS model (MBAY) from August 2012 to September 2013. For newer data ( Aug 2013 - Present), look at the 'COAMPS Forecast' layer. 48-hour weather forecasts were provided by the Coupled Ocean/Atmosphere Mesoscale Prediction System, (Naval Research Laboratory, Monterey, CA) and were aggregated by Engineers at Axiom Data Science for CeNCOOS.   This model run had a resolution of 3km and covered the coastal ocean from Oregon to Pt. Conception. Variables available in the CeNCOOS data portal include: Total Precipitation, Visibility, Cloudbase, Air Temperature, Relative Humidity and Winds. Other atmospheric variables and altitude layers are available through the GODAE server ie. heat flux, sea level pressure, vorticity, geopotential height. More information: CeNCOOS COAMPS page: NRL COAMPS page: GODAE server:";
    String time_coverage_end "2013-09-27T12:00:00Z";
    String time_coverage_start "2012-08-30T12:00:00Z";
    String title "COAMPS 3D Air Temperature, 3km";


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{?query}
For example,[(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.20
Disclaimers | Privacy Policy | Contact