USGS Coastal and Marine Geology Program ERDDAP
Easier access to scientific data
   
Brought to you by USGS CMHRP    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Time-series oceanographic data from the Monterey Canyon, CA October 2015,
March 2017, CCE15M1A01tu
Subscribe RSS
Institution:  USGS Coastal and Marine Geology Program   (Dataset ID: CCE15M1A01tu)
Range: longitude = -121.8446 to -121.8446°E, latitude = 36.79328 to 36.79328°N, depth = 203.9 to 203.9m, time = 2015-10-06T17:15:00Z to 2016-01-17T00:00:00Z
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.4441517e+9, 1.4529888e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "time of measurement";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 36.79328, 36.79328;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    Float64 epic_code 500.0;
    String ioos_category "Location";
    String long_name "sensor latitude";
    String standard_name "latitude";
    String type "EVEN";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -121.8446, -121.8446;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    Float64 epic_code 502.0;
    String ioos_category "Location";
    String long_name "sensor longitude";
    String standard_name "longitude";
    String type "EVEN";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 actual_range 203.89999999999998, 203.89999999999998;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    Float64 epic_code 3.0;
    Float64 initial_sensor_height 65.0;
    String ioos_category "Location";
    String long_name "mean water depth";
    String positive "down";
    String source_name "z";
    String standard_name "depth";
    String type "EVEN";
    String units "m";
  }
  Trb_980 {
    Float64 _FillValue NaN;
    Float64 actual_range 2.3486401, 1662.3323609;
    String coverage_content_type "physicalMeasurement";
    Float64 epic_code 980.0;
    Float64 initial_sensor_height 65.0;
    String ioos_category "Unknown";
    String long_name "TURBIDITY (NTU)";
    String name "trb";
    String sensor_manufacturer "Seapoint";
    String sensor_type "Seapoint Turbidity Meter";
    Float64 serial_number 14960.0;
    String standard_name "sea_water_turbidity";
    String units "NTU";
  }
  feature_type_instance {
    String cf_role "timeseries_id";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Identifier";
    String long_name "Feature Type Instance";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.7.4,hdf5=1.10.6";
    String basefilename "054170_20160418_1309";
    String cdfFilename "CCE15M1A01Tu.nc";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "feature_type_instance, latitude, longitude";
    Float64 clkerr 22.0;
    String CollaboratingAgency "MBARI NERC-UK";
    String Conventions "CF-1.6, ACDD-1.3, COARDS";
    String COORD_SYSTEM "GEOGRAPHIC";
    String creation_date "27-Mar-2018 12:19:56";
    String creator_name "USGS Coastal and Marine Geology Program";
    String creator_type "institution";
    String creator_url "https://www.usgs.gov/";
    String CruiseID "2015-619-FA";
    String DATA_CMNT "CCE 2015 Site MS1 Top RBR Virtuoso-Tu on ADCP Sphere";
    String DATA_ORIGIN "USGS/PCMSC";
    String DATA_SUBTYPE "MOORED";
    String DATA_TYPE "TIME";
    String datasetID "CCE15M1A01tu";
    String date_created "2018-03-27T12:19:56Z";
    String Deployment_date "06-Oct-2015 17:15";
    String DESCRIPTION "300m mooring";
    Float64 Easternmost_Easting -121.8446;
    String EXPERIMENT "CCE";
    String experiment_id "CCE15";
    String featureType "TimeSeries";
    Float64 FILL_FLAG 1.0e+35;
    Float64 geospatial_lat_max 36.79328;
    Float64 geospatial_lat_min 36.79328;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -121.8446;
    Float64 geospatial_lon_min -121.8446;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 203.89999999999998;
    Float64 geospatial_vertical_min 203.89999999999998;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Imported from ScienceBase data release and converted to CF using process_F7FT8J7Q.ipynb;
2024-02-21T19:06:31Z (local files)
2024-02-21T19:06:31Z https://geoport.usgs.esipfed.org/tabledap/CCE15M1A01tu.das";
    String id "CCE15M1A01tu";
    String infoUrl "https://doi.org/10.5066/F7FT8J7Q";
    Float64 initial_instrument_height 65.0;
    String INST_TYPE "RBR Virtuoso Turbidity Logger";
    String institution "USGS Coastal and Marine Geology Program";
    String instrument_number "CCE15M1A01";
    Float64 interval 60.0;
    String keywords "canyon, cce15m1a01tu, coastal, data, depth, feature, feature_type_instance, geological, geology, identifier, instance, latitude, longitude, marine, measurement, monterey, nephelometric, ntu, oceanographic, oceanography, program, sea, sea_water_turbidity, seawater, sediment transport, sensor, series, states, survey, time, time-series, Trb_980, turbidity, type, united, units, usgs, water";
    Float64 latitude 36.79328;
    String LatLonDatum "NAD83";
    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 loggerType "Virtuoso";
    Float64 longitude -121.8446;
    Float64 magnetic_variation 13.4;
    String metadata_link "https://doi.org/10.5066/F7FT8J7Q";
    String metafile_author "Joanne Ferreira, USGS PCMSC";
    Float64 metafile_version 1.0;
    String mode "average";
    String MOORING "CCE15M1A";
    String naming_authority "gov.usgs.cmgp";
    Float64 nominal_instrument_depth 203.89999999999998;
    Float64 Northernmost_Northing 36.79328;
    Float64 number_of_samples 147286.0;
    String platform_type "Subsurface";
    String program "Sediment Transport in Coastal Environments";
    String project "CMG_Portal";
    String publisher_url "https://www.usgs.gov/";
    String raw_filename "054170_20160418_1309.rsk";
    String Recovery_date "17-Jan-2016 00:00";
    String Region "Monterey Bay";
    Float64 sampling_count 3.0;
    Float64 sampling_gain_applied 1.0;
    String sampling_mode "average";
    Float64 sampling_period 1.0;
    Float64 sampling_range 2500.0;
    String sampling_range_mode "Manual";
    String SciPi "Katie Coble, Kurt Rosenberger";
    Float64 Seapoint_serial_number 14960.0;
    Float64 serial_number 54170.0;
    String Site "MS1";
    String source "USGS";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 36.79328;
    String standard_name_vocabulary "CF Standard Name Table v66";
    String subsetVariables "latitude, longitude, depth, feature_type_instance";
    String summary 
"Time-series oceanographic data from the Monterey Canyon, CA October 2015 - March 2017 - CCE15M1A01tu. Time-series data of water depth, velocity, turbidity, and temperature were acquired between 5 October 2015 and 21 March 2017 within the Monterey Canyon off of Monterey, CA, USA.

In order to better understand the triggering, progression and evolution of turbidity currents in Monterey Submarine Canyon, an experiment was designed to directly measure velocity, suspended sediment and physical water properties (temperature, salinity and density) along the canyon axis during an 18-month period.

Three moorings in the upper canyon (MS1, MS2, MS3) containing oceanographic instruments and Anderson- type sediment traps were deployed during three consecutive six-month periods (A: October 2015 - April 2016; B: April - October 2016; C: October 2016 - March 2017). In addition, a bottom platform to the South of the canyon head (MS0) housed instrumentation to measure currents and waves on the adjacent shelf. The mooring diagram image files are a generalized representation of the deployed instrumentation at each site, and are included as a visual aid for understanding the sampling environment. A text file of the specific sensors listing the parameters measured is also included.";
    String time_coverage_duration "P102DT6H45M0S";
    String time_coverage_end "2016-01-17T00:00:00Z";
    String time_coverage_resolution "P0DT0H1M0S";
    String time_coverage_start "2015-10-06T17:15:00Z";
    String title "Time-series oceanographic data from the Monterey Canyon, CA October 2015, March 2017, CCE15M1A01tu";
    String txt_filename "054170_20160418_1309_data.txt";
    Float64 WATER_DEPTH 268.9;
    String WATER_DEPTH_SOURCE "MBARI Multibeam Bathy";
    Float64 Westernmost_Easting -121.8446;
  }
}

 

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