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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Saildrone SD1021 ADCP Subscribe RSS
Institution:  NOAA/PMEL   (Dataset ID: sd1021_adcp_arctic_2018)
Range: longitude = -169.1138 to -158.38324°E, latitude = 53.844406 to 72.99612°N, depth = 6.0 to 104.0m, time = 2018-06-30T19:59:58Z to 2018-10-06T23:29:58Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
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 {
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 actual_range 6.0, 104.0;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "depth of each measurement";
    String point_spacing "even";
    String positive "down";
    String source_name "DEPTH_ADCP";
    String standard_name "depth";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.530388798e+9, 1.538868598e+9;
    String axis "T";
    String calendar "GREGORIAN";
    String ioos_category "Time";
    String long_name "Time";
    String point_spacing "even";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  U {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -84.900286421769, 104.609306762946;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String history "From sd1021adcp";
    String long_name "uadcp";
    Float64 missing_value -1.0e+34;
    String standard_name "eastward_sea_water_velocity";
    String units "cm s-1";
  }
  V {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -156.793553049975, 121.400001525879;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String history "From sd1021adcp";
    String long_name "vadcp";
    Float64 missing_value -1.0e+34;
    String standard_name "northward_sea_water_velocity";
    String units "cm s-1";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -169.113803204734, -158.383245380436;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String history "From sd1021adcp";
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 missing_value -1.0e+34;
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue -1.0e+34;
    Float64 actual_range 53.8444061111659, 72.9961165656452;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String history "From sd1021adcp";
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value -1.0e+34;
    String standard_name "latitude";
    String units "degrees_north";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String drone_id "1021";
    Float64 Easternmost_Easting -158.383245380436;
    String featureType "Point";
    Float64 geospatial_lat_max 72.9961165656452;
    Float64 geospatial_lat_min 53.8444061111659;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -158.383245380436;
    Float64 geospatial_lon_min -169.113803204734;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 104.0;
    Float64 geospatial_vertical_min 6.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"Saildrone
2024-04-18T10:09:15Z (local files)
2024-04-18T10:09:15Z https://data.pmel.noaa.gov/pmel/tabledap/sd1021_adcp_arctic_2018.das";
    String infoUrl "www.pmel.noaa.gov";
    String institution "NOAA/PMEL";
    String keywords "acoustic, adcp, circulation, current, currents, data, depth, doppler, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, eastward, eastward_sea_water_velocity, environmental, laboratory, latitude, longitude, marine, noaa, northward, northward_sea_water_velocity, ocean, oceans, pacific, pmel, profiler, saildrone, science, sd1021, sea, seawater, time, uadcp, vadcp, velocity, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"Data Licenses / Data Usage Restrictions
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.

Unless otherwise noted, data served through this ERDDAP server are 
not quality controlled.  Users may need to do quality control when using 
these data. These data are made available at the users own risk.";
    Float64 Northernmost_Northing 72.9961165656452;
    String platform "Saildrone";
    String principal_investigator "Dr. Jessica Cross; Dr. Dongxiao Zhang";
    String principal_investigator_email "jessica.cross@noaa.gov; dongxiao.zhang@noaa.gov";
    String principal_investigator_institution "NOAA PMEL and CICOES/University of Washington";
    String project "arctic_2018";
    String QC_indicator "Level 1";
    String qc_manual "QC Performed: motion corrected";
    String source "Saildrone";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 53.8444061111659;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Acoustic Doppler Current Profiler (ADCP) currents measured by SD1021 during the Pacific Marine Environmental Laboratory (PMEL) Arctic 2018 Saildrone Mission";
    String time_coverage_end "2018-10-06T23:29:58Z";
    String time_coverage_start "2018-06-30T19:59:58Z";
    String title "Saildrone SD1021 ADCP";
    Float64 Westernmost_Easting -169.113803204734;
  }
}

 

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