SO-CHIC ERDDAP
Easier access to scientific data
   
Brought to you by SO-CHIC    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  SOOS - Epipelagic mesozooplankton distribution and abundance in Southern Ocean Subscribe RSS
Institution:  British Antarctic Survey   (Dataset ID: BONGO_NETS)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Net ?          "Bongo 100"    "Bongo 50"
 Maxdepth ?          50    400
 Cruise_name ?          "JR19960103"    "JR20130109"
 Event_name ?          "JR100_Bongo02"    "JR82_Bongo170"
 time (Start Of Event, UTC) ?              
 latitude (degrees_north) ?          -65.1285    79.05749
  < slider >
 longitude (degrees_east) ?          -69.28211    26.06155
  < slider >
 End_of_event ?          "01/01/2001 04:27"    "31/12/2004 08:52"
 Taxon_name ?          "Acartia clausi"    "jelly mass"
 Taxon_class ?          "C1"    "zoeae"
 Abundance (Abundance (m-2)) ?          0.0    1664638.72
 Scientist ?          "Peter Ward"    "Rachel Shreeve/Pet..."
 
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 information)

(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 {
  Net {
    String long_name "Net";
  }
  Maxdepth {
    Int16 actual_range 50, 400;
    String long_name "Maxdepth";
  }
  Cruise_name {
    String long_name "Cruise Name (click For Details)";
  }
  Event_name {
    String long_name "Event Name";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Start Of Event";
    String source_name "Start_of_event";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -65.1285, 79.05749;
    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 -69.28211, 26.06155;
    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";
  }
  End_of_event {
    String long_name "End Of Event";
    String source_name "End_of_event";
  }
  Taxon_name {
    String long_name "Taxon Name";
  }
  Taxon_class {
    String long_name "Taxon Class";
  }
  Abundance {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 1664638.72;
    String long_name "Abundance (m-2)";
  }
  Scientist {
    String long_name "Scientist";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "British Antarctic Survey";
    String creator_url "https://data.bas.ac.uk/metadata.php?id=GB/NERC/BAS/PDC/01316";
    Float64 Easternmost_Easting 26.06155;
    String featureType "Point";
    Float64 geospatial_lat_max 79.05749;
    Float64 geospatial_lat_min -65.1285;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 26.06155;
    Float64 geospatial_lon_min -69.28211;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-12-22T21:36:49Z (local files)
2024-12-22T21:36:49Z https://erddap.sochic-h2020.eu/erddap/tabledap/BONGO_NETS.html";
    String infoUrl "https://data.bas.ac.uk/metadata.php?id=GB/NERC/BAS/PDC/01316";
    String institution "British Antarctic Survey";
    String keywords "abundance, antarctic, array, array-data, british, class, click, comprehensive, cruise, Cruise_name, data, details, distribution, end, End_lat, End_lon, End_of_event, epipelagic, event, Event_name, large, latitude, longitude, m-2, maxdepth, mesozooplankton, name, net, ocean, scientist, southern, start, stewardship, survey, system, taxon, Taxon_class, Taxon_name, time";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    Float64 Northernmost_Northing 79.05749;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -65.1285;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Mesozooplankton were collected with a motion-compensated Bongo net (61 cm mouth diameter, 100 and 200 micrometre meshes) and a mini- Bongo net (18 cm mouth diameter, 50 micrometre mesh nets). Both nets fished to a maximum depth of 400 m but sometimes shallower. Specimens were categorised to the lowest possible taxonomic level, which in some cases encompassed developmental stages but in other cases was limited to higher order taxa. Each taxa was enumerated to determine abundance in units of individuals m-2. The dataset allows examination of the distribution and abundance of these species within the Atlantic sector of the Southern Ocean over a number of years and covering much of the productive season from spring to autumn. The data for the North Atlantic and Arctic covers one season only (summer) and is limited to providing a spatial perspective on the distribution and abundance of mesozooplankton.";
    String title "SOOS - Epipelagic mesozooplankton distribution and abundance in Southern Ocean";
    Float64 Westernmost_Easting -69.28211;
  }
}

 

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