NERACOOS   ERDDAP
Easier access to realtime and historic NERACOOS buoy observations.
   
Brought to you by NOAA IOOS NERACOOS    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  J02 Accelerometer - Waves   RSS
Institution:  Univ. of Maine   (Dataset ID: J02_accelerometer_all)
Range: longitude = -67.01072 to -67.01072°E, latitude = 44.88791 to 44.88791°N, depth = 0.0 to 0.0m, time = 2002-11-13T16:00:00Z to 2007-12-06T17:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background | Subset | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Color: 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  station {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station J02";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0372031999999866e+9, 1.1969604000000134e+9;
    String axis "T";
    String calendar "gregorian";
    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";
  }
  mooring_site_desc {
    String ioos_category "Location";
    String long_name "Station Description";
  }
  significant_wave_height {
    Float32 _FillValue -999.0;
    Float32 actual_range 0.0, 1.315059;
    String ancillary_variables "significant_wave_height_qc";
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum 0.0;
    String coordinates "time lon lat depth";
    Int32 epic_code 4061;
    String ioos_category "Surface Waves";
    String long_name "Significant Wave Height";
    String short_name "SWH";
    String standard_name "significant_height_of_wind_and_swell_waves";
    String units "meters";
    Float32 valid_range 0.0, 40.0;
  }
  significant_wave_height_qc {
    Byte _FillValue -128;
    Byte actual_range 0, 40;
    Float64 colorBarMaximum 128.0;
    Float64 colorBarMinimum 0.0;
    String coordinates "time lon lat depth";
    String flag_meanings "quality_good out_of_range sensor_nonfunctional algorithm_failure_no_infl_pt";
    Byte flag_values 0, 1, 2, 3;
    String intent "data_quality";
    String ioos_category "Quality";
    String long_name "Significant Wave Height Quality Control";
    String short_name "SWHQC";
    String standard_name "significant_wave_height data_quality";
    String units "1";
    Byte valid_range -127, 127;
  }
  dominant_wave_period {
    Float32 _FillValue -999.0;
    Float32 actual_range 1.032258, 16.0;
    String ancillary_variables "dominant_wave_period_qc";
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum 0.0;
    String coordinates "time lon lat depth";
    Int32 epic_code 4063;
    String ioos_category "Surface Waves";
    String long_name "Dominant Wave Period";
    String short_name "DWP";
    String standard_name "period";
    String units "seconds";
    Float32 valid_range 0.0, 32.0;
  }
  dominant_wave_period_qc {
    Byte _FillValue -128;
    Byte actual_range 0, 40;
    Float64 colorBarMaximum 128.0;
    Float64 colorBarMinimum 0.0;
    String coordinates "time lon lat depth";
    String flag_meanings "quality_good out_of_range sensor_nonfunctional algorithm_failure_no_infl_pt";
    Byte flag_values 0, 1, 2, 3;
    String intent "data_quality";
    String ioos_category "Quality";
    String long_name "Dominant Wave Period Quality";
    String short_name "DWPQ";
    String standard_name "dominant_wave_period data_quality";
    String units "1";
    Byte valid_range -127, 127;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -67.01072, -67.01072;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 44.88791, 44.88791;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.0, 0.0;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum 0.0;
    String colorBarPalette "OceanDepth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
 }
  NC_GLOBAL {
    Int32 breakout_id 7;
    String buffer_type "accelerometer";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station, longitude, latitude";
    String comment "processed with MATLAB";
    String contact "nealp@maine.edu,ljm@umeoce.maine.edu,jevans@umeoce.maine.edu";
    String Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    String creator_email "nealp@maine.edu,ljm@umeoce.maine.edu,jevans@umeoce.maine.edu";
    String creator_name "Neal Pettigrew";
    String creator_url "http://gyre.umeoce.maine.edu/";
    String defaultGraphQuery "time,significant_wave_height&time%3E=now-7days&.draw=lines&.color=0x000000";
    Int32 delta_t 60;
    String dominant_wave_period_algorithm_id "$Id: calculate_wave_parameters.m,v 1.10 2003/02/13 21:59:04 jevans Exp $";
    Float64 Easternmost_Easting -67.01072;
    Float64 ending_julian_day_number 54440.70833333349;
    String ending_julian_day_string "2007-12-06 17:00:00";
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 44.88791;
    Float64 geospatial_lat_min 44.88791;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -67.01072;
    Float64 geospatial_lon_min -67.01072;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Fri Dec  7 07:01:16 2007: /usr/local/bin/ncrcat J02.accelerometer.historical.nc J0214.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Wed Nov 29 22:18:38 2006: /usr/local/bin/ncrcat J02.accelerometer.historical.nc J0213.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Fri May 12 16:14:32 2006: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0212.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Wed Jan 18 14:03:35 2006: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0211.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Tue Sep 27 13:37:07 2005: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0210.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Thu May 19 19:05:43 2005: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0209.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Sun Oct  3 17:11:51 2004: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0208.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Wed Aug 18 13:52:32 2004: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0207.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Wed Aug 18 13:51:37 2004: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0206.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
Sat Feb 28 18:59:52 2004: /usr/local/nco/bin/ncrcat J02.accelerometer.historical.nc J0205.accelerometer.realtime.nc J02.accelerometer.historical.nc.new
24-Sep-2003 21:16:33:  Tentatively added in J0204 data starting from julian date 2452706.79166667, 2003-3-7 19:00:00Z
Wed Sep 24 20:53:51 2003: ncrcat /data/gomoos/buoy/archive/J02/J02.accelerometer.historical.nc /data/gomoos/buoy/archive/J0204/realtime/J0204.accelerometer.realtime.nc J02.accelerometer.historical.nc
27-Jun-2003 13:02:30:  Added ancillary_variables, intent attributes for CF compliance.
Sat Feb 22 19:11:14 2003: ncrcat -v significant_wave_height,significant_wave_height_qc,dominant_wave_period,dominant_wave_period_qc J02.accelerometer.historical.nc j.nc
Sat Feb 22 19:10:12 2003: Created J02.accelerometer.historical.nc from J0202.accelerometer.raw.nc.  There was an accelerometer on J0201, but all data was bad.

2020-01-22T11:09:01Z (local files)
2020-01-22T11:09:01Z http://www.neracoos.org/tabledap/J02_accelerometer_all.das";
    String id "J02-accelerometer";
    String infoUrl "http://www.neracoos.org";
    String institution "Univ. of Maine";
    String institution_url "http://gyre.umeoce.maine.edu/";
    String julian_day_convention "Julian date convention starts at 00:00:00 UTC on 17 November 1858 AD";
    String keywords "accelerometer, agg, b01, buoy, chemistry, chlorophyll, circulation, conductivity, control, currents, data, density, department, depth, dominant, dominant_wave_period data_quality, dsg, Earth Science > Oceans > Ocean Chemistry > Chlorophyll, Earth Science > Oceans > Ocean Chemistry > Oxygen, Earth Science > Oceans > Ocean Circulation > Ocean Currents, Earth Science > Oceans > Ocean Optics > Turbidity, Earth Science > Oceans > Ocean Pressure > Sea Level Pressure, Earth Science > Oceans > Ocean Temperature > Water Temperature, Earth Science > Oceans > Ocean Waves > Significant Wave Height, Earth Science > Oceans > Ocean Waves > Swells, Earth Science > Oceans > Ocean Waves > Wave Period, Earth Science > Oceans > Ocean Winds > Surface Winds, Earth Science > Oceans > Salinity/Density > Conductivity, Earth Science > Oceans > Salinity/Density > Density, Earth Science > Oceans > Salinity/Density > Salinity, height, level, maine, marine, name, neracoos, o2, ocean, oceanography, oceans, optics, oxygen, period, physical, pressure, quality, salinity, school, sciences, sea, seawater, sensor, significant, significant_height_of_wind_and_swell_waves, significant_wave_height data_quality, station, station_name, surface, surface waves, swell, swells, temperature, time, turbidity, university, water, wave, waves, wind, winds";
    String keywords_vocabulary "GCMD Science Keywords";
    Float64 latitude 44.8879044980419;
    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 long_name "J02";
    Float64 longitude -67.0107168080855;
    Float64 magnetic_variation -18.6;
    String Metadata_Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    String mooring_site_id "J02";
    String naming_authority "edu.maine";
    Int32 nco_openmp_thread_number 1;
    String neracoos_data_provider "UMO";
    Float64 Northernmost_Northing 44.88791;
    String processing "historical";
    String project "NERACOOS";
    String project_url "http://gomoos.org";
    String publisher "NERACOOS";
    String publisher_email "info@neracoos.org";
    String publisher_name "Northeastern Regional Association of Coastal and Ocean Observing Systems (NERACOOS)";
    String publisher_phone "(603) 319 1785";
    String publisher_url "http://www.neracoos.org/";
    String references "http://gyre.umeoce.maine.edu/data/gomoos/doc/buoy_system_doc/buoy_system/book1.html";
    String short_name "J02";
    String significant_wave_height_algorithm_id "$Id: calculate_wave_parameters.m,v 1.10 2003/02/13 21:59:04 jevans Exp $";
    String source "surface observation";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.88791;
    String standard_name_vocabulary "CF-1.6";
    Float64 starting_julian_day_number 52591.66666666651;
    String starting_julian_day_string "2002-11-13 16:00:00";
    String station_name "J02";
    String subsetVariables "station, longitude, latitude, depth";
    String summary "Ocean observation data from the Northeastern Regional Association of Coastal & Ocean Observing Systems (NERACOOS). The NERACOOS region includes the northeast United States and Canadian Maritime provinces, as part of the United States Integrated Ocean Observing System (IOOS).  These data are served by Unidata's Thematic Realtime Environmental Distributed Data Services (THREDDS) Data Server (TDS) in a variety of interoperable data services and output formats.";
    String time_coverage_end "2007-12-06T17:00:00Z";
    String time_coverage_start "2002-11-13T16:00:00Z";
    String time_zone "UTC";
    String title "J02 Accelerometer - Waves";
    Float64 water_depth 32.0;
    Float64 Westernmost_Easting -67.01072;
  }
}

 

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