Easier access to all of NOAA's data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  NCOM Region 10, Best Time Series [time], 2010-2013 Subscribe RSS
Institution:  Naval Oceanographic Office   (Dataset ID: noaa_ncddc_5325_cd6e_43de)
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 Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   Ascending: 
(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 ? )
    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.272672e+9, 1.3639104e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Forecast time for ForecastModelRunCollection";
    Float64 missing_value NaN;
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  time_run {
    String _CoordinateAxisType "RunTime";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "run times for coordinate = time";
    String standard_name "forecast_reference_time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  time_offset {
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "offset hour from start of run for coordinate = time";
    String standard_name "forecast_period";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String cdm_data_type "Grid";
    String classification_authority "not applicable";
    String classification_level "UNCLASSIFIED";
    String contact "NAVO, N33";
    String Conventions "CF-1.6, NAVO_netcdf_v1.0, COARDS, ACDD-1.3";
    String creator_email "";
    String creator_name "USA/NAVY/NAVO";
    String creator_type "institution";
    String creator_url "";
    String distribution_statement "Approved for public release. Distribution unlimited.";
    String downgrade_date "not applicable";
    String generating_model "Global NCOM with OSU tides";
    String history 
"Thu Nov  7 10:58:19 2013: ncks -O -dtime,0,7 ./ ./
created on 20130318 ;
FMRC Best Dataset
    String id "ncom.ncom_reg10_agg.NCOM_Region_10_Aggregation_best.ncd";
    String infoUrl "";
    String input_data_source "FNMOC NOGAPS, NAVO MODAS, NAVO NLOM";
    String institution "Naval Oceanographic Office";
    String keywords "atmospheric, best, best time series, coastal, coordinate, data, forecast, forecast_period, forecast_reference_time, global, hour, model, naval, navoceano, navy, ncom, nogaps, ocean, oceanographic, office, offset, operational, period, prediction, reference, region, run, series, start, system, time, time series, time_offset, time_run, times";
    String license "Approved for public release. Distribution unlimited.";
    String location "Proto fmrc:NCOM_Region_10_Aggregation";
    String message "UNCLASSIFIED";
    String model_type "x-curvilinear lon, y-curvilinear lat, z-sigma_z";
    String NCO "4.0.5";
    String operational_status "development";
    String publisher_email "";
    String publisher_name "USA/NOAA/NESDIS/NCDDC";
    String publisher_type "institution";
    String publisher_url "";
    String references "";
    String sourceUrl "";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Best time series, taking the data from the most recent run available. Aggregation of NCOM Region 10 These forecasts are from an operational, data assimilating nowcast-forecast system run by the Naval Oceanographic Office using the Navy Coastal Ocean Model (NCOM). The output files contain temperature, salinity, east and north components of current, and surface elevation, interpolated to a 1/8 degree Cartesian grid in the horizontal and to standard depth levels in the vertical, and written at three-hour intervals out to 72 hours. The Navy global atmospheric model, Navy Operational Global Atmospheric Prediction System (NOGAPS), provides atmospheric forcing. A tidal component is not included in the model output.";
    String time_coverage_end "2013-03-22T00:00:00Z";
    String time_coverage_start "2010-05-01T00:00:00Z";
    String time_origin "2013-03-18 00:00:00";
    String title "NCOM Region 10, Best Time Series [time], 2010-2013";


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