ERDDAP > tabledap > Data Access Form

Dataset Title:	[GP15 Iron Ligands in Particles] - Iron ligand concentration in particles (1- 51 μm) analyzed by liquid chromatography-mass spectrometry from samples collected on the US GEOTRACES Pacific Meridional Transect (PMT) cruise RR1814 (GP15) on R/V Roger Revelle in October 2018 (Trace Element Organic Speciation along the US GEOTRACES Pacific Meridional Transect)
Institution:	BCO-DMO   (Dataset ID: bcodmo_dataset_929884_v1)
Information:	Summary | License | Metadata | Background | Files | Make a graph

 

Variable	Optional Constraint #1		Optional Constraint #2		Minimum	Maximum
Sample (unitless)	!= =~ <= >= = < >		!= =~ <= >= = < >		"GT12706"	"GT13400"
Station (unitless)	!= =~ <= >= = < >		!= =~ <= >= = < >		6	14
Lat (degrees_north)	!= =~ <= >= = < >		!= =~ <= >= = < >		31.99997	51.99467
longitude (degrees_east)	!= =~ <= >= = < >		!= =~ <= >= = < >		-152.0	-151.9999
depth (m)	!= =~ <= >= = < >		!= =~ <= >= = < >		38	499
Ferrioxamine_G (picomolar (pM))	!= =~ <= >= = < >		!= =~ <= >= = < >		0.02	7.8
time (Iso_datetime_utc, UTC)	!= =~ <= >= = < >		!= =~ <= >= = < >		2018-10-01T20:35:00Z	2018-10-13T15:52:00Z

 

Server-side Functions

distinct()

orderBy orderByDescending orderByClosest orderByCount orderByLimit orderByMax orderByMin orderByMinMax orderByMean orderBySum (" Sample Station Lat longitude depth Ferrioxamine_G time Sample Station Lat longitude depth Ferrioxamine_G time Sample Station Lat longitude depth Ferrioxamine_G time Sample Station Lat longitude depth Ferrioxamine_G time Sample Station Lat longitude depth Ferrioxamine_G time ")

File type: (more information) .asc - View OPeNDAP-style ISO-8859-1 comma-separated text. .csv - Download a ISO-8859-1 comma-separated text table (line 1: names; line 2: units; ISO 8601 times). .csvp - Download a ISO-8859-1 .csv file with line 1: name (units). Times are ISO 8601 strings. .csv0 - Download a ISO-8859-1 .csv file without column names or units. Times are ISO 8601 strings. .dataTable - A JSON file formatted for use with the Google Visualization client library (Google Charts). .das - View the dataset's metadata via an ISO-8859-1 OPeNDAP Dataset Attribute Structure (DAS). .dds - View the dataset's structure via an ISO-8859-1 OPeNDAP Dataset Descriptor Structure (DDS). .dods - OPeNDAP clients use this to download the data in the DODS binary format. .esriCsv - Download a ISO_8859_1 .csv file for ESRI's ArcGIS 9.x and below (separate date and time columns). .fgdc - View the dataset's UTF-8 FGDC .xml metadata. .geoJson - Download longitude,latitude,otherColumns data as a UTF-8 GeoJSON .json file. .graph - View a Make A Graph web page. .help - View a web page with a description of tabledap. .html - View an OPeNDAP-style HTML Data Access Form. .htmlTable - View a UTF-8 .html web page with the data in a table. Times are ISO 8601 strings. .iso19115 - View the dataset's ISO 19115-2/19139 UTF-8 .xml metadata. .itx - Download an ISO-8859-1 Igor Text File. Each response column becomes a wave. .json - View a table-like UTF-8 JSON file (missing value = 'null'; times are ISO 8601 strings). .jsonlCSV1 - View a UTF-8 JSON Lines CSV file with column names on line 1 (mv = 'null'; times are ISO 8601 strings). .jsonlCSV - View a UTF-8 JSON Lines CSV file without column names (mv = 'null'; times are ISO 8601 strings). .jsonlKVP - View a UTF-8 JSON Lines file with Key:Value pairs (missing value = 'null'; times are ISO 8601 strings). .mat - Download a MATLAB binary file. .nc - Download a flat, table-like, NetCDF-3 binary file with COARDS/CF/ACDD metadata. .ncHeader - View the UTF-8 header (the metadata) for the NetCDF-3 .nc file. .ncCF - Download a NetCDF-3 CF Discrete Sampling Geometries file (Contiguous Ragged Array). .ncCFHeader - View the UTF-8 header (the metadata) for the .ncCF file. .ncCFMA - Download a NetCDF-3 CF Discrete Sampling Geometries file (Multidimensional Array). .ncCFMAHeader - View the UTF-8 header (the metadata) for the .ncCFMA file. .nccsv - Download a NetCDF-3-like 7-bit ASCII NCCSV .csv file with COARDS/CF/ACDD metadata. .nccsvMetadata - View the dataset's metadata as the top half of a 7-bit ASCII NCCSV .csv file. .ncoJson - Download a UTF-8 NCO lvl=2 JSON file with COARDS/CF/ACDD metadata. .odvTxt - Download longitude,latitude,time,otherColumns as an ISO-8859-1 ODV Generic Spreadsheet File (.txt). .subset - View an HTML form which uses faceted search to simplify picking subsets of the data. .tsv - Download a ISO-8859-1 tab-separated text table (line 1: names; line 2: units; ISO 8601 times). .tsvp - Download a ISO-8859-1 .tsv file with line 1: name (units). Times are ISO 8601 strings. .tsv0 - Download a ISO-8859-1 .tsv file without column names or units. Times are ISO 8601 strings. .wav - Download a .wav audio file. All columns must be numeric and of the same type. .xhtml - View a UTF-8 XHTML (XML) file with the data in a table. Times are ISO 8601 strings. .kml - View a .kml file, suitable for Google Earth. .smallPdf - View a small .pdf image file with a graph or map. .pdf - View a standard, medium-sized .pdf image file with a graph or map. .largePdf - View a large .pdf image file with a graph or map. .smallPng - View a small .png image file with a graph or map. .png - View a standard, medium-sized .png image file with a graph or map. .largePng - View a large .png image file with a graph or map. .transparentPng - View a .png image file (just the data, without axes, landmask, or legend).

(Documentation / Bypass this form )
 
Submit (Please be patient. It may take a while to get the data.)

 

---

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Sample {
    String long_name "Sample";
    String units "unitless";
  }
  Station {
    Int32 actual_range 6, 14;
    String long_name "Station";
    String units "unitless";
  }
  Lat {
    Float32 actual_range 31.99997, 51.99467;
    String long_name "Lat";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -152.0, -151.9999;
    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";
    Int32 actual_range 38, 499;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Ferrioxamine_G {
    Float32 actual_range 0.02, 7.8;
    String long_name "Ferrioxamine_g";
    String units "picomolar (pM)";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5384261e+9, 1.53944592e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String defaultDataQuery "&time<now";
    String doi "10.26008/1912/bco-dmo.929884.1";
    Float64 Easternmost_Easting -151.9999;
    Float64 geospatial_lon_max -151.9999;
    Float64 geospatial_lon_min -152.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 499.0;
    Float64 geospatial_vertical_min 38.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-12-30T18:01:17Z (local files)
2024-12-30T18:01:17Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_929884_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/929884";
    String institution "BCO-DMO";
    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 sourceUrl "(local files)";
    String summary "This dataset includes iron ligand concentration in particles (1-51 μm) analyzed by liquid chromatography-mass spectrometry. Samples were collected on the US GEOTRACES Pacific Meridional Transect (PMT) cruises (GP15, RR1814 & RR1815) on R/V Roger Revelle from September to November 2018.";
    String time_coverage_end "2018-10-13T15:52:00Z";
    String time_coverage_start "2018-10-01T20:35:00Z";
    String title "[GP15 Iron Ligands in Particles] - Iron ligand concentration in particles (1-51 μm) analyzed by liquid chromatography-mass spectrometry from samples collected on the US GEOTRACES Pacific Meridional Transect (PMT) cruise RR1814 (GP15) on R/V Roger Revelle in October 2018 (Trace Element Organic Speciation along the US GEOTRACES Pacific Meridional Transect)";
    Float64 Westernmost_Easting -152.0;
  }
}

 

---

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 Data Access Protocol (DAP) and its selection constraints.

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