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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [GP17-OCE Event Log] - Scientific sampling event log from the US GEOTRACES
GP17-OCE cruise on R/V Roger Revelle (RR2214) from December 2022 to January
2023 (US GEOTRACES GP17 Section: South Pacific and Southern Ocean (GP17-OCE))
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_927550_v1)
Range: longitude = -152.0003 to -73.51437°E, latitude = -67.00984 to -17.53652°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
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: 
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.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
Zoom: 
[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 {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  Event {
    String long_name "Event";
    String units "unitless";
  }
  Instrument {
    String long_name "Instrument";
    String units "unitless";
  }
  Action {
    String long_name "Action";
    String units "unitless";
  }
  Transect {
    String long_name "Transect";
    String units "unitless";
  }
  Station {
    String long_name "Station";
    String units "unitless";
  }
  Cast {
    Int32 actual_range 0, 14;
    String long_name "Cast";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -67.00984, -17.53652;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -152.0003, -73.51437;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  sample_depth_min {
    Int32 actual_range 0, 3300;
    String long_name "Sample_depth_min";
    String units "m";
  }
  sample_depth_max {
    Int32 actual_range 1, 17345;
    String long_name "Sample_depth_max";
    String units "m";
  }
  GEOTRACES_ID_Num_Range {
    String long_name "Geotraces_id_num_range";
    String units "unitless";
  }
  Seafloor {
    String long_name "Seafloor";
    String units "meters (m)";
  }
  Author {
    String long_name "Author";
    String units "unitless";
  }
  Comment {
    String long_name "Comment";
    String units "unitless";
  }
  DateTimeUTC {
    String long_name "Datetimeutc";
    String units "unitless";
  }
  ISO_DateTime_UTC {
    Float64 actual_range 1.66963374e+9, 1.67457138e+9;
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  GPS_Time {
    Float64 actual_range 1.66963374e+9, 1.67457138e+9;
    String ioos_category "Time";
    String long_name "Gps_time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Revisions {
    String long_name "Revisions";
    String units "unitless";
  }
 }
  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 doi "10.26008/1912/bco-dmo.927550.1";
    Float64 Easternmost_Easting -73.51437;
    Float64 geospatial_lat_max -17.53652;
    Float64 geospatial_lat_min -67.00984;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -73.51437;
    Float64 geospatial_lon_min -152.0003;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:03:33Z (local files)
2024-11-08T06:03:33Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_927550_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/927550";
    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.";
    Float64 Northernmost_Northing -17.53652;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -67.00984;
    String summary "This dataset is the scientific sampling event log from the US GEOTRACES GP17-OCE cruise on R/V Roger Revelle (RR2214). The expedition departed Papeete, Tahiti (French Polynesia) on December 1st, 2022 and arrived in Punta Arenas, Chile on January 25th, 2023. The cruise took place in the South Pacific and Southern Oceans aboard the R/V Roger Revelle with a team of 34 scientists led by Ben Twining (Chief Scientist), Jessica Fitzsimmons, and Greg Cutter (Co-Chief Scientists). GP17 was planned as a two-leg expedition, with its first leg (GP17-OCE) as a southward extension of the 2018 GP15 Alaska-Tahiti expedition and a second leg (GP17-ANT; December 2023-January 2024) into coastal and shelf waters of Antarctica's Amundsen Sea.";
    String title "[GP17-OCE Event Log] - Scientific sampling event log from the US GEOTRACES GP17-OCE cruise on R/V Roger Revelle (RR2214) from December 2022 to January 2023 (US GEOTRACES GP17 Section: South Pacific and Southern Ocean (GP17-OCE))";
    Float64 Westernmost_Easting -152.0003;
  }
}

 

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