OccurrenceIssue (GBIF Common :: API 2.1.4 API) (original) (raw)

Coordinate is the exact 0°, 0° coordinate, often indicating a bad null coordinate.

Coordinate has a latitude and/or longitude value beyond the maximum (or minimum) decimal value.

Coordinate value is given in some form but GBIF is unable to interpret it.

Original coordinate modified by rounding to 5 decimals.

The geodetic datum given could not be interpreted.

Indicating that the interpreted coordinates assume they are based on WGS84 datum as the datum was either not indicated or interpretable. See GEODETIC_DATUM_INVALID.

The original coordinate was successfully reprojected from a different geodetic datum to WGS84.

The given decimal latitude and longitude could not be reprojected to WGS84 based on the provided datum.

Indicates successful coordinate reprojection according to provided datum, but which results in a datum shift larger than 0.1 decimal degrees.

Deprecated.
Indicates an invalid or very unlikely coordinate accuracy derived from precision or uncertainty in meters.

Indicates an invalid or very unlikely coordinatePrecision

Indicates an invalid or very unlikely dwc:uncertaintyInMeters.

Deprecated.
There is a mismatch between coordinate uncertainty in meters and coordinate precision.

The Footprint Spatial Reference System given could not be interpreted.

The Footprint Well-Known-Text conflicts with the interpreted coordinates (Decimal Latitude, Decimal Longitude etc).

The Footprint Well-Known-Text given could not be interpreted.

The interpreted occurrence coordinates fall outside of the indicated country.

Interpreted country for dwc:country and dwc:countryCode contradict each other.

Uninterpretable country values found.

The interpreted country is based on the coordinates, not the verbatim string information.

The interpreted occurrence coordinates fall outside of the indicated continent.

The interpreted continent and country do not match.

Uninterpretable continent values found.

The interpreted continent is based on the country, not the verbatim string information.

The interpreted continent is based on the coordinates, not the verbatim string information.

Latitude and longitude appear to be swapped.

Longitude appears to be negated, e.g. 32.3 instead of -32.3

Latitude appears to be negated, e.g. 32.3 instead of -32.3

The recorded date specified as the eventDate string and the individual year, month, day and/or startDayOfYear, endDayOfYear are contradictory.

A (partial) invalid date is given, such as a non-existent date, zero month, etc.

The recorded date is highly unlikely, falling either into the future or representing a very old date before 1600 thus predating modern taxonomy.

Matching to the taxonomic backbone can only be done using a fuzzy, non-exact match.

Matching to the taxonomic backbone can only be done on a higher rank and not the scientific name.

Matching to the taxonomic backbone can only be done on a species level, but the occurrence was in fact considered a broader species aggregate/complex.
See Also:

The scientificNameID was not used when mapping the record to the GBIF backbone. This may indicate one of

The taxonConceptID was not used when mapping the record to the GBIF backbone. This may indicate one of

The taxonID was not used when mapping the record to the GBIF backbone. This may indicate one of

The scientificNameID matched a known pattern, but it was not found in the associated checklist. The backbone lookup was performed using either the names or a different ID on the record. This may indicate a poorly formatted identifier or may be caused by a newly created ID that isn't yet known in the version of the published checklist.
See Also:

The taxonConceptID matched a known pattern, but it was not found in the associated checklist. The backbone lookup was performed using either the names or a different ID on the record. This may indicate a poorly formatted identifier or may be caused by a newly created ID that isn't yet known in the version of the published checklist.
See Also:

The taxonID matched a known pattern, but it was not found in the associated checklist. The backbone lookup was performed using either the names or a different ID on the record. This may indicate a poorly formatted identifier or may be caused by a newly created ID that isn't yet known in the version of the published checklist.
See Also:

The scientificName provided in the occurrence record does not precisely match the name in the registered checklist when using the scientificNameID, taxonID or taxonConceptID to look it up. Publishers are advised to check the IDs are correct, or update the formatting of the names on their records.
See Also:

Matching to the taxonomic backbone cannot be done because there was no match at all, or several matches with too little information to keep them apart (potentially homonyms).

The GBIF Backbone concept was found using the scientificNameID, taxonID or taxonConceptID, but it differs from what would have been found if the classification names on the record were used. This may indicate a gap in the GBIF backbone, a poor mapping between the checklist and the backbone, or a mismatch between the classification names and the declared IDs (scientificNameID or taxonConceptID) on the occurrence record itself.
See Also:

Set if supplied depth is not given in the metric system, for example using feet instead of meters

Set if depth is larger than 11,000m or negative.

Set if supplied minimum depth > maximum depth

Set if depth is a non-numeric value

Set if elevation is above the troposphere (17km) or below 11km (Mariana Trench).

Set if supplied minimum elevation > maximum elevation

Set if supplied elevation is not given in the metric system, for example using feet instead of meters

Set if elevation is a non-numeric value

A (partial) invalid date is given for dc:modified, such as a nonexistent date, zero month, etc.

The date given for dc:modified is in the future or predates Unix time (1970).

The date given for dwc:dateIdentified is in the future or before Linnean times (1700).

The date given for dwc:dateIdentified is invalid and can't be interpreted at all.

The given basis of record is impossible to interpret or significantly different from the recommended vocabulary.

The given type status is impossible to interpret or significantly different from the recommended vocabulary.

The given type status contains some words that express uncertainty.

An invalid date is given for dc:created of a multimedia object.

An invalid URI is given for a multimedia object.

An invalid URI is given for dc:references.

An error occurred during interpretation, leaving the record interpretation incomplete.

The individual count value is not a positive integer

Example: individual count value > 0, but occurrence status is absent.

Occurrence status was inferred from the individual count value

Occurrence status was inferred from basis of records

The date given for dwc:georeferencedDate is in the future or before Linnean times (1700).

The date given for dwc:georeferencedDate is invalid and can't be interpreted at all.

The given institution matches with more than 1 GRSciColl institution.

The given collection matches with more than 1 GRSciColl collection.

The given institution couldn't be matched with any GRSciColl institution.

The given collection couldn't be matched with any GRSciColl collection.

The given institution was fuzzily matched to a GRSciColl institution. This can happen when either the code or the ID don't match or when the institution name is used instead of the code.

The given collection was fuzzily matched to a GRSciColl collection. This can happen when either the code or the ID don't match or when the collection name is used instead of the code.

The collection matched doesn't belong to the institution matched.

Deprecated.
The given owner institution is different than the given institution. Therefore we assume it could be on loan and we don't link it to the occurrence.
Deprecated by DIFFERENT_OWNER_INSTITUTION.

The given owner institution is different than the given institution. Therefore we assume it doesn't belong to the institution and we don't link it to the occurrence.

Era or erathem was inferred from a parent rank.

Period or system was inferred from a parent rank.

Epoch or series was inferred from a parent rank.

Age or stage was inferred from a parent rank.

The eon or eonothem provided belongs to another rank.

The era or erathem provided belongs to another rank.

The period or system provided belongs to another rank.

The period or series provided belongs to another rank.

The age or stage provided belongs to another rank.

The earliest eon or eonothem has to be earlier than the latest.

The era or erathem has to be earlier than the latest.

The period or system has to be earlier than the latest.

The period or series has to be earlier than the latest.

The age or stage has to be earlier than the latest.

The era or erathem don't belong to the eon or eonothem.

The period or system don't belong to the era or erathem.

The epoch or series don't belong to the period or system.

The age or stage don't belong to the epoch or series.