NOAA The NOAA GEO-IDE UAF ERDDAP
Easier access to all of NOAA's data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Data Access Form ?

Dataset Title:  HYCOM Surface, HYCOM Surface, Best Time Series [time], 2013-present Subscribe RSS
Institution:  Naval Oceanographic Office   (Dataset ID: noaa_ncddc_cc1d_d4d0_30bd)
Information:  Summary ? | License ? | Metadata | Background (external link) | Make a graph
 
Dimensions ? Start ? Stride ? Stop ?  Size ?    Spacing ?
 time (UTC) ?      12315    3h 39m 51s (uneven)
  < slider >
 
Grid Variables (which always also download all of the dimension variables)
 time_run (run times for coordinate = time, seconds since 1970-01-01T00:00:00Z) ?
 time_offset (seconds since 1970-01-01T00:00:00Z) ?

File type: (more info)

(Documentation / Bypass this form) ?
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.3624416e+9, 1.5248736e+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";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String cdm_data_type "Grid";
    String contact "NAVOCEANO, NP31";
    String Conventions "CF-1.6, NAVO_netcdf_v1.1, COARDS, ACDD-1.3";
    String creator_email "forum@hycom.org";
    String creator_name "kelly.r.wood@navy.mil; jeffery.rayburn@navy.mil";
    String creator_url "https://hycom.org/";
    String distribution_statement "Approved for public release: distribution unlimited.";
    String field_type "instantaneous";
    String generating_model "GOFS 3.0, Global HYCOM with OSU tides";
    String history 
"created on 20180324 ;
FMRC Best Dataset
2018-04-23T11:52:19Z https://ecowatch.ncddc.noaa.gov/thredds/dodsC/hycom/hycom_sfc_agg/HYCOM_Surface_Aggregation_best.ncd
2018-04-23T11:52:19Z http://upwell.pfeg.noaa.gov/erddap/griddap/noaa_ncddc_cc1d_d4d0_30bd.das";
    String id "hycom/hycom_sfc_agg/HYCOM_Surface_Aggregation_best.ncdhttps://ecowatch.ncddc.noaa.gov/thredds/dodsC/hycom/hycom_sfc_agg/HYCOM_Surface_Aggregation_best.ncd";
    String infoUrl "http://www.navo.navy.mil/";
    String input_data_source "FNMOC NAVGEM, Satellite SSH, SST, in situ";
    String institution "Naval Oceanographic Office";
    String keywords "best, best time series, coordinate, data, forecast, forecast_period, forecast_reference_time, hour, hybrid, hycom, model, naval, ocean, oceanographic, office, offset, period, reference, run, series, start, surface, time, time series, time_offset, time_run, times";
    String license "Approved for public release: distribution unlimited.";
    String location "Proto fmrc:HYCOM_Surface_Aggregation";
    String model_type "x-curvilinear lon, y-curvilinear lat, hybrid z";
    String operational_status "operational";
    String publisher_name "OceanNOMADS@noaa.gov";
    String publisher_type "institution";
    String references "http://www.navo.navy.mil/";
    String source "HYCOM archive file";
    String sourceUrl "https://ecowatch.ncddc.noaa.gov/thredds/dodsC/hycom/hycom_sfc_agg/HYCOM_Surface_Aggregation_best.ncd";
    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 HYbrid Coordinate Ocean Model (HYCOM) Region Surface Aggregation of HYCOM Region 1";
    String testOutOfDate "now+4days";
    String time_coverage_end "2018-04-28T00:00:00Z";
    String time_coverage_start "2013-03-05T00:00:00Z";
    String time_origin "2018-03-24 00:00:00";
    String title "HYCOM Surface, HYCOM Surface, Best Time Series [time], 2013-present";
  }
}

 

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://upwell.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://upwell.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
Disclaimers | Privacy Policy | Contact