Ifremer ERDDAP
Easier access to scientific data

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Bioice Station list Subscribe RSS
Institution:  LifeWatch ERIC   (Dataset ID: BIOICE_station_list)
Range: longitude = 60.0335 to 69.25683°E, latitude = -30.115 to -6.191°N, time = 1991-07-01T00:00:00Z to 2004-07-25T00:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
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.")
Graph Settings
Marker Type:   Size: 
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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  bioice_sample_number {
    Int32 actual_range 2000, 3670;
  cruise_id {
  cruise_station_number {
    Int32 actual_range 1, 9901;
  sampling_gear {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 6.783264e+8, 1.0907136e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String max_value "2004-07-25";
    String min_value "1991-07-01";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  local_time_at_start_of_tow {
  latitute_at_start_of_tow_degr {
    Int32 actual_range 600201, 691541;
  longitute_at_start_of_tow_degr {
    Int32 actual_range 61146, 300690;
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 60.0335, 69.25683;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -30.115, -6.191;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  depth_m_start_of_tow {
  local_time_at_end_of_tow {
  latitute_at_end_of_tow_degr {
    Float32 actual_range 600229.0, 691534.0;
  longitute_at_end_of_tow_degr {
  latitute_at_end_of_tow_desimal {
    Float32 actual_range 60.03817, 69.25567;
  longitute_at_end_of_tow_desimal {
    Float32 actual_range -30.09833, -6.197833;
  coordinateuncertaintyinmeters {
    Float32 actual_range 1000.0, 1000.0;
  depth_m_end_of_tow {
    Float32 actual_range 18.0, 3007.0;
  bottom_temp_c {
  salinity_ppm {
    Float32 actual_range 33.97, 35.2;
  description_of_substrate {
  smell_of_sulphur {
  sample_volume_liters {
    Float32 actual_range 0.0, 3000.0;
  volume_sieved_liters {
    Float32 actual_range 0.0, 200.0;
  volume_picked_liters {
    Float32 actual_range 0.0, 3000.0;
  comments_on_sample {
    String cdm_data_type "Point";
    Float64 Easternmost_Easting 69.25683;
    String featureType "Point";
    Float64 geospatial_lat_max -6.191;
    Float64 geospatial_lat_min -30.115;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 69.25683;
    Float64 geospatial_lon_min 60.0335;
    String geospatial_lon_units "degrees_east";
    String history 
"2022-08-10T20:35:43Z marinedataarchive.org
2022-08-10T20:35:43Z http://www.ifremer.fr/tabledap/BIOICE_station_list.das";
    String infoUrl "https://www.lifewatch.eu/";
    String institution "LifeWatch ERIC";
    String keywords "bioice, station";
    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.";
    Float64 Northernmost_Northing -6.191;
    String sourceUrl "marinedataarchive.org";
    Float64 Southernmost_Northing -30.115;
    String subsetVariables "cruise_id,cruise_station_number,sampling_gear,description_of_substrate,smell_of_sulphur";
    String summary "BioIce Station list dataset example. Data extracted from the Marine Data Archive.";
    String time_coverage_end "2004-07-25T00:00:00Z";
    String time_coverage_start "1991-07-01T00:00:00Z";
    String title "Bioice Station list";
    Float64 Westernmost_Easting 60.0335;


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
For example,
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