The NOAA GEO-IDE UAF ERDDAP
Easier access to all of NOAA's data

Make A Graph

Dataset Title:	ESPRESSO Real-Time v2 Averages, ESPRESSO Real-Time v2 Averages, Forecast Model Run Collection (2D time coordinates) [eta_rho][xi_rho]
Institution:	MARINE.RUTGERS (Dataset ID: rutgers_marine_5073_03ae_3b10)
Information:	Summary \| License \| Metadata \| Background \| Data Access Form

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Show advanced settings : Privacy / Content settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Internet Explorer: "Tools : Internet Options : Security : Internet : Custom level :
          Sripting/ Active Scripting : Enable : OK : OK"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:
X Axis:
Y Axis:
Color:

Dimensions

Start

Stop

eta_rho (count)

xi_rho (count)

specify just 1 value →

Graph Settings

Marker Type:

Size:

Color:

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  eta_rho {
    Int32 actual_range 0, 81;
    String ioos_category "Location";
    String long_name "eta rho";
    String units "count";
  }
  xi_rho {
    Int16 actual_range 0, 129;
    String ioos_category "Location";
    String long_name "xi rho";
    String units "count";
  }
  lon_rho {
    String _CoordinateAxisType "Lon";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String field "lon_rho, scalar";
    String ioos_category "Location";
    String long_name "longitude of RHO-points";
    String standard_name "longitude";
    String units "degrees_east";
  }
  lat_rho {
    String _CoordinateAxisType "Lat";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String field "lat_rho, scalar";
    String ioos_category "Location";
    String long_name "latitude of RHO-points";
    String standard_name "latitude";
    String units "degrees_north";
  }
  h {
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String field "bath, scalar";
    String ioos_category "Bathymetry";
    String long_name "bathymetry at RHO-points";
    String standard_name "sea_floor_depth";
    String units "meter";
  }
  f {
    String field "coriolis, scalar";
    String ioos_category "Unknown";
    String long_name "Coriolis parameter at RHO-points";
    String units "second-1";
  }
  pm {
    String field "pm, scalar";
    String ioos_category "Unknown";
    String long_name "curvilinear coordinate metric in XI";
    String units "meter-1";
  }
  pn {
    String field "pn, scalar";
    String ioos_category "Unknown";
    String long_name "curvilinear coordinate metric in ETA";
    String units "meter-1";
  }
  angle {
    Float64 colorBarMaximum 3.2;
    Float64 colorBarMinimum -3.2;
    String field "angle, scalar";
    String ioos_category "Unknown";
    String long_name "angle between XI-axis and EAST";
    String units "radians";
  }
  mask_rho {
    Float64 colorBarMaximum 1.5;
    Float64 colorBarMinimum 0.0;
    String flag_meanings "land water";
    Float64 flag_values 0.0, 1.0;
    String ioos_category "Identifier";
    String long_name "mask on RHO-points";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String ana_file "ROMS/Functionals/ana_btflux.h, /home/julia/ROMS/espresso/RealTime/Compile/fwd/ana_nudgcoef.h";
    String avg_base "espresso_avg_4471";
    String bry_file "../Data/espresso_bdry_new.nc";
    String cdm_data_type "Grid";
    String clm_file "../Data/espresso_clm_new.nc";
    String code_dir "/home/julia/ROMS/espresso/svn1409";
    String compiler_command "/opt/pgisoft/openmpi/bin/mpif90";
    String compiler_flags "-O3 -Mfree";
    String compiler_system "pgi";
    String Conventions "CF-1.6, SGRID-0.3, COARDS, ACDD-1.3";
    String CPP_options "MyCPP, ADD_FSOBC, ADD_M2OBC, ANA_BSFLUX, ANA_BTFLUX, ASSUMED_SHAPE, AVERAGES, BULK_FLUXES, CURVGRID, DEFLATE, DJ_GRADPS, DOUBLE_PRECISION, EAST_FSCHAPMAN, EAST_M2FLATHER, EAST_M3NUDGING, EAST_M3RADIATION, EAST_TNUDGING, EAST_TRADIATION, EMINUSP, FLOATS, FORWARD_WRITE, GLS_MIXING, HDF5, KANTHA_CLAYSON, LONGWAVE_OUT, M3CLIMATOLOGY, M3CLM_NUDGING, MASKING, MIX_GEO_TS, MIX_S_UV, MPI, NONLINEAR, NONLIN_EOS, NORTHERN_WALL, N2S2_HORAVG, POWER_LAW, PROFILE, K_GSCHEME, !RST_SINGLE, SALINITY, SOLAR_SOURCE, SOLVE3D, SOUTH_FSCHAPMAN, SOUTH_M2FLATHER, SOUTH_M3NUDGING, SOUTH_M3RADIATION, SOUTH_TNUDGING, SOUTH_TRADIATION, SPLINES, SSH_TIDES, TCLIMATOLOGY, TCLM_NUDGING, TS_A4HADVECTION, TS_A4VADVECTION, TS_DIF2, TS_PSOURCE, UV_ADV, UV_COR, UV_U3HADVECTION, UV_C4VADVECTION, UV_QDRAG, UV_PSOURCE, UV_TIDES, UV_VIS2, VAR_RHO_2D, WEST_FSCHAPMAN, WEST_M2FLATHER, WEST_M3NUDGING, WEST_M3RADIATION, WEST_TNUDGING, WEST_TRADIATION";
    String creator_email "julia@marine.rutgers.edu";
    String creator_name "Julia Levin";
    String creator_type "person";
    String creator_url "https://www.myroms.org/";
    String file "espresso_avg_4471_0001.nc";
    String flt_file "espresso_flt_4471.nc";
    String fpos_file "/home/om/cron/glider_floats/data/maracoos_floats.in";
    String frc_file_01 "/home/om/roms/espresso/Data/espresso_tide_c05_20060101.nc";
    String frc_file_02 "../Data/espresso_river.nc";
    String frc_file_03 "../Data/rain_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_04 "../Data/swrad_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_05 "../Data/Tair_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_06 "../Data/Pair_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_07 "../Data/Qair_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_08 "../Data/lwrad_down_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_09 "../Data/Uwind_ncepnam_3hourly_MAB_and_GoM.nc";
    String frc_file_10 "../Data/Vwind_ncepnam_3hourly_MAB_and_GoM.nc";
    String grd_file "/home/om/roms/espresso/Data/espresso_grid_c05.nc";
    String header_dir "/home/julia/ROMS/espresso/RealTime/Compile/fwd";
    String header_file "espresso.h";
    String his_base "espresso_his_4471";
    String history 
"ROMS/TOMS, Version 3.5, Monday - April 2, 2018 -  5:19:27 AM ;
FMRC 2D Dataset
2018-04-25T21:18:40Z http://tds.marine.rutgers.edu/thredds/dodsC/roms/espresso/2013_da/avg/ESPRESSO_Real-Time_v2_Averages_fmrc.ncd
2018-04-25T21:18:40Z http://upwell.pfeg.noaa.gov/griddap/rutgers_marine_5073_03ae_3b10.das";
    String id "roms/espresso/2013_da/avg/ESPRESSO_Real-Time_v2_Averages_fmrc.ncdhttp://tds.marine.rutgers.edu/thredds/dodsC/roms/espresso/2013_da/avg/ESPRESSO_Real-Time_v2_Averages_fmrc.ncd";
    String infoUrl "https://www.myroms.org/applications/espresso/";
    String ini_file "/home/julia/ROMS/espresso/RealTime/Storage/run04/espresso_ini_4471.nc";
    String institution "MARINE.RUTGERS";
    String keywords "2013-present, adcirc, advanced, angle, averages, axis, bathymetry, between, circulation, collection, coordinate, coordinates, coriolis, curvilinear, data, depth, earth, Earth Science > Oceans > Bathymetry/Seafloor Topography > Bathymetry, east, espresso, eta, eta_rho, experimental, floor, fmrc, forecast, identifier, is4dvar, lat_rho, latitude, lon_rho, longitude, marine.rutgers, mask, mask_rho, metric, model, modeling, new, ocean, oceans, operational, optics, parameter, points, predicting, present, real, real time, real-time, realtime, regional, rho, rho-points, roms, run, science, sea, sea_floor_depth, seafloor, shelf, slope, system, time, topography, version, xi, xi-axis, xi_rho";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "Freely available";
    String location "Proto fmrc:espresso_2013_da_avg";
    String naming_authority "edu.rutgers.marine";
    String publisher_email "wilkin@marine.rutgers.edu";
    String publisher_name "OM/IMCS";
    String publisher_type "institution";
    String publisher_url "https://marine.rutgers.edu/po/";
    String rst_file "espresso_rst_4471.nc";
    String script_file "nl_ocean_espresso.in";
    String sourceUrl "http://tds.marine.rutgers.edu/thredds/dodsC/roms/espresso/2013_da/avg/ESPRESSO_Real-Time_v2_Averages_fmrc.ncd";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Regional Ocean Modeling System (ROMS) Experimental System for Predicting Shelf and Slope Optics (ESPRESSO) Real-Time Operational IS4DVAR Forecast System Version 2 (NEW) 2013-present FMRC Averages. Forecast Model Run Collection (2D time coordinates). FMRC datasets for averages operational nowcast/forecast system version 2 for maracoos project (https://maracoos.org). grid configuration and assimilation system the same as for the ~6 km resolution roms espresso experiment. these simulations are forced by ncep nam operational atmospheric forcing, boundary conditions are from hycom-ncoda 1/12 deg model; tides are from ADvanced CIRCulation (adcirc) model. assimilated data: sst (avhrr and blended mw+ir), hf radar, along track ssh from jason2.";
    String svn_rev "exported";
    String svn_url "https://www.myroms.org/svn/src/trunk";
    String tiling "004x002";
    String title "ESPRESSO Real-Time v2 Averages, ESPRESSO Real-Time v2 Averages, Forecast Model Run Collection (2D time coordinates) [eta_rho][xi_rho]";
    String type "ROMS/TOMS nonlinear model averages file";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form. It makes the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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