NOAA ERDDAP
Easier access to scientific data
   
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  COAMPS Cloud Base Altitude Forecast, 4km Subscribe RSS
Institution:  58   (Dataset ID: COAMPS_4KM_CLD_BASE)
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 →
    << -
< <
y (km) ?
    +
    -
< slider >
x (km) ?
    +
    -
< slider >
 
Graph Settings
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 ? )
    [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.3775184e+9, 1.5103332e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "date time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  y {
    String _CoordinateAxisType "GeoY";
    Float64 actual_range 3217.6206264877414, 4657.620626487742;
    String grid_spacing "4.0 km";
    String ioos_category "Location";
    String long_name "y coordinate of projection";
    String standard_name "projection_y_coordinate";
    String units "km";
  }
  x {
    String _CoordinateAxisType "GeoX";
    Float64 actual_range 0.0, 1200.0;
    String grid_spacing "4.0 km";
    String ioos_category "Location";
    String long_name "x coordinate of projection";
    String standard_name "projection_x_coordinate";
    String units "km";
  }
  cloud_base {
    Int32 GRIB_center_id 58;
    Int32 GRIB_level_type 1;
    Int32 GRIB_param_id 1, 58, 3, 135;
    String GRIB_param_name "cloud_base";
    Int32 GRIB_param_number 135;
    String GRIB_param_short_name "cld_base";
    String GRIB_product_definition_type "Initialized analysis product";
    Int32 GRIB_table_id 3;
    String GRIB_VectorComponentFlag "easterlyNortherlyRelative";
    String grid_mapping "Mercator";
    String ioos_category "Meteorology";
    String long_name "cloud_base @ surface";
    Float32 missing_value -9999.0;
    String standard_name "cloud_base_altitude";
    String units "m";
  }
  NC_GLOBAL {
    String _CoordinateModelRunDate "2015-05-28T12:00:00Z";
    String _CoordSysBuilder "ucar.nc2.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_name "58";
    String date_issued "2013-08-01";
    String file_format "GRIB-1";
    String history 
"Direct read of GRIB-1 into NetCDF-Java 4 API
2018-11-14T07:40:42Z (local files)
2018-11-14T07:40:42Z http://erddap.axiomdatascience.com/griddap/COAMPS_4KM_CLD_BASE.das";
    String infoUrl "???";
    String institution "58";
    String keywords "4km, altitude, atmosphere, base, boundary, cloud, cloud_base_altitude, clouds, coamps, Earth Science > Atmosphere > Altitude > Planetary Boundary Layer Height, Earth Science > Atmosphere > Clouds > Cloud Base, Earth Science > Atmosphere > Clouds > Cloud Properties > Cloud Base Height, forecast, height, layer, meteorology, planetary, properties, surface";
    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 location "/mnt/gluster/data/netCDF/coamps/cencoos_4km/cld_base/0m/coamps_cencoos_4km_0m_cld_base_2015-05-28-16_2015.148.12.nc";
    String Metadata_Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    String original_institution "Center U.S. Navy Fleet Numerical Meteorology and Oceanography Center (58)";
    String Originating_center "U.S. Navy Fleet Numerical Meteorology and Oceanography Center (58)";
    String Product_Type "Forecast/Uninitialized Analysis/Image Product";
    String publisher_email "coamps@nrlmry.navy.mil";
    String publisher_name "Naval Research Laboratory";
    String publisher_url "www.nrlmry.navy.mil/coamps-web/home";
    String source "Forecast/Uninitialized Analysis/Image Product";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Names V27";
    String summary "Near-real-time 48-hour weather forecasts from the new CeNCOOS COAMPS model run (August 2013 - Present). For older data, look at the COAMPS Forecast [2012 - 2013] layer. The Coupled Ocean/Atmosphere Mesoscale Prediction System, developed and run by the Naval Research Laboratory (NRL) in Monterey, CA, is a numerical weather prediction model. This model run has a resolution of 4km and covers the coastal ocean from Oregon to Mexico. Variables available in the CeNCOOS data portal include: Total Precipitation, Visibility, Cloudbase, Air Temperature, Relative Humidity and Wind. Other atmospheric variables and additional altitude layers are available through the GODAE server ie. heat flux, sea level pressure, vorticity, geopotential height. More information: CeNCOOS COAMPS page: http://www.cencoos.org/sections/models/coamps/ NRL COAMPS page: http://www.nrlmry.navy.mil/coamps-web/web/cencoos GODAE server: http://www.usgodae.org/pub/outgoing/fnmoc/models/coamps/calif/cencoos/";
    String time_coverage_end "2017-11-10T17:00:00Z";
    String time_coverage_start "2013-08-26T12:00:00Z";
    String title "COAMPS Cloud Base Altitude Forecast, 4km";
  }
}

 

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 1.82_axiom-r1
Disclaimers | Privacy Policy | Contact