ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD

Make A Graph

Dataset Title:	ROMS DOPPIO OBS FILE
Institution:	Institute for Marine and Coastal Sciences, Rutgers University (Dataset ID: DOPPIOobs)
Range:	longitude = -80.24546 to -59.125°E, latitude = 31.875 to 47.125°N, depth = -3250.0 to 0.0m, time = 2016-06-12T00:00:00Z to 2024-04-17T23:45:10Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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 : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

Constraints

Optional
Constraint #1

Optional
Constraint #2

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

Draw land mask:

Y Axis Minimum:

Maximum:

(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

)

Click on the map to specify a new center point.

Zoom:

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:

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 {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.4656896e+9, 1.71339751008e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "time of observation";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range -3250.0, 0.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "depth_of_observation";
    String negative "downwards";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 31.875, 47.125;
    String axis "Y";
    String ioos_category "Location";
    String long_name "latitude of observation";
    String standard_name "latitude";
    String units "degrees_north";
    Float32 valid_max 90.0;
    Float32 valid_min -90.0;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -80.24546, -59.125;
    String axis "X";
    String ioos_category "Location";
    String long_name "longitude of observation";
    String standard_name "longitude";
    String units "degrees_east";
    Float32 valid_max 180.0;
    Float32 valid_min -180.0;
  }
  value {
    Float32 actual_range -1.56888236e+11, 5.6997715e+18;
    String ioos_category "Other";
    String long_name "observation value";
    String units "magnitude in terms of state variable type";
  }
  type {
    Float32 actual_range 1.0, 7.0;
    String ioos_category "Other";
    String long_name "model state variable associated with observation";
    String option_01 "free-surface";
    String option_02 "vertically integrated u-momentum component";
    String option_03 "vertically integrated v-momentum component";
    String option_04 "u-momentum component";
    String option_05 "v-momentum component";
    String option_06 "potential temperature";
    String option_07 "salinity";
    String units "unity";
  }
  provenance {
    Float32 actual_range 203.0, 1747.0;
    Int32 ALTIKA_SSH 426;
    Int32 Altimeter_superobs 400;
    Int32 AMSR_microwave_SST 306;
    Int32 AVHRR_IR_SST 302;
    Int32 CODAR_velocities 500;
    Int32 Cryosat_SSH 424;
    Int32 ECOMON_CTD 730;
    Int32 Envisat_SSH 423;
    Int32 GOES_geostationary_IR_SST 303;
    String ioos_category "Other";
    Int32 IOOS_gliders 702;
    Int32 Jason_1_SSH 401;
    Int32 Jason_2_SSH 402;
    Int32 Jason_3_SSH 403;
    Int32 MetOffice_Argo 722;
    Int32 MetOffice_Bouys 723;
    Int32 MetOffice_CTD_XCTD_TESAC 721;
    Int32 MetOffice_XBT 720;
    Int32 NERACOOS_CTD 740;
    Int32 OSMC_GTS_floats 713;
    Int32 OSMC_GTS_gliders 711;
    Int32 OSMC_GTS_moored_bouys 716;
    Int32 OSMC_GTS_other 710;
    Int32 OSMC_GTS_ships_generic 717;
    Int32 OSMC_GTS_VOShips 714;
    Int32 Pioneer_Array_CP01CNSM 601;
    Int32 Pioneer_Array_CP01CNSP 602;
    Int32 Pioneer_Array_CP02PMCI 603;
    Int32 Pioneer_Array_CP02PMCO 606;
    Int32 Pioneer_Array_CP02PMUI 605;
    Int32 Pioneer_Array_CP02PMUO 610;
    Int32 Pioneer_Array_CP03ISSM 607;
    Int32 Pioneer_Array_CP03ISSP 608;
    Int32 Pioneer_Array_CP04OSPM 609;
    Int32 Pioneer_Array_CP04OSSM 611;
    Int32 Pioneer_Array_GL003 641;
    Int32 Pioneer_Array_GL335 642;
    Int32 Pioneer_Array_GL336 643;
    Int32 Pioneer_Array_GL339 644;
    Int32 Pioneer_Array_GL340 645;
    Int32 Pioneer_Array_GL374 646;
    Int32 Pioneer_Array_GL376 647;
    Int32 Pioneer_Array_GL379 648;
    Int32 Pioneer_Array_GL380 649;
    Int32 Pioneer_Array_GL387 650;
    Int32 Pioneer_Array_GL388 651;
    Int32 Pioneer_Array_GL389 652;
    Int32 Pioneer_Array_GL390 653;
    Int32 Pioneer_Array_PG564 654;
    Int32 RU_MARACOOS_gliders 701;
    Int32 Sentinel_3a_SSH 441;
    Int32 Sentinel_3b_SSH 442;
    Int32 SST_super_observations 300;
    Int32 TRMM_microwave_SST 304;
    Int32 VIIRS_IR_SST 307;
    Int32 WSAT_microwave_SST 305;
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "CF-1.6";
    Float64 Easternmost_Easting -59.125;
    String featureType "Point";
    Float64 geospatial_lat_max 47.125;
    Float64 geospatial_lat_min 31.875;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -59.125;
    Float64 geospatial_lon_min -80.24546;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.0;
    Float64 geospatial_vertical_min -3250.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Thu Apr 18 15:00:24 2024: ncks -O -d obs_time,6681.0,6681.99999 /home/om/cron/erddap_doppio/tmp/temp.nc /home/om/cron/erddap_doppio/data/temp_6681.nc
Thu Apr 18 15:00:23 2024: ncrename -O -d datum,obs_time /home/julia/ROMS/doppio/RealTime/CombineOBS//ssh_sst_codar_glider_ctd_argo_6679.nc /home/om/cron/erddap_doppio/tmp/temp.nc
18-Apr-2024 02:50:31:  Prepared by Julia Levin (julia@marine.rutgers.edu)
18-Apr-2024 02:50:31:  Blended data
2024-04-19T10:03:28Z http://tds.marine.rutgers.edu
2024-04-19T10:03:28Z https://tds.marine.rutgers.edu/tabledap/DOPPIOobs.das";
    String infoUrl "https://marine.rutgers.edu/cool";
    String institution "Institute for Marine and Coastal Sciences, Rutgers University";
    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 NCO "netCDF Operators version 5.1.8 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco, Citation = 10.1016/j.envsoft.2008.03.004)";
    Float64 Northernmost_Northing 47.125;
    String sourceUrl "http://tds.marine.rutgers.edu";
    Float64 Southernmost_Northing 31.875;
    String state_units "Free-surface (m), 2D momentum (m/s), 3D momentum (m/s), potential temperature (Celsius), salinity (PSU)";
    String subsetVariables "type,provenance";
    String summary "ROMS OBSERVATION FILE";
    String time_coverage_end "2024-04-17T23:45:10Z";
    String time_coverage_start "2016-06-12T00:00:00Z";
    String title "ROMS DOPPIO OBS FILE";
    String type "Roms observation file";
    Float64 Westernmost_Easting -80.24546;
  }
}

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its selection 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 or Subset form. They make 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.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.

ERDDAP, Version 2.23
Disclaimers | Privacy Policy | Contact