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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Empire Metocean Buoy, ADCP Timeseries Data Subscribe RSS
Institution:  Empire Wind   (Dataset ID: Empire_adcp)
Range: longitude = -73.4461 to -73.4461°E, latitude = 40.319 to 40.319°N, depth = 1.0 to 40.0m, time = 2025-07-03T19:58:49Z to 2025-09-17T23:18:38Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
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.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.751572729e+9, 1.758151118e+9;
    String axis "T";
    String calendar "gregorian";
    String cf_role "profile_id";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  station {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String standard_name "platform_name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 _FillValue NaN;
    Float32 actual_range 40.319, 40.319;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 _FillValue NaN;
    Float32 actual_range -73.4461, -73.4461;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1.0, 40.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  ZCel_WTmp {
    Float32 _FillValue NaN;
    Float32 actual_range 20.22, 27.14;
    String coordinates "latitude longitude station";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Temperature";
    String long_name "Water Temperature";
    String ncei_name "WATER TEMPERATURE";
    String standard_name "sea_water_temperature";
    String standard_name_url "https://vocab.nerc.ac.uk/collection/P07/current/CFSN0335";
    String units "C";
  }
  CurrSpd {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 0.9;
    String coordinates "latitude longitude station";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Currents";
    String long_name "Current Speed";
    String ncei_name "CURRENT METER - SPEED";
    String standard_name "sea_water_speed";
    String standard_name_url "https://vocab.nerc.ac.uk/collection/P07/current/CFSN0334";
    String units "m s-1";
  }
  CurrDirTo {
    Float32 _FillValue NaN;
    Float32 actual_range 0.01, 359.91;
    String coordinates "latitude longitude station";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Currents";
    String long_name "Current Direction";
    String ncei_name "CURRENT METER - DIRECTION";
    String standard_name "sea_water_velocity_to_direction";
    String standard_name_url "https://vocab.nerc.ac.uk/collection/P07/current/5D4D7YMF";
    String units "degree";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.9.3,hdf5=1.14.6";
    String acknowledgement "This dataset is part of a MetOcean Cyberinfrastructure supported by the Integrated Ocean Observing System (IOOS) to streamline integration of data from offshore operations.";
    String cdm_data_type "TimeSeriesProfile";
    String cdm_profile_variables "time";
    String cdm_timeseries_variables "station,longitude,latitude,depth";
    String comment "Empire Metocean Buoy developed and deployed by Woods Hole Group";
    String contributor_address "107 Waterhouse Rd, Bourne, MA 02532";
    String contributor_email "rnewell at woodsholegroup";
    String contributor_name "Woods Hole Group";
    String contributor_url "https://www.woodsholegroup.com/";
    String creator_address "34 35th Sreet Suite A415, Brooklyn, NY 11232";
    String creator_country "USA";
    String creator_email "empirewind at equinor.com";
    String creator_name "Empire Wind";
    String creator_sector "industry";
    String creator_state "New York";
    String creator_URL "https://www.empirewind.com/";
    Float64 Easternmost_Easting -73.4461;
    String featureType "TimeSeriesProfile";
    Float64 geospatial_lat_max 40.319;
    Float64 geospatial_lat_min 40.319;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -73.4461;
    Float64 geospatial_lon_min -73.4461;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 40.0;
    Float64 geospatial_vertical_min 1.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-09-17T23:56:46Z (local files)
2025-09-17T23:56:46Z http://data.neracoos.org/tabledap/Empire_adcp.das";
    String id "EW1-adcp";
    String infoURL "https://www.empirewind.com/";
    String infoUrl "https://www.empirewind.com/";
    String institution "Empire Wind";
    String Instrument "Nortek Aquadopp Profiler Z-Cell 1000kHz";
    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, Empire Wind, Equinor, 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.";
    Float64 Northernmost_Northing 40.319;
    String platform_name "Empire Wind Metocean Buoy";
    String processing_level "raw dataset, no qc provided";
    String project "Empire Wind";
    String publisher_country "USA";
    String publisher_email "devops at rpsgroup.com, info at neracoos.org";
    String publisher_institution "MARACOOS, NERACOOS";
    String publisher_name "MARACOOS, NERACOOS";
    String publisher_phone "(401) 789-6224, (603) 319-1785";
    String publisher_type "institution";
    String publisher_url "https://www.maracoos.org, https://www.neracoos.org";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.319;
    String standard_name_vocabulary "CF Standard Name Table v90";
    String subsetVariables "depth";
    String summary "This dataset contains observations to support further understanding of metocean conditions off the coast of New York. Data is collected from a floating wave buoy and the dataset includes  measurements of sea temperature, conductivity, current speed, current direction, wave height, wave direction, and wave period, air temperature, atmospheric pressure, relative humidity, visibility, surface wind speed,  surface wind direction, and surface wind gust.";
    String time_coverage_end "2025-09-17T23:18:38Z";
    String time_coverage_start "2025-07-03T19:58:49Z";
    String title "Empire Metocean Buoy, ADCP Timeseries Data";
    Float64 Westernmost_Easting -73.4461;
  }
}

 

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.

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