NOAA   ERDDAP   Easier access to oceanographic data Brought to you by NOAA NMFS SFSC ERD    

ERDDAP > tabledap > Make a Graph

Dataset Title:  OBIS - ARGOS Satellite Tracking of Animals   RSS
Institution:  AADC   (Dataset ID: aadcArgos)
Range:  longitude = -180.0 to 180.0°E, latitude = -90.0 to 90.0°N
Information:  Summary | License | Metadata | Background | Data Access Form
 
Graph Type: 
X Axis: 
Y Axis: 
Color: 
 
Constraints   Constraint #1 Constraint #2
         
         
         
         
         
 
Server-side Functions
distinct()
orderBy(      " ")
orderByMax(" ")
 
Graph Settings
Marker Type:     Size:
Color: 
Color Bar:    Continuity:    Scale:
      Min:    Max:    N Sections:
Draw the land mask:
Y Axis Minimum:    Maximum:
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: and
or view the URL:
(Documentation / How to bypass this form ) (File Type information)
    Click on the map to specify a new center point.
Zoom: 
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 {
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -180.0, 180.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -90.0, 90.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  altitude {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "up";
    String axis "Z";
    String comment "Created from the darwin:MinimumDepth variable.";
    String ioos_category "Location";
    String long_name "Altitude";
    String positive "up";
    String standard_name "altitude";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String comment 
"Created from the darwin:YearCollected-darwin:MonthCollected-darwin:
DayCollected and darwin:TimeOfDay variables.";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  ID {
    String comment 
"Created from the [darwin:InstitutionCode]:[darwin:CollectionCode]:[darwin:
CatalogNumber] variables.";
    String ioos_category "Identifier";
  }
  BasisOfRecord {
    String comment 
"An abbreviation indicating whether the record represents an observation (O), 
living organism (L), specimen (S), germplasm/seed (G), etc.";
    String ioos_category "Identifier";
  }
  BoundingBox {
    String comment 
"This access point provides a mechanism for performing searches using a 
bounding box. A Bounding Box element is not typically present in the 
database, but rather is derived from the Latitude and Longitude columns by 
the data provider";
    String ioos_category "Location";
  }
  CatalogNumber {
    String comment 
"A unique alphanumeric value which identifies an individual record within the 
collection. It is recommended that this value provides a key by which the 
actual specimen can be identified. If the specimen has several items such as 
various types of preparation, this value should identify the individual 
component of the specimen";
    String ioos_category "Identifier";
  }
  Citation {
    String comment "Indicates how this record should be attributed if used";
    String ioos_category "Other";
  }
  Class {
    String comment "The class name of the organism";
    String ioos_category "Taxonomy";
  }
  CollectionCode {
    String comment 
"A unique alphanumeric value which identifies the collection within the 
institution";
    String ioos_category "Identifier";
  }
  Collector {
    String comment 
"The name(s) of the collector(s) responsible for collection the specimen or 
taking the observation";
    String ioos_category "Identifier";
  }
  CollectorNumber {
    String comment 
"An identifying 'number' (really a string) applied to specimens (in some 
disciplines) at the time of collection. Establishes a links different parts/
preparations of a single specimen and between field notes and the specimen.";
    String ioos_category "Identifier";
  }
  ContinentOcean {
    String comment "The continent or ocean from which a specimen was collected.";
    String ioos_category "Location";
  }
  CoordinatePrecision {
    String comment 
"An estimate of how tightly the collecting locality was specified; expressed 
as a distance, in meters, that corresponds to a radius around the latitude-
longitude coordinates. Use NULL where precision is unknown, cannot be 
estimated, or is not applicable.";
    String ioos_category "Location";
    String units "m";
  }
  Country {
    String comment 
"The country or major political unit from which the specimen was collected. 
http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/db_en.html , ISO 3166-1 
values should be used. Full country names are currently in use. A future 
recommendation is to use ISO3166-1 two letter codes or the full name when 
searching";
    String ioos_category "Location";
  }
  County {
    String comment 
"The county (or shire, or next political region smaller than State / 
Province) from which the specimen was collected";
    String ioos_category "Location";
  }
  DateLastModified {
    String comment 
"ISO 8601 compliant stamp indicating the date and time in UTC(GMT) when the 
record was last modified. Example: the instant 'November 5, 1994, 8:15:30 am, 
US Eastern Standard Time' would be represented as '1994-11-05T13:15:30Z' (see 
http://www.w3.org/TR/NOTE-datetime , W3C Note on Date and Time 
Formats). (What to do when this date-time is unknown? Use Date-Time first '
published'?)";
    String ioos_category "Time";
    String long_name "Time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  DayCollected {
    String comment 
"The day of the month the specimen was collected from the field. Possible 
value ranges from 01..31 inclusive";
    String ioos_category "Time";
  }
  DayIdentified {
    String comment 
"The day portion of the date when the Collection Item was identified; as two 
digits [01..31].";
    String ioos_category "Time";
  }
  DepthRange {
    String comment 
"For data sets that have the depth range expressed in one field (e.g. '150-
200 m') it can be entered here as free text.  Separate, numeric Minimum and 
Maximum Depth fields are the preferred format; the Depth Range option is 
included for legacy data sets.";
    String ioos_category "Location";
  }
  EndDayCollected {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the end day of the collecting event.  Possible value ranges from 01..31 
inclusive";
    String ioos_category "Time";
  }
  EndJulianDay {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the end ordinal day of the year for the collecting event; i.e., the number of 
days since January 1 of the same year. (January 1 is Julian Day 1.).  Should 
be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-9][0-
9)|([1-9])).";
    String ioos_category "Time";
  }
  EndLatitude {
    String comment 
"For samples/observations/record events better represented as line features 
rather than point features (e.g. extended trawls or transects) this indicates 
the starting latitude location from which the specimen was collected or in 
which the sample/observation/record event occurred. This value should be 
expressed in decimal degrees (East & North = +; West & South = -). GPS-
derived data must use the WGS 84 geodetic reference system (http://www.wgs84.
com/).";
    String ioos_category "Location";
    String units "degrees_north";
  }
  EndLongitude {
    String comment 
"For samples/observations/record events better represented as line features 
rather than point features (e.g. extended trawls or transects) this indicates 
the starting longitude location from which the specimen was collected. 
Express in decimal degrees (East & North = +; West & South = -). GPS-derived 
data must use the WGS 84 geodetic reference system (http://www.wgs84.com/). [-
180 to 180]";
    String ioos_category "Location";
    String units "degrees_east";
  }
  EndMonthCollected {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the end month of the collecting event.  Possible values range from 01...12 
inclusive";
    String ioos_category "Time";
  }
  EndTimeofDay {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the end time of day of the collecting event expressed as decimal hours from 
midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm)";
    String ioos_category "Time";
    String units "hours";
  }
  EndYearCollected {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the end year of the collecting event.  The full year should be expressed (e.
g. 1972 must be expressed as '1972' not '72'). Must always be a four digit 
integer";
    String ioos_category "Time";
  }
  Family {
    String comment "The family name of the organism";
    String ioos_category "Taxonomy";
  }
  FieldNumber {
    String comment 
"A 'number' (really a string) created at collection time to identify all 
material that resulted from a collecting event.";
    String ioos_category "Identifier";
  }
  GMLFeature {
    String comment 
"Geographic Markup Language(GML) description of the feature for representing 
complex shapes such as lines and polygons, per Open GIS Consortium (OGC) 
standards - http://www.opengis.net/gml/01-029/GML2.html.";
    String ioos_category "Other";
  }
  Genus {
    String comment "The genus name of the organism";
    String ioos_category "Taxonomy";
  }
  IdentifiedBy {
    String comment 
"The name(s) of the person(s) who applied the currently accepted Scientific 
Name to the Cataloged Item.";
    String ioos_category "Taxonomy";
  }
  IndividualCount {
    String comment 
"The number of individuals present in the lot or container. Not an estimate 
of abundance or density at the collecting locality.";
    String ioos_category "Other";
    String units "count";
  }
  InstitutionCode {
    String comment 
"A 'standard' code identifier that identifies the institution to which the 
collection belongs. No global registry exists for assigning institutional 
codes. Use the code that is 'standard' in your discipline.";
    String ioos_category "Identifier";
  }
  JulianDay {
    String comment 
"The ordinal day of the year; i.e., the number of days since January 1 of the 
same year. (January 1 is Julian Day 1.)";
    String ioos_category "Time";
  }
  Kingdom {
    String comment "The kingdom to which the organism belongs";
    String ioos_category "Taxonomy";
  }
  LifeStage {
    String comment 
"Indicates the life stage present. Will require developing a controlled 
vocabulary. Can include multiple stages for a lot with multiple individuals.";
    String ioos_category "Biology";
  }
  Locality {
    String comment 
"The locality description (place name plus optionally a displacement from the 
place name) from which the specimen was collected. Where a displacement from 
a location is provided, it should be in un-projected units of measurement";
    String ioos_category "Location";
  }
  MaximumDepth {
    String comment 
"The maximum distance in meters below the surface of the water at which the 
collection was made; all material collected was at most this deep. Positive 
below the surface, negative above (e.g. collecting above sea level in tidal 
areas).";
    String ioos_category "Location";
    String units "m";
  }
  MaximumElevation {
    String comment 
"The maximum distance in meters above (positive) or below sea level of the 
collecting locality.";
    String ioos_category "Location";
    String units "m";
  }
  MinimumElevation {
    String comment 
"The minimum distance in meters above (positive) or below sea level of the 
collecting locality.";
    String ioos_category "Location";
    String units "m";
  }
  MonthCollected {
    String comment 
"The month of year the specimen was collected from the field. Possible values 
range from 01...12 inclusive";
    String ioos_category "Time";
  }
  MonthIdentified {
    String comment 
"The month portion of the date when the Collection Item was identified; as 
two digits [01..12].";
    String ioos_category "Time";
  }
  Notes {
    String comment "Free text notes attached to the specimen record";
    String ioos_category "Other";
  }
  ObservedIndividualCount {
    String comment "The number of individuals (abundance) found in a collection/record event.";
    String ioos_category "Other";
    String units "count";
  }
  ObservedWeight {
    String comment "The total biomass found in a collection/record event.  Expressed as kg.";
    String ioos_category "Biology";
    String units "kg";
  }
  Order {
    String comment "The order name of the organism";
    String ioos_category "Taxonomy";
  }
  Phylum {
    String comment "The phylum (or division) to which the organism belongs";
    String ioos_category "Taxonomy";
  }
  PreparationType {
    String comment 
"The type of preparation (skin. slide, etc). Probably best to add this as a 
record element rather than access point. Should be a list of preparations for 
a single collection record.";
    String ioos_category "Other";
  }
  PreviousCatalogNumber {
    String comment 
"The previous (fully qualified) catalog number of the Cataloged Item if the 
item earlier identified by another Catalog Number, either in the current 
catalog or another Institution / catalog. A fully qualified Catalog Number is 
preceded by Institution Code and Collection Code, with a space separating the 
each subelement. Referencing a previous Catalog Number does not imply that a 
record for the referenced item is or is not present in the corresponding 
catalog, or even that the referenced catalog still exists. This access point 
is intended to provide a way to retrieve this record by previously used 
identifier, which may used in the literature. In future versions of this 
schema this attribute should be set-valued.";
    String ioos_category "Identifier";
  }
  RecordURL {
    String comment 
"Gives the web address of the page where more information on this particular 
record (not on the whole dataset) can be found.";
    String ioos_category "Identifier";
  }
  RelatedCatalogItem {
    String comment 
"The fully qualified identifier of a related Catalog Item (a reference to 
another specimen); Institution Code, Collection Code, and Catalog Number of 
the related Cataloged Item, where a space separates the three subelements.";
    String ioos_category "Other";
  }
  RelationshipType {
    String comment 
"A named or coded valued that identifies the kind relationship between this 
Collection Item and the referenced Collection Item. Named values include: '
parasite of', 'epiphyte on', 'progeny of', etc. In future versions of this 
schema this attribute should be set-valued.";
    String ioos_category "Other";
  }
  SampleSize {
    String comment 
"Sample_size: the size of the sample from which the collection/observation 
was drawn.  It can be a volume (e.g. for a phytoplankton sample), a linear 
distance (e.g. for a visual transect or net haul), a surface area (e.g. for a 
benthic core), etc.  This field must also include the units, e.g. 200 mfor a 
transect, or 0.25 m^2 for a benthic grab (use ^ to denote a superscript).  
Note that when multiple collections/observations are reported from the same 
physical sample, a code identifying the sample can be placed in the Field_
Number field to allow all collections/observations from a single sample to be 
connected.";
    String ioos_category "Other";
  }
  ScientificName {
    String comment 
"The full name of lowest level taxon the Cataloged Item can be identified as 
a member of; includes genus name, specific epithet, and subspecific 
epithet (zool.) or infraspecific rank abbreviation, and infraspecific 
epithet (bot.) Use name of suprageneric taxon (e.g., family name) if 
Cataloged Item cannot be identified to genus, species, or infraspecific taxon.";
    String ioos_category "Identifier";
  }
  ScientificNameAuthor {
    String comment 
"The author of a scientific name. Author string as applied to the accepted 
name. Can be more than one author (concatenated string). Should be formatted 
according to the conventions of the applicable taxonomic discipline.";
    String ioos_category "Taxonomy";
  }
  Sex {
    String comment 
"The sex of a specimen. The domain should be a controlled set of 
terms (codes) based on community consensus. Proposed values: M=Male; F=
Female; H=Hermaphrodite; I=Indeterminate (examined but could not be 
determined; U=Unkown (not examined); T=Transitional (between sexes; useful 
for sequential hermaphrodites)";
    String ioos_category "Biology";
  }
  Source {
    String comment 
"Indicates who gave the record to the data provider. Can indicate a 
literature citation, an electronic dataset, etc. Is used to provide credit.";
    String ioos_category "Identifier";
  }
  Species {
    String comment "The specific epithet of the organism";
    String ioos_category "Taxonomy";
  }
  StartDayCollected {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the start day of the collecting event.  Possible value ranges from 01..31 
inclusive";
    String ioos_category "Time";
  }
  StartJulianDay {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the start ordinal day of the year for the collecting event; i.e., the number 
of days since January 1 of the same year. (January 1 is Julian Day 1.). 
Should be an integer from one to 365, i.e. of the form (([0-3][0-9][0-9)|([0-
9][0-9)|([1-9])).";
    String ioos_category "Time";
  }
  StartLatitude {
    String comment 
"For samples/observations/record events better represented as line features 
rather than point features (e.g. extended trawls or transects) this indicates 
the starting latitude location from which the specimen was collected or in 
which the sample/observation/record event occurred. This value should be 
expressed in decimal degrees (East & North = +; West & South = -). GPS-
derived data must use the WGS 84 geodetic reference system (http://www.wgs84.
com/).";
    String ioos_category "Location";
    String units "degrees_north";
  }
  StartLongitude {
    String comment 
"For samples/observations/record events better represented as line features 
rather than point features (e.g. extended trawls or transects) this indicates 
the starting longitude location from which the specimen was collected. 
Express in decimal degrees (East & North = +; West & South = -). GPS-derived 
data must use the WGS 84 geodetic reference system (http://www.wgs84.com/). [-
180 to 180]";
    String ioos_category "Location";
    String units "degrees_east";
  }
  StartMonthCollected {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the start month of the collecting event.  Possible values range from 01...12 
inclusive";
    String ioos_category "Time";
  }
  StartTimeofDay {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the start time of day of the collecting event expressed as decimal hours from 
midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm)";
    String ioos_category "Time";
    String units "hours";
  }
  StartYearCollected {
    String comment 
"For samples/observations/record events that were taken over time this gives 
the start year of the collecting event.  The full year should be expressed (e.
g. 1972 must be expressed as '1972' not '72'). Must always be a four digit 
integer";
    String ioos_category "Time";
  }
  Start_EndCoordinatePrecision {
    String comment 
"An estimate of how tightly the locality was specified in the Start/End 
Latitude and Longitude fields; expressed as a distance, in meters, that 
corresponds to a radius around the latitude-longitude coordinates. Use NULL 
where precision is unknown, cannot be estimated, or is not applicable.";
    String ioos_category "Location";
    String units "m";
  }
  StateProvince {
    String comment 
"The state, province or region (i.e. next political region smaller than 
Country) from which the specimen was collected. There is some suggestion to 
use the values described in http://www.iso.ch/cate/d8349.html , ISO 3166-2, 
however these values are in a continual state of flux and it appears unlikely 
that an appropriate mechanism (by ISO) will be in place to manage these 
changes. Hence it is recommended that where possible, the full, unabbreviated 
name should be used for storing information. The server should optionally 
handle abbreviations as an access point. Note: this is a recurring 
theme (country and state) abbreviations. Check the existence of an attribute 
type to deal with abbreviations from the bib-1 profile";
    String ioos_category "Location";
  }
  Subgenus {
    String comment "The subgenus name of the organism";
    String ioos_category "Taxonomy";
  }
  Subspecies {
    String comment "The sub-specific epithet of the organism";
    String ioos_category "Taxonomy";
  }
  Temperature {
    String comment 
"The temperature recorded with the collection/record event. Is assumed to be 
taken at the collection depth. Expressed in degrees Celsius.";
    String ioos_category "Temperature";
    String units "degree_C";
  }
  TimeOfDay {
    String comment 
"The time of day a specimen was collected expressed as decimal hours from 
midnight local time (e.g. 12.0 = mid day, 13.5 = 1:30pm)";
    String ioos_category "Time";
    String units "hours";
  }
  TimeZone {
    String comment "Indicates the time zone for the Time of Day measurements";
    String ioos_category "Time";
  }
  TypeStatus {
    String comment 
"Indicates the kind of nomenclatural type that a specimen represents. (This 
is incomplete because type status actually describes the relationship between 
a name and a specimen [or ternary relatiohnship between a specimen, name, and 
publication].) In particular, the type status may not apply to the name 
listed in the scientific name, i.e., current identification. In rare cases, a 
single specimen may be the type of more than one name.";
    String ioos_category "Taxonomy";
  }
  YearCollected {
    String comment 
"The year (expressed as an integer) in which the specimen was collected. The 
full year should be expressed (e.g. 1972 must be expressed as '1972' not '
72'). Must always be a four digit integer [-9999..9999]";
    String ioos_category "Time";
  }
  YearIdentified {
    String comment 
"The year portion of the date when the Collection Item was identified; as 
four digits [-9999..9999], e.g., 1906, 2002.";
    String ioos_category "Time";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String citation 
"See the following Metadata records http://data.aad.gov.au/aadc/metadata/
metadata_redirect.cfm?md=AMD/AU/DB_Argos_PTT_Tracking http://data.aad.gov.au/
aadc/metadata/metadata_redirect.cfm?md=AMD/AU/HI_animaltracks_ARGOS http://
data.aad.gov.au/aadc/metadata/metadata_redirect.cfm?md=AMD/AU/Tracking_BI 
http://data.aad.gov.au/aadc/metadata/metadata_redirect.cfm?md=AMD/AU/Tracking_
Mag http://data.aad.gov.au/aadc/metadata/metadata_redirect.cfm?md=AMD/AU/STA_
Bibliography http://data.aad.gov.au/aadc/metadata/metadata_redirect.cfm?md=
AMD/AU/Tracking_SI http://data.aad.gov.au/aadc/metadata/metadata_redirect.cfm?
md=AMD/AU/Tracking_EDP http://data.aad.gov.au/aadc/metadata/metadata_redirect.
cfm?md=AMD/AU/Tracking_DD Contact Data Centre for help on citation details.";
    String Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    String creator_email "kim.finney@aad.gov.au";
    Float64 Easternmost_Easting 180.0;
    Float64 geospatial_lat_max 90.0;
    Float64 geospatial_lat_min -90.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 180.0;
    Float64 geospatial_lon_min -180.0;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "up";
    String geospatial_vertical_units "m";
    String history 
"2017-06-25 http://aadc-maps.aad.gov.au/digir/digir.php
2017-06-25 http://cwcgom.aoml.noaa.gov/tabledap/aadcArgos.das";
    String infoUrl "http://data.aad.gov.au/";
    String institution "AADC";
    String keywords "ARGOS, satellite tracking, penguins, whales, seals, albatrosses";
    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.

By using OBIS data, I agree that, in any publication or presentation
of any sort based wholly or in part on such data, I will:

1. Acknowledge the use of specific records from contributing databases
in the form appearing in the GLOBAL 'citation' attribute thereof (if any);
and acknowledge the use of the OBIS facility in one of the following
prescribed forms:

For OBIS website:

Ocean Biogeographic Information System. [date accessed]
http://aadc-maps.aad.gov.au/digir/digir.php

For data used:

Author, initials. Database title. Retrieved [date accessed] from
http://aadc-maps.aad.gov.au/digir/digir.php

Example:

Stocks, K. SeamountsOnline: an online information system for seamount
biology. Version 3.1. Retrieved [date accessed] from
http://aadc-maps.aad.gov.au/digir/digir.php.

2. For information purposes, provide to kim.finney@aad.gov.au
the full citation of any publication I make (printed or electronic)
that cites OBIS or any constituent part.

3. Recognize the limitations of data in OBIS:
OBIS is comparable to a scientific journal that makes data freely
available on the internet. Thus the geographic and taxonomic scope,
and quantity of data provided, depend on the scientists and
organizations that provide data. However, in contrast to data in a
journal, the 'reader' can select and combine data in OBIS from a
variety of sources. OBIS and its users give feedback on data quality
and possible errors to data providers. Because data providers are
willing to correct errors, the quality of the data will increase in
time. How OBIS provides quality assurance, who is primarily
responsible for data published in OBIS (its owners), issues to be
considered in using the data, and known gaps in the data, are
described below.

Quality assurance

Only data from authoritative scientists and science organizations
approved by OBIS are served. All data are subject to quality control
procedures before publication, and at regular intervals, with data
providers informed of any discrepancies and potential errors (e.g.
species names spelt incorrectly, mapping errors). OBIS also benefits
from user peer-review and feedback to identify technical, geographic,
and taxonomic errors in data served. However, although errors will
exist as they do in any publication, OBIS is confident that the data
are the best available in electronic form. That said, the user needs
sufficient knowledge to judge the appropriate use of the data, i.e.
for what purpose it is fit.

Many of the data published through OBIS have voucher specimens in
institutional collections and museums, images of observations, and
the original identifier of the specimens is often credited or will
be contactable from the data custodian.

Data ownership

Data providers retain ownership of the data provided. OBIS does not
own or control or limit the use of any data or products accessible
through its website. Accordingly, it does not take responsibility
for the quality of such data or products, or the use that people may
make of them.

Data use

Appropriate caution is necessary in the interpretation of results
derived from OBIS. Users must recognize that the analysis and
interpretation of data require background knowledge and expertise
about marine biodiversity (including ecosystems and taxonomy).
Users should be aware of possible errors, including in the use of
species names, geo-referencing, data handling, and mapping. They
should cross-check their results for possible errors, and qualify
their interpretation of any results accordingly.

Users should be aware that OBIS is a gateway to a system of databases
distributed around the world. More information on OBIS data is
available from the data sources websites and contact persons. Users
should email any questions concerning OBIS data or tools (e.g. maps)
to the appropriate contact person and copy this request to
kim.finney@aad.gov.au .

Data gaps

Major gaps in data and knowledge about the oceans are reflected in
OBIS' data coverage. Note the following:
Most of the planet is more than 1 km under water: this deep sea is
the least surveyed part of our world.
Coastal areas have been adequately sampled only for the distribution
of most vertebrates (birds, mammals, reptiles, larger fish).
The oceans have been better sampled in the northern than the
southern hemisphere, as reflected in the distribution of data in
OBIS.
Most marine species have not yet been recognized or named. A major
effort is required to describe marine species, especially
invertebrates and deep-sea organisms.
Of the marine species that have been described, some have been
discovered to be several species, and others combined into single
species. Thus, there are changes in the application of species names
over time. A checklist of all current marine species names is not
available but it is estimated that 230,000 have been described.
Only about half of these names have been organized into global
species checklists. OBIS includes distribution data on (a) many of
these validated names and (b) additional names that remain to be
organized into global species checklists. Thus, OBIS has some
distribution data for about one third of the known marine species.
Some species distribution data are not available in any form, as
they have not have been published nor made available for databases.
Only some of the recently collected, and less of the older published,
data have been entered into databases. Thus databases are incomplete.
Of existing databases, many are not connected to OBIS.

You can help address these data gaps by (a) recognizing and
encouraging scientists and organizations to make their data available
online so they are accessible to OBIS, and (b) advocating for and
carrying out field surveys and taxonomic studies designed to fill
geographic and taxonomic gaps in knowledge.
";
    String Metadata_Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    Float64 Northernmost_Northing 90.0;
    String sourceUrl "http://aadc-maps.aad.gov.au/digir/digir.php";
    Float64 Southernmost_Northing -90.0;
    String standard_name_vocabulary "CF-12";
    String summary 
"Various species have been tracked using ARGOS PTT trackers since the early 
1990's. These include Emperor, King and Adelie pengiuns, Light-mantled Sooty, 
Grey-headed and Black-browed albatrosses, Antarctic and Australian fur seals, 
Southern Elephant Seal and Blue and Humpback whales. Note that not all data 
for any species or locations is or will be exposed to OBIS. Geographic 
coverage is from Heard Island to the west and Macquarie Island to the east 
and several islands near the southern end of Chile. The data has been 
filtered to remove most but not all erroneous positions.

DiGIR is an engine which takes XML requests for data and returns a data
subset stored as XML data (as defined in a schema). For more DiGIR
information, see http://digir.sourceforge.net/ ,
http://diveintodigir.ecoforge.net/draft/digirdive.html ,
and http://digir.net/prov/prov_manual.html .
A list of Digir providers is at
http://bigdig.ecoforge.net/wiki/SchemaStatus .

Darwin is the original schema for use with the DiGIR engine.

The Ocean Biogeographic Information System (OBIS) schema extends
Darwin. For more OBIS info, see http://www.iobis.org .
See the OBIS schema at http://www.iobis.org/tech/provider/questions .

Queries: Although OBIS datasets have many variables, most variables
have few values.  The only queries that are likely to succeed MUST
include a constraint for Genus= and MAY include constraints for
Species=, longitude, latitude, and time.

Most OBIS datasets return a maximum of 1000 rows of data per request.
The limitation is imposed by the OBIS administrators.

Available Genera (and number of records): (error)";
    String title "OBIS - ARGOS Satellite Tracking of Animals";
    Float64 Westernmost_Easting -180.0;
  }
}

 

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 is a superset of the OPeNDAP DAP constraint protocol.

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
   http://cwcgom.aoml.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
   http://cwcgom.aoml.noaa.gov/erddap/tabledap/pmelTao.htmlTable?longitude,latitude,time,sea_surface_temperature&longitude>180&longitude<180.2&latitude>0&latitude<0.2&time>2007-06-01T00: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 separated by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.
 


ERDDAP, Version 1.30
Questions, comments, suggestions? Please send an email to joaquin dot trinanes at noaa dot gov
and include the ERDDAP URL directly related to your question or comment.
Disclaimers | Privacy Policy