BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Profiling float surface dates, times and locations from the Sargasso Sea from
2013 to 2014.
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_728359)
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 deployment (unitless) ?          "B295"    "F034"
 date (unitless) ?          "2013/07/06"    "2014/11/24"
 time2 (Time, unitless) ?          "10:26"    "9:59"
 latitude (degrees_north) ?          28.4094    34.5731
  < slider >
 longitude (degrees_east) ?          -69.025    -61.3763
  < slider >
 time (ISO Date Time UTC, UTC) ?          2013-07-06T19:50:00Z    2014-11-24T03:39:00Z
  < slider >
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more info)

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


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  deployment {
    String bcodmo_name "unknown";
    String description "Deployment numbers for two Sea-Bird Scientific Navis BGCi floats. For short-term deployments (1.5-3 days), the BATS cruise number from which the float was deployed. For long-term deployments, the serial number of the float (F033 or F034).";
    String long_name "Deployment";
    String units "unitless";
  }
  date {
    String bcodmo_name "date";
    String description "Date of surface GPS fix; yyyy/mm/dd.";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String time_precision "1970-01-01";
    String units "unitless";
  }
  time2 {
    String bcodmo_name "time";
    String description "Time of surface GPS fix.";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 28.4094, 34.5731;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Latitude";
    String ioos_category "Location";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -69.025, -61.3763;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Longitude";
    String ioos_category "Location";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.3731402e+9, 1.41680034e+9;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "DateTime; ISO UTC formatted";
    String ioos_category "Time";
    String long_name "ISO Date Time UTC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/DTUT8601/";
    String source_name "ISO_DateTime_UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description "Profiling float surface dates, times and locations from the Sargasso Sea.";
    String awards_0_award_nid "644826";
    String awards_0_award_number "OCE-1406552";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1406552";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "Henrietta N Edmonds";
    String awards_0_program_manager_nid "51517";
    String cdm_data_type "Other";
    String comment 
"Deployment Locations and Times 
  M. Estapa and K. Buesseler, PIs 
  Version 26 February 2018";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.3  19 Dec 2019";
    String date_created "2018-02-26T20:24:29Z";
    String date_modified "2018-09-19T19:26:19Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.734354";
    Float64 Easternmost_Easting -61.3763;
    Float64 geospatial_lat_max 34.5731;
    Float64 geospatial_lat_min 28.4094;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -61.3763;
    Float64 geospatial_lon_min -69.025;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-20T00:46:26Z (local files)
2024-04-20T00:46:26Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_728359.html";
    String infoUrl "https://www.bco-dmo.org/dataset/728359";
    String institution "BCO-DMO";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, date, deployment, dmo, erddap, iso, latitude, longitude, management, oceanography, office, preliminary, time, time2";
    String license "https://www.bco-dmo.org/dataset/728359/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/728359";
    Float64 Northernmost_Northing 34.5731;
    String param_mapping "{'728359': {'lat': 'master - latitude', 'lon': 'master - longitude', 'ISO_DateTime_UTC': 'master - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/728359/parameters";
    String people_0_affiliation "Skidmore College";
    String people_0_person_name "Margaret L. Estapa";
    String people_0_person_nid "644830";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Woods Hole Oceanographic Institution";
    String people_1_affiliation_acronym "WHOI";
    String people_1_person_name "Kenneth O. Buesseler";
    String people_1_person_nid "50522";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Skidmore College";
    String people_2_person_name "Margaret L. Estapa";
    String people_2_person_nid "644830";
    String people_2_role "Contact";
    String people_2_role_type "related";
    String people_3_affiliation "Woods Hole Oceanographic Institution";
    String people_3_affiliation_acronym "WHOI BCO-DMO";
    String people_3_person_name "Hannah Ake";
    String people_3_person_nid "650173";
    String people_3_role "BCO-DMO Data Manager";
    String people_3_role_type "related";
    String project "RapAutParticleFlux";
    String projects_0_acronym "RapAutParticleFlux";
    String projects_0_description 
"Particles settling into the deep ocean remove carbon and biologically-important trace elements from sunlit, productive surface waters and from contact with the atmosphere over short timescales. A shifting balance among physical, chemical, and biological processes determines the ultimate fate of most particles at depths between 100 and 1,000 m, where fluxes are hardest to measure. Our challenge is to expand the number of particle flux observations in the critical \"twilight zone\", something that has proven elusive with ship-based “snapshots” that have lengths of, at most, a few weeks. Here, we propose an optical, transmissometer-based method to make particle flux observations from autonomous, biogeochemical profiling floats. Novel developments in data interpretation, sensor operation, and platform control now allow flux measurements at hourly resolution and give us observational access to the water-column processes driving particle flux over short timescales. The sensors and float platforms that we propose to use are simple, robust, and commercially-available, making them immediately compatible with community-scale efforts to implement other float-based biogeochemical measurements.
We have two main goals:  First, we will quantify particulate organic carbon (POC) flux using float-based optical measurements by validating our observations against fluxes measured directly with neutrally-buoyant, drifting sediment traps. Second, we will evaluate the contribution of rapid export events to total POC fluxes in the oligotrophic ocean by using a biogeochemical profiling float to collect nearly-continuous, depth-resolved flux measurements and coupled, water-column bio-optical profiles. 
To achieve these goals, we will implement a work plan consisting of 1) a set of laboratory-based sensor calibration experiments to determine detection limits and evaluate sensitivity to particle size; 2) a series of four sediment trap and biogeochemical float co-deployments during which we will collect POC flux and field calibration data; and 3) a long-term sampling and analysis period (approximately 1 year) during which data will be returned by satellite from the biogeochemical float. We will conduct calibration fieldwork in conjunction with monthly Bermuda Atlantic Time-series Study (BATS) cruises, taking advantage of the timeseries measurements and the context provided by the 25-year record of POC flux at that site. The data returned by the float will comprise the first quantitative particle flux observations made at high-enough temporal resolution to interpret in the context of short-term, upper-ocean production events.";
    String projects_0_end_date "2014-11";
    String projects_0_geolocation "Sargasso Sea";
    String projects_0_name "Rapid, Autonomous Particle Flux Observations in the Oligotrophic Ocean";
    String projects_0_project_nid "644827";
    String projects_0_start_date "2013-07";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 28.4094;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Optical proxy measurements of sinking particle flux and water-column bio-optical profiles were obtained from profiling floats in the Sargasso Sea to expand the number of particle flux observations in the critical and under-sampled \\u201ctwilight zone\\u201d.  A typical float cycle consisted of the descent to the target park depth, a park phase at the target depth which cycled among depths ranging 150-1000 m, a descent to 1000 m, an ascent to the surface during which measurements are made, and a surface telemetry phase, during which a GPS fix is obtained. Dates, times, and locations obtained during the surface telemetry phase are provided.";
    String time_coverage_end "2014-11-24T03:39:00Z";
    String time_coverage_start "2013-07-06T19:50:00Z";
    String title "Profiling float surface dates, times and locations from the Sargasso Sea from 2013 to 2014.";
    String version "1";
    Float64 Westernmost_Easting -69.025;
    String xml_source "osprey2erddap.update_xml() v1.3";
  }
}

 

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