EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in    
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Mobile gears: Oceanographic data from fishing vessels Subscribe RSS
Institution:  Berring Data Collective   (Dataset ID: BDC_MobileGear_FV_NRT)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 time (Datetime, UTC) ?          2019-01-10T04:41:08Z    2020-07-10T03:55:51Z
  < slider >
 latitude (degrees_north) ?          40.7016    72.8148
  < slider >
 longitude (degrees_east) ?          -179.964    177.143
  < slider >
 depth (m) ?          1.001    601.79
  < slider >
 temperature (degree_C) ?          -1.275    26.302
 salinity (PSU) ?          16.897    35.991
 sensor_type ?      
   - +  ?
 vessel_gear_type ?      
   - +  ?
 data_collection_program ?      
   - +  ?
 vessel_id ?          1    62
 tow_id ?          133    12945
 segment_type ?      
   - +  ?
 DOI (Digital Object Identifier) ?      
   - +  ?
 
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.547095268e+9, 1.594353351e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetime";
    String source_name "datetime";
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 40.7016, 72.8148;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -179.964, 177.143;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1.001, 601.79;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  temperature {
    Float32 _FillValue NaN;
    Float32 actual_range -1.275, 26.302;
    Float64 colorBarMaximum 25.0;
    Float64 colorBarMinimum -4.0;
    String ioos_category "Temperature";
    String long_name "Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  }
  salinity {
    Float32 _FillValue NaN;
    Float32 actual_range 16.897, 35.991;
    Float64 colorBarMaximum 36.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "Sea Water Practical Salinity";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  sensor_type {
    String conventions "SensorML";
    String ioos_category "Unknown";
    String long_name "Sensor Type";
    String metadata_link "https://berringdatacollective.com/oceanography/";
  }
  vessel_gear_type {
    String conventions "ISSCFG";
    String ioos_category "Unknown";
    String long_name "Fishing Gear Used as a Sensor Platform";
    String metadata_link "http://www.fao.org/3/a-bt987e.pdf";
  }
  data_collection_program {
    String ioos_category "Unknown";
    String long_name "Data Collection Program or Industry Body";
  }
  vessel_id {
    Int32 actual_range 1, 62;
    String ioos_category "Identifier";
    String long_name "Confidential Unique Vessel Identifier";
  }
  tow_id {
    Int32 actual_range 133, 12945;
    String ioos_category "Identifier";
    String long_name "Unique Fishing Operation Identifier";
  }
  segment_type {
    String conventions "Fishing: bottom data; Profiling Down: gear being set; Profiling Up; gear being hauled";
    String ioos_category "Unknown";
    String long_name "Fishing Stage When Data is Collected";
    String metadata_link "https://berringdatacollective.com/oceanography/";
  }
  DOI {
    String ioos_category "Unknown";
    String long_name "Digital Object Identifier";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, ISSCFG, NCCSV-1.0";
    Float64 Easternmost_Easting 177.143;
    String featureType "Point";
    Float64 geospatial_lat_max 72.8148;
    Float64 geospatial_lat_min 40.7016;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 177.143;
    Float64 geospatial_lon_min -179.964;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 601.79;
    Float64 geospatial_vertical_min 1.001;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2020-09-26T21:58:36Z (local files)
2020-09-26T21:58:36Z https://erddap.emodnet-physics.eu/erddap/tabledap/BDC_MobileGear_FV_NRT.html";
    String infoUrl "https://berringdatacollective.com/oceanography/";
    String institution "Berring Data Collective";
    String keywords "arctic, citizen science, citizen_science, data, Earth Science > Oceans > Salinity/Density > Salinity, fish, fishing, gear, in-situ, industry, latitude, longitude, ocean, pressure, profile, program, salinity, science, sea, sea_water_practical_salinity, seawater, segment, sensor, situ, temperature, time, type, vessel, vessel_gear_type, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "The data are intended as a sample and may not be used or distributed for operational, scientific, or commercial purposes without prior consent by Berring Data Collective, ApS";
    Float64 Northernmost_Northing 72.8148;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.7016;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "sensor_type, vessel_gear_type, data_collection_program, segment_type, DOI";
    String summary "Ocean data collected via mobile gear fishing vessels. Location changes over a fishing operation; each tow is ananogous to a glider dive. Aggregated from both science and industry programs. Basic QC routine has been applied, all flagged data is removed.";
    String time_coverage_end "2020-07-10T03:55:51Z";
    String time_coverage_start "2019-01-10T04:41:08Z";
    String title "Mobile gears: Oceanographic data from fishing vessels";
    Float64 Westernmost_Easting -179.964;
  }
}

 

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