Easy Access to PMEL Scientific Data
The Pacific Marine Environmental Laboratory's ERDDAP data server for public access to scientific data

NOAA OAR PMEL

Make A Graph

Dataset Title:	Saildrone 2019 Arctic Flux Data
Institution:	NOAA PMEL (Dataset ID: saildrone_2019_arctic_flux)
Range:	longitude = -178.93831 to -146.13472°E, latitude = 53.84473 to 75.49652°N, time = 2019-05-14T14:10:00Z to 2019-10-12T01:50:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| Data Access Form \| Files

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 {
  ID {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "ID";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.557843e+9, 1.570845e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "T10 MIN";
    String source_name "T10MIN";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -178.93830784, -146.1347168;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String history "From /home/ibis11/zhang/Arctic2019/saildrone_arctic_2019_1041f.nc";
    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.84473024, 75.4965248;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String history "From /home/ibis11/zhang/Arctic2019/saildrone_arctic_2019_1041f.nc";
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value -1.0e+34;
    String standard_name "latitude";
    String units "degrees_north";
  }
  QS {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -77.159, 131.799;
    String history "From Arctic2019UQTadjSD1041fIce";
    String long_name "Q sensible";
    Float64 missing_value -1.0e+34;
    String units "W/m2";
  }
  QL {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range -66.918, 137.096;
    String history "From Arctic2019UQTadjSD1041fIce";
    String long_name "Q latent";
    Float64 missing_value -1.0e+34;
    String units "W/m2";
  }
  TAU {
    Float64 _FillValue -1.0e+34;
    Float64 actual_range 0.0, 1.132;
    String history "From Arctic2019UQTadjSD1041fIce";
    String long_name "Tau";
    Float64 missing_value -1.0e+34;
    String units "N/m2";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "ID";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_email "pmel.info@noaa.gov";
    String creator_name "NOAA PMEL";
    String creator_type "institution";
    String creator_url "https://www.pmel.noaa.gov/";
    Float64 Easternmost_Easting -146.1347168;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 75.4965248;
    Float64 geospatial_lat_min 53.84473024;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -146.1347168;
    Float64 geospatial_lon_min -178.93830784;
    String geospatial_lon_units "degrees_east";
    String history 
"PyFerret V7.5 (optimized) 15-Sep-20
2024-12-11T16:22:39Z (local files)
2024-12-11T16:22:39Z https://data.pmel.noaa.gov/pmel/tabledap/saildrone_2019_arctic_flux.das";
    String infoUrl "https://www.pmel.noaa.gov/";
    String institution "NOAA PMEL";
    String keywords "data, environmental, flux, laboratory, latent, latitude, longitude, marine, min, noaa, pacific, pmel, saildrone, sensible, t10, tau, time";
    String license "These data were produced by NOAA and are not subject to copyright protection in the United States. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0-1.0).";
    String NCO "netCDF Operators version 4.7.5 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 75.4965248;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 53.84473024;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "ID";
    String summary "Saildrone 2019 Arctic Flux Data. NOAA Pacific Marine Environmental Laboratory (PMEL) data from a local source.";
    String time_coverage_end "2019-10-12T01:50:00Z";
    String time_coverage_start "2019-05-14T14:10:00Z";
    String title "Saildrone 2019 Arctic Flux Data";
    Float64 Westernmost_Easting -178.93830784;
  }
}

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