NOAA ERDDAP
Easier access to scientific data
   
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > info > fishbaseObis

Grid
DAP
Data
Sub-
set
Table
DAP
Data
Make
A
Graph
W
M
S
Source
Data
Files
Title Sum-
mary
FGDC,
ISO,
Metadata
Back-
ground
Info
RSS E
mail
Institution Dataset ID
     data   graph     OBIS - FishBase (Philippine Server)    ?   F   I   M   background (external link) RSS Subscribe FishBase fishbaseObis

The Dataset's Variables and Attributes

Row Type Variable Name Attribute Name Data Type Value
attribute NC_GLOBAL cdm_data_type String Point
attribute NC_GLOBAL Conventions String COARDS, CF-1.6, ACDD-1.3
attribute NC_GLOBAL creator_email String fishbase at cgiar.org
attribute NC_GLOBAL Easternmost_Easting double 180.0
attribute NC_GLOBAL featureType String Point
attribute NC_GLOBAL geospatial_lat_max double 90.0
attribute NC_GLOBAL geospatial_lat_min double -90.0
attribute NC_GLOBAL geospatial_lat_units String degrees_north
attribute NC_GLOBAL geospatial_lon_max double 180.0
attribute NC_GLOBAL geospatial_lon_min double -180.0
attribute NC_GLOBAL geospatial_lon_units String degrees_east
attribute NC_GLOBAL geospatial_vertical_positive String up
attribute NC_GLOBAL geospatial_vertical_units String m
attribute NC_GLOBAL infoUrl String http://filaman.ifm-geomar.de/home.htm (external link)
attribute NC_GLOBAL institution String FishBase
attribute NC_GLOBAL license String 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://www.fishbase.ph/digirprov/www/DiGIR.php

For data used:

Author, initials. Database title. Retrieved [date accessed] from
http://www.fishbase.ph/digirprov/www/DiGIR.php

Example:

Stocks, K. SeamountsOnline: an online information system for seamount
biology. Version 3.1. Retrieved [date accessed] from
http://www.fishbase.ph/digirprov/www/DiGIR.php.

2. For information purposes, provide to fishbase@cgiar.org
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
fishbase@cgiar.org .

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.
attribute NC_GLOBAL Northernmost_Northing double 90.0
attribute NC_GLOBAL sourceUrl String http://www.fishbase.ph/digirprov/www/DiGIR.php (external link)
attribute NC_GLOBAL Southernmost_Northing double -90.0
attribute NC_GLOBAL standard_name_vocabulary String CF Standard Name Table v29
attribute NC_GLOBAL summary String FishBase is a global information system on fishes. FishBase is a relational database with information to cater to different professionals such as research scientists, fisheries managers, zoologists and many more. FishBase on the web contains practically all fish species known to science. FishBase was developed at the WorldFish Center in collaboration with the Food and Agriculture Organization of the United Nations (FAO) and many other partners, and with support from the European Commission (EC). Since 2001 FishBase is supported by a consortium of seven research institutions.

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)
attribute NC_GLOBAL title String OBIS - FishBase (Philippine Server)
attribute NC_GLOBAL Westernmost_Easting double -180.0
variable longitude   double  
attribute longitude _CoordinateAxisType String Lon
attribute longitude actual_range double -180.0, 180.0
attribute longitude axis String X
attribute longitude ioos_category String Location
attribute longitude long_name String Longitude
attribute longitude standard_name String longitude
attribute longitude units String degrees_east
variable latitude   double  
attribute latitude _CoordinateAxisType String Lat
attribute latitude actual_range double -90.0, 90.0
attribute latitude axis String Y
attribute latitude ioos_category String Location
attribute latitude long_name String Latitude
attribute latitude standard_name String latitude
attribute latitude units String degrees_north
variable altitude   double  
attribute altitude _CoordinateAxisType String Height
attribute altitude _CoordinateZisPositive String up
attribute altitude axis String Z
attribute altitude comment String Created from the darwin:MinimumDepth variable.
attribute altitude ioos_category String Location
attribute altitude long_name String Altitude
attribute altitude positive String up
attribute altitude standard_name String altitude
attribute altitude units String m
variable time   double  
attribute time _CoordinateAxisType String Time
attribute time axis String T
attribute time comment String Created from the darwin:YearCollected-darwin:MonthCollected-darwin:DayCollected and darwin:TimeOfDay variables.
attribute time ioos_category String Time
attribute time long_name String Time
attribute time standard_name String time
attribute time time_origin String 01-JAN-1970 00:00:00
attribute time units String seconds since 1970-01-01T00:00:00Z
variable ID   String  
attribute ID comment String Created from the [darwin:InstitutionCode]:[darwin:CollectionCode]:[darwin:CatalogNumber] variables.
attribute ID ioos_category String Identifier
variable BasisOfRecord   String  
attribute BasisOfRecord comment String An abbreviation indicating whether the record represents an observation (O), living organism (L), specimen (S), germplasm/seed (G), etc.
attribute BasisOfRecord ioos_category String Identifier
variable BoundingBox   String  
attribute BoundingBox comment String 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
attribute BoundingBox ioos_category String Location
variable CatalogNumber   String  
attribute CatalogNumber comment String 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
attribute CatalogNumber ioos_category String Identifier
variable Citation   String  
attribute Citation comment String Indicates how this record should be attributed if used
attribute Citation ioos_category String Other
variable Class   String  
attribute Class comment String The class name of the organism
attribute Class ioos_category String Taxonomy
variable CollectionCode   String  
attribute CollectionCode comment String A unique alphanumeric value which identifies the collection within the institution
attribute CollectionCode ioos_category String Identifier
variable Collector   String  
attribute Collector comment String The name(s) of the collector(s) responsible for collection the specimen or taking the observation
attribute Collector ioos_category String Identifier
variable CollectorNumber   String  
attribute CollectorNumber comment String 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.
attribute CollectorNumber ioos_category String Identifier
variable ContinentOcean   String  
attribute ContinentOcean comment String The continent or ocean from which a specimen was collected.
attribute ContinentOcean ioos_category String Location
variable CoordinatePrecision   double  
attribute CoordinatePrecision comment String 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.
attribute CoordinatePrecision ioos_category String Location
attribute CoordinatePrecision units String m
variable Country   String  
attribute Country comment String 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
attribute Country ioos_category String Location
variable County   String  
attribute County comment String The county (or shire, or next political region smaller than State / Province) from which the specimen was collected
attribute County ioos_category String Location
variable DateLastModified   double  
attribute DateLastModified comment String 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'?)
attribute DateLastModified ioos_category String Time
attribute DateLastModified long_name String Date Last Modified
attribute DateLastModified time_origin String 01-JAN-1970 00:00:00
attribute DateLastModified units String seconds since 1970-01-01T00:00:00Z
variable DayCollected   byte  
attribute DayCollected comment String The day of the month the specimen was collected from the field. Possible value ranges from 01..31 inclusive
attribute DayCollected ioos_category String Time
variable DayIdentified   byte  
attribute DayIdentified comment String The day portion of the date when the Collection Item was identified; as two digits [01..31].
attribute DayIdentified ioos_category String Time
variable DepthRange   String  
attribute DepthRange comment String 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.
attribute DepthRange ioos_category String Location
variable EndDayCollected   byte  
attribute EndDayCollected comment String 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
attribute EndDayCollected ioos_category String Time
variable EndJulianDay   short  
attribute EndJulianDay comment String 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])).
attribute EndJulianDay ioos_category String Time
variable EndLatitude   double  
attribute EndLatitude comment String 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/).
attribute EndLatitude ioos_category String Location
attribute EndLatitude units String degrees_north
variable EndLongitude   double  
attribute EndLongitude comment String 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]
attribute EndLongitude ioos_category String Location
attribute EndLongitude units String degrees_east
variable EndMonthCollected   byte  
attribute EndMonthCollected comment String 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
attribute EndMonthCollected ioos_category String Time
variable EndTimeofDay   double  
attribute EndTimeofDay comment String 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)
attribute EndTimeofDay ioos_category String Time
attribute EndTimeofDay units String hours
variable EndYearCollected   short  
attribute EndYearCollected comment String 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
attribute EndYearCollected ioos_category String Time
variable Family   String  
attribute Family comment String The family name of the organism
attribute Family ioos_category String Taxonomy
variable FieldNumber   String  
attribute FieldNumber comment String A 'number' (really a string) created at collection time to identify all material that resulted from a collecting event.
attribute FieldNumber ioos_category String Identifier
variable GMLFeature   String  
attribute GMLFeature comment String 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.
attribute GMLFeature ioos_category String Other
variable Genus   String  
attribute Genus comment String The genus name of the organism
attribute Genus ioos_category String Taxonomy
variable IdentifiedBy   String  
attribute IdentifiedBy comment String The name(s) of the person(s) who applied the currently accepted Scientific Name to the Cataloged Item.
attribute IdentifiedBy ioos_category String Taxonomy
variable IndividualCount   int  
attribute IndividualCount comment String The number of individuals present in the lot or container. Not an estimate of abundance or density at the collecting locality.
attribute IndividualCount ioos_category String Other
attribute IndividualCount units String count
variable InstitutionCode   String  
attribute InstitutionCode comment String 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.
attribute InstitutionCode ioos_category String Identifier
variable JulianDay   short  
attribute JulianDay comment String 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.)
attribute JulianDay ioos_category String Time
variable Kingdom   String  
attribute Kingdom comment String The kingdom to which the organism belongs
attribute Kingdom ioos_category String Taxonomy
variable LifeStage   String  
attribute LifeStage comment String Indicates the life stage present. Will require developing a controlled vocabulary. Can include multiple stages for a lot with multiple individuals.
attribute LifeStage ioos_category String Biology
variable Locality   String  
attribute Locality comment String 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
attribute Locality ioos_category String Location
variable MaximumDepth   double  
attribute MaximumDepth comment String 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).
attribute MaximumDepth ioos_category String Location
attribute MaximumDepth units String m
variable MaximumElevation   double  
attribute MaximumElevation comment String The maximum distance in meters above (positive) or below sea level of the collecting locality.
attribute MaximumElevation ioos_category String Location
attribute MaximumElevation units String m
variable MinimumElevation   double  
attribute MinimumElevation comment String The minimum distance in meters above (positive) or below sea level of the collecting locality.
attribute MinimumElevation ioos_category String Location
attribute MinimumElevation units String m
variable MonthCollected   byte  
attribute MonthCollected comment String The month of year the specimen was collected from the field. Possible values range from 01...12 inclusive
attribute MonthCollected ioos_category String Time
variable MonthIdentified   byte  
attribute MonthIdentified comment String The month portion of the date when the Collection Item was identified; as two digits [01..12].
attribute MonthIdentified ioos_category String Time
variable Notes   String  
attribute Notes comment String Free text notes attached to the specimen record
attribute Notes ioos_category String Other
variable ObservedIndividualCount   int  
attribute ObservedIndividualCount comment String The number of individuals (abundance) found in a collection/record event.
attribute ObservedIndividualCount ioos_category String Other
attribute ObservedIndividualCount units String count
variable ObservedWeight   double  
attribute ObservedWeight comment String The total biomass found in a collection/record event. Expressed as kg.
attribute ObservedWeight ioos_category String Biology
attribute ObservedWeight units String kg
variable Order   String  
attribute Order comment String The order name of the organism
attribute Order ioos_category String Taxonomy
variable Phylum   String  
attribute Phylum comment String The phylum (or division) to which the organism belongs
attribute Phylum ioos_category String Taxonomy
variable PreparationType   String  
attribute PreparationType comment String 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.
attribute PreparationType ioos_category String Other
variable PreviousCatalogNumber   String  
attribute PreviousCatalogNumber comment String 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.
attribute PreviousCatalogNumber ioos_category String Identifier
variable RecordURL   String  
attribute RecordURL comment String Gives the web address of the page where more information on this particular record (not on the whole dataset) can be found.
attribute RecordURL ioos_category String Identifier
variable RelatedCatalogItem   String  
attribute RelatedCatalogItem comment String 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.
attribute RelatedCatalogItem ioos_category String Other
variable RelationshipType   String  
attribute RelationshipType comment String 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.
attribute RelationshipType ioos_category String Other
variable SampleSize   String  
attribute SampleSize comment String 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.
attribute SampleSize ioos_category String Other
variable ScientificName   String  
attribute ScientificName comment String 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.
attribute ScientificName ioos_category String Identifier
variable ScientificNameAuthor   String  
attribute ScientificNameAuthor comment String 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.
attribute ScientificNameAuthor ioos_category String Taxonomy
variable Sex   String  
attribute Sex comment String 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)
attribute Sex ioos_category String Biology
variable Source   String  
attribute Source comment String Indicates who gave the record to the data provider. Can indicate a literature citation, an electronic dataset, etc. Is used to provide credit.
attribute Source ioos_category String Identifier
variable Species   String  
attribute Species comment String The specific epithet of the organism
attribute Species ioos_category String Taxonomy
variable StartDayCollected   byte  
attribute StartDayCollected comment String 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
attribute StartDayCollected ioos_category String Time
variable StartJulianDay   short  
attribute StartJulianDay comment String 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])).
attribute StartJulianDay ioos_category String Time
variable StartLatitude   double  
attribute StartLatitude comment String 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/).
attribute StartLatitude ioos_category String Location
attribute StartLatitude units String degrees_north
variable StartLongitude   double  
attribute StartLongitude comment String 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]
attribute StartLongitude ioos_category String Location
attribute StartLongitude units String degrees_east
variable StartMonthCollected   byte  
attribute StartMonthCollected comment String 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
attribute StartMonthCollected ioos_category String Time
variable StartTimeofDay   double  
attribute StartTimeofDay comment String 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)
attribute StartTimeofDay ioos_category String Time
attribute StartTimeofDay units String hours
variable StartYearCollected   short  
attribute StartYearCollected comment String 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
attribute StartYearCollected ioos_category String Time
variable Start_EndCoordinatePrecision   double  
attribute Start_EndCoordinatePrecision comment String 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.
attribute Start_EndCoordinatePrecision ioos_category String Location
attribute Start_EndCoordinatePrecision units String m
variable StateProvince   String  
attribute StateProvince comment String 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
attribute StateProvince ioos_category String Location
variable Subgenus   String  
attribute Subgenus comment String The subgenus name of the organism
attribute Subgenus ioos_category String Taxonomy
variable Subspecies   String  
attribute Subspecies comment String The sub-specific epithet of the organism
attribute Subspecies ioos_category String Taxonomy
variable Temperature   double  
attribute Temperature comment String The temperature recorded with the collection/record event. Is assumed to be taken at the collection depth. Expressed in degrees Celsius.
attribute Temperature ioos_category String Temperature
attribute Temperature units String degree_C
variable TimeOfDay   double  
attribute TimeOfDay comment String 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)
attribute TimeOfDay ioos_category String Time
attribute TimeOfDay units String hours
variable TimeZone   String  
attribute TimeZone comment String Indicates the time zone for the Time of Day measurements
attribute TimeZone ioos_category String Time
variable TypeStatus   String  
attribute TypeStatus comment String 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.
attribute TypeStatus ioos_category String Taxonomy
variable YearCollected   short  
attribute YearCollected comment String 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]
attribute YearCollected ioos_category String Time
variable YearIdentified   short  
attribute YearIdentified comment String The year portion of the date when the Collection Item was identified; as four digits [-9999..9999], e.g., 1906, 2002.
attribute YearIdentified ioos_category String Time

The information in the table above is also available in other file formats (.csv, .htmlTable, .itx, .json, .jsonlCSV, .jsonlKVP, .mat, .nc, .nccsv, .tsv, .xhtml) via a RESTful web service.


 
ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact