DQ Tests-Assertions - Post workshop.xlsx
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
#IDsVariableSpecificationSpecification (Techncial Description)Example Implementations (Mechanisms)Data resolutionOutput TypeDarwin Core ClassDarwin Core TermsSeveritySourceReferencesLink to Specification Source CodeComments and Questions
2
1Number of assertions = TRUE. An indication of the record issuese.g. Count the number of TRUE values of columns with prefix “VALIDATION_" Single RecordMeasureAllAllWarningLee Belbin
3
2Number of supplied + inferred Darwin Core fields. An indication of record completenesse.g. Count the number of non-NULL or empty (disregarding spaces) values of the record.Single RecordMeasureAllAllWarningLee Belbin
4
3Completeness checks – calculating ratio of null DwC values in a table?e.g. Count the number of NULL or empty (disregarding spaces) values of each record record in the dataset and divide by total number of records in the dataset.DatasetMeasureAllAllWarningTania Laity
5
6MODIFIED_DATE_INVALIDA (partial) invalid date is given for dc:modified, such as a non existing date, invalid zero month, etc.Is or can be converted to ISO format dateSingle RecordValidationAlldcterms:modifiedGBIF
6
8MODIFIED_DATE_UNLIKELYThe date given for dc:modified is in the future or predates unix time (1970).Single RecordValidationAlldcterms:modifiedGBIF
7
430008MISSING_COLLECTION_DATECollection date field is missing or null or 00-00-0000e.g. Return FALSE if value is 0000-00-00 or empty value (disregarding spaces).ALA-SandBoxSingle RecordValidationEventeventDateErrorALACovered by #5
8
530010INCOMPLETE_COLLECTION_DATEThe supplied collection date is missing a day and/or month component. This is used to differentiate non error conditions for an event date.Single RecordValidationEventeventDateWarningALANot entiurely sure what this means? (AC)
9
730007INVALID_COLLECTION_DATEThe collecting event date was given as pre 1700, or is otherwise invalid. This is used as a general date issueSingle RecordValidationEventeventDateErrorALA, GBIFPossibly reword to make sure #9 and #10 are covered. Is 1700 the earliest possible collection date? suggest use 1600? (AC) - SUGGEST WE REMOVE THIS ONE.
10
9datecollected_boundsDate Collected out of bounds (1700-01-02, Date of Indexing).Single RecordValidationEventeventDateiDigBioFits under #7 (AC)
11
10RECORDED_DATE_UNLIKELYThe recording date is highly unlikely, falling either into the future or represents a very old date before 1600 that predates modern taxonomy.Single RecordValidationEventeventDateGBIFFits under #7 (AC) But Note that says pre 1600 - others say pre 1700. Do we have valid collections between 1600 and 1700 - I suspect that there are some. TBA!
12
1230009DAY_MONTH_TRANSPOSEDSupplied day and month fields appear to be transposed. if month > 12 and day <12 we can infer the fields have been incorrectly mappedSingle RecordValidation and ImprovementEventeventDate, day, monthWarningALA
13
1330003FIRST_OF_MONTHMay indicate the date is only known or recorded to the Month. Flag if there is no precision data. DatasetValidationEventeventDate, datePrecision(nonDwC)WarningALAPosibly for datasets - so need in?
14
1430004FIRST_OF_YEARMay indicate the date is only known or recorded to the Year. Flag if there is no precision data. DatasetValidationEventeventDate, datePrecision(nonDwC)WarningALAPossibly for datasets
15
1530005FIRST_OF_CENTURYMay indicate the date is only known or recorded to the Century. Flag if there is no precision data. DatasetValidationEventeventDate, datePrecision(nonDwC)WarningALAPossibly for datasets
16
1630006DATE_PRECISION_MISMATCHDate precision does not match the data. Single RecordValidationEventeventDate, datePrecision(nonDwC)ErrorALAFlag for DwC (AC)
17
11RECORDED_DATE_MISMATCHThe recording date specified as the eventDate string and the individual year, month, day are contradicting.Single RecordValidationEventeventDate, day, month, yearGBIF
18
1730001ID_PRE_OCCURRENCEdateIdentified < eventDateSingle RecordValidationEvent, IdentificationdateIdentified, eventDateErrorALA
19
2130002GEOREFERENCE_POST_OCCURRENCEThe record was georeferenced after recording - not an error but has implications for precision and accuracy. The amount of time may indicate severity?Single RecordValidationEvent, LocationeventDate, georeferenceDateWarningALA
20
18IDENTIFIED_DATE_UNLIKELYThe date given for dwc:dateIdentified is in the future or before Linnean times (1700).Single RecordValidationIdentificationdateIdentifiedGBIF1753?
21
19IDENTIFIED_DATE_INVALIDThe date given for dwc:dateIdentified is invalid and cant be interpreted at all.Is or can be converted to ISO format dateSingle RecordValidationIdentificationdateIdentifiedGBIF
22
2210009MISSING_IDENTIFICATIONQUALIFIERidentificationQualifier not supplied with the recordSingle RecordValidationIdentificationidentficationQualifierWarningALA
23
2310011MISSING_IDENTIFICATIONREFERENCESidentificationReferences not supplied with the recordSingle RecordValidationIdentificationidentficationReferencesWarningALA
24
2010012MISSING_DATEIDENTIFIEDidentificationDate not supplied with the recordSingle RecordValidationIdentificationidentificationDateWarningALA, BISON
25
2410013IDENTIFICATION_UNCERTAINThe identification is uncertain. If doubts expresssed regarding taxon identification, e.g. 'requires verification' or 'doubtful' or 'uncertain' or similar then exclude.Single RecordValidationIdentificationscientificName, identificationQualifierErrorALA, GBIFChapman 2005a & 2005b, Zermoglio et al. 2016aff, or cf or ?
26
2510014IDENTIFICATION_VERIFIEDThe identication has been verified. The identification is verified as authentic, e.g. 'verified', 'confirmed'Reliability flagSingle RecordValidationIdentificationidentificationQualifierVerificationALAChapman 2005a & 2005bThis information should be in identificationVerificationStatus
27
2610010MISSING_IDENTIFIEDBYidentifiedBy not supplied with the recordSingle RecordValidationIdentificationidentifiedByWarningALA
28
2720004UNRECOGNISED_TYPESTATUSUnable to extract the supplied type status to the vocabulary in useSingle RecordValidationIdentificationtypeStatusWarningALA, GBIF
29
28dwc_continent_addedDarwin Core Continent Added.http://terms.tdwg.org/wiki/dwc:continentSingle RecordImprovementLocationcontinentiDigBioAssume missing continent - so added from coordinates?
30
29dwc_continent_replacedDarwin Core Continent Corrected.Single RecordImprovementLocationcontinentiDigBioContinent name has been corrected from misspelling or corrected from coordinates
31
111CONTINENT_INVALIDUninterpretable continent values found.Single RecordValidationLocationcontinentGBIF29=111 (duplicate)
32
3023COORDINATE_PRECISION_MISMATCHCoordinate data does not match precision indicated - could be incorrect precision or truncation or rounding of the coordinate data (most likely with trailing zeros)Single RecordValidationLocationcoordinatePrecisionWarningALANeeded?
33
3117PRECISION_RANGE_MISMATCHA precision value should be between >0 and <=1 if entered according to DwC specificiationsSingle RecordValidationLocationcoordinatePrecisionWarningALAPrecision is out of range 0-<1
34
3229MISSING_COORDINATEPRECISIONcoordinatePrecision not supplied with the recordSingle RecordValidationLocationcoordinatePrecisionWarningALANeeded?
35
33GEOPOINT_LOW_PRECISIONGeographic Coordinate has Low Precision.Single RecordValidationLocationcoordinatePrecision, decimalLatitude, decimalLongitudeiDigBioNeeded? Precision IS reported and should be noted. CoordinatePrecision is > .1 or the decimal latitude/longitude values have limited siginficant figures.
36
3436COORDINATE_UNCERTAINTY_IN_METERSThe inferred maximum (minimum?) uncertainty is 'n' metresSingle RecordValidationLocationcoordinatePrecision, geodeticDatum, coordinateUncertaintyInMeters, georeferenceProtocol, dataGeneralizationsMetricALA, CRIAGeoRef, ICSM 2000; BioGeom aNeeded? Check ALA code
37
3524UNCERTAINTY_RANGE_MISMATCHUncertainty should be a whole number >0Single RecordValidationLocationcoordinateUncertaintyInMetersWarningALA
38
3627UNCERTAINTY_NOT_SPECIFIEDUncertainty was not supplied with the recordSingle RecordValidationLocationcoordinateUncertaintyInMetersWarningALANeeded?
39
3725UNCERTAINTY_IN_PRECISIONUncertainty value in precision fieldSingle RecordValidationLocationcoordinateUncertaintyInMeters, coordinatePrecisionWarningALAcoordinateUncertaintyInMeters and coordinatePrecision appear swapped. Precision <= 1 , Uncertainty >= 1. Possibly combine with #35, needs further discussion
40
386UNKNOWN_COUNTRY_NAMEUnrecognised or unparseable country nameSingle RecordValidationLocationcountryWarningGBIFUnrecognised country name - should they be inferred or flagged?
41
3921COUNTRY_INFERRED_FROM_COORDINATESCountry field supplied was empty, but was inferred in processing by the supplied coordinatesSingle RecordImprovementLocationcountry, decimalLatitude, decimalLongitudeWarningGBIFGBIF 2010
42
40dwc_country_addedDarwin Core Country Added.http://terms.tdwg.org/wiki/dwc:countrySingle RecordImprovementLocationcountryiDigBioAs 39. It might useful to just define a test category that applies to any Darwin Core term country_added, eventdate_added, county_added, etc.
43
41dwc_country_replacedDarwin Core Country Corrected.Single RecordImprovementLocationcountryiDigBioFlag only? It might useful to just define a test category that applies to any Darwin Core term country_replaced, eventdate_replaced, county_replaced, etc.
44
110CONTINENT_COUNTRY_MISMATCHThe interpreted continent and country do not match up.Single RecordValidationLocationcountry, continentGBIFError? (AC) Potentiall either a validation or an error depending on how you define mismatch
45
109COUNTRY_MISMATCHInterpreted country for dwc:country and dwc:countryCode contradict each other.Single RecordValidationLocationcountry, countryCodeGBIF
46
4216COUNTRY_COORDINATE_MISMATCHCoordinates outside the range for the reported countrySingle RecordValidationLocationcountry, decimalLatitude, decimalLongitudeWarningGBIF
47
4928COORDINATES_CENTRE_OF_COUNTRYSupplied coordinates centre of countrySingle RecordValidationLocationcountry, decimalLatitude, decimalLongitudeWarningALAIs this an Error? It may have a huge Coordinate Uncertainty - if all the record has is a country name for example (AC)
48
43rev_geocode_mismatchGeographic Coordinate did not reverse geocode to correct country.Single RecordValidationLocationcountry, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioAs 42 (Christian Gendreau: yes it is) Aren't 42-28 really the one test? - i.e. coordinates outside of the Country (42) and then 44-48 is determining if one of those would Improve it. So I see 44-48 as subsets of 42 - how best to handle this (AC)
49
44rev_geocode_both_signGeographic Coordinate had its Latitude and Longitude negated to place it in correct country.Single RecordValidation and ImprovementLocationcountry, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioClarify naming of flag, possibly merge with other values
50
45rev_geocode_flipGeographic Coordinate had its Latitude and Longitude swapped to place it in correct country.Single RecordValidation and ImprovementLocationcountry, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioClarify naming of flag, possibly merge with other values
51
46rev_geocode_flip_both_signGeographic Coordinate had its Latitude and Longitude both swapped and negated to place it in correct country.Single RecordValidation and ImprovementLocationcountry, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioClarify naming of flag, possibly merge with other values
52
47rev_geocode_flip_lat_signGeographic Coordinate had its Latitude and Longitude swapped, and its Latitude negated to place it in correct country.Single RecordValidation and ImprovementLocationcountry, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioClarify naming of flag, possibly merge with other values
53
48rev_geocode_flip_lon_signGeographic Coordinate had its Latitude and Longitude swapped, and its Longitude negated to place it in correct country.Single RecordValidation and ImprovementLocationcountry, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioClarify naming of flag, possibly merge with other values
54
50idigbio_isocountrycode_addediDigBio ISO 3166-1 alpha-3 Country Code Added.iDigBio correction tableSingle RecordImprovementLocationcountryCodeiDigBioAs 40?
55
511NEGATED_LATITUDERecord appears to be referencing a location in the wrong hemisphereSingle RecordValidation and ImprovementLocationdecimalLatitudeWarningGBIF, BISONSame as #47 (AC), Clarify naming of flag, possibly merge with other values
56
523INVERTED_COORDINATESLatitude and longitude have been transposed accidently (typically bad database mapping)Single RecordValidation and ImprovementLocationdecimalLatitude, decimalLongitudeWarningGBIFSame as #45 (AC), Clarify naming of flag, possibly merge with other values
57
534ZERO_COORDINATESCoordinates given as 0,0. Typically a result of bad default values for empty database fieldsLee: Coordinates interpreted as 0,0?Single RecordValidationLocationdecimalLatitude, decimalLongitudeErrorGBIF
58
555COORDINATES_OUT_OF_RANGELatitude >90 or <-90 and Longitude >180 or <-180Separate the testsSingle RecordValidationLocationdecimalLatitude, decimalLongitudeErrorGBIFShould be split? decimalLatitude is out of range. decumalLongitude is out of range. ORDER OF TESTS COULD BE SIGNIFICANT
59
5639DETECTED_ENVIRONMENTAL_OUTLIERThe location is an outlier detected using jack-knife algorithmDetected environmental outlier flag test (1)All taxa recordsValidationLocationdecimalLatitude, decimalLongitudeErrorALAChapman 2005a, ALA 2008The record is an environmental outlier for that taxa based on all records of that taxa across one or more environmental parameters.
60
5740DETECTED_OUTLIER_OTHEROther methods of outliers detection to be investigated. An investigation will be made of the suitability of MaxEnt probababiilty values as an indicator of outliers. Other outlier detection methods will also be investigated, e.g. Chapman 2005a (p.45) mentions these geographic outlier detection methods: Cumulative Freqency Curves(Diva-GIS, ANUCLIM); Principle Components Analysis (FloraMap, PATN); Cluster Analysis (FloraMap, PATN); Climatic Envelope (Diva-GIS); Reverse Jackknife (Diva-GIS, planned for BioGeomancer in 2006); Parameter Extremes (ANUCLIM); Other Methods (Standard Deviations from Mean; Deviations from Median; Use of Modelled Distributions - GARP, Lifemapper; Pattern Analysis - PATN; Ordinal Association Rules- PATN - assocation with vegetation types etc). Note: some of these are explicitly mention in other proposed outlier checks. Note that all these are environmental outlier checks of one type or another (LB).As 56All taxa recordsValidationLocationdecimalLatitude, decimalLongitudeErrorALAAs with #65, suggest we use a single robust measure to detect outliers - probably convex hull. (I disagree here as some outlier detection methods work better than others in different circumstances and none could be regarded as truly robust in all circumstances. There should be a choice of methods as in many of the other tests. The TEST is "Is it an identified outlier?" the METHOD of doing this may be any of a number of Methods - geographic, environmental, etc. - AC)
61
5844DECIMAL_COORDINATES_NOT_SUPPLIEDdecimal latitude and longitude not suppliedSingle RecordValidationLocationdecimalLatitude, decimalLongitudeErrorALA
62
5945DECIMAL_LAT_LONG_CONVERTEDDecimal latitude and longitude were converted to WGS84Single RecordValidation and ImprovementLocationdecimalLatitude, decimalLongitude, geodeticDatumWarningALA, GBIFAmounts to a recommendation that aggregators should flag all coordinates that had to be convereted to be used. Might also imply saying something about the datum and uncertainty as a result. Potentially drop the WGS84 datum requirement
63
6046DECIMAL_LAT_LONG_CONVERSION_FAILEDConversion of decimal latitude and longitude to WGS84 failedSingle RecordValidationLocationdecimalLatitude, decimalLongitude, geodeticDatumErrorALA, GBIF Lee to check ALA code
64
6149DECIMAL_LAT_LONG_CALCULATED_FROM_EASTING_NORTHINGDecimal latitude and longitude were calculated using easting, northing and zoneSingle RecordValidation and ImprovementLocationdecimalLatitude, decimalLongitude, verbatimLat/LongWarningALAPossibly combine with other verbatum coordinate conversion flags? Check ALA code
65
6250DECIMAL_LAT_LONG_CALCULATION_FROM_EASTING_NORTHING_FAILEDFailed to calculate decimal latitude and longitude using easting, northing and zoneSingle RecordValidationLocationdecimalLatitude, decimalLongitudeErrorALAPossibly combine with other verbatum coordinate conversion flags?
66
6341INFERRED_FALSE_PRECISIONThe location may have a false level of precision. Indicate this if many decimal places in coordinates, but no precision or uncertainty measures. Methods to be investigated by SBIf more than 7 decimal places - more than needed - flagSingle RecordValidationLocationdecimalLatitude, decimalLongitude, coordinatePrecision, coordinateUncertaintyInMetersWarningALAChapman 2005b p26
67
6426SPECIES_OUTSIDE_EXPERT_RANGEGeographic coordinates are outside the geographic range as defined by 'expert/s' for the taxa. E.g. corals outside known range according to Charlie Veron - possible misidentification.All taxa recordsValidationLocationdecimalLatitude, decimalLongitude, expert range spatial layerWarningALAPriority of tests for data publishers
68
6520DETECTED_OUTLIER_ENVIRONMENTALRecord marked as outlier because it is outside the acepted environmental range/envelope of the speciesSame as #56All taxa recordsValidationLocationdecimalLatitude, decimalLongitude, various spatial layersErrorALAMerge with #56 - use the most robust test for determining environmental outliers (convex hull, jack-knife etc)
69
6653COORDINATE_DECIMAL_PLACES_MISMATCHCoordinates have a mismatched number of decimal places. Warning is raised if difference in number of decimal places between lat long is greater than 2.Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatimLatitude, verbatimLongitudeWarningALA
70
6754COORDINATE_SUSPECT_NUMBER_DECIMAL_PLACESLatitude and or longitude has a suspect number of decimal places. GPS receivers typically measure decimal degress to a maximum of 7 decimal places. Warning is raised if lat or long has greater than 7 decimal placesSame as #63Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatimLatitude, verbatimLongitudeWarningALAMerge with 63
71
6855SUPPLIED_COORDINATES_CONVERTEDSupplied coordinates may have been converted from another format. Warning is raised if lat or long has a decimal digit repeated 4 or more timesNeed a generic - coordinates converted but need howSingle RecordValidationLocationdecimalLatitude, decimalLongitude, verbatimLatitude, verbatimLongitudeWarningALAGeneralise test as converted from another corrdinate system? Subsume 61
72
69COORDINATE_INVALIDCoordinate value given in some form but GBIF is unable to interpret it.Generic failed test?Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatimLatitude, verbatimLongitudeGBIF
73
7047DECIMAL_LAT_LONG_CALCULATED_FROM_VERBATIMDecimal latitude and longitude were calculated using verbatimLatitude, verbatimLongitude and verbatimSRSDiscussSingle RecordValidation and ImprovementLocationdecimalLatitude, decimalLongitude, verbatimLatitude, verbatimLongitude, verbatimSRSWarningALA
74
7148DECIMAL_LAT_LONG_CALCULATION_FROM_VERBATIM_FAILEDFailed to calculate decimal latitude and longitude from verbatimLatitude, verbatimLongitude and verbatimSRSDiscussSingle RecordValidationLocationdecimalLatitude, decimalLongitude, verbatimLatitude, verbatimLongitude, verbatimSRSErrorALA
75
54geopoint_0_coordGeographic Coordinate had literal '0' values.Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioAs 53
76
72geopoint_similar_coordGeographic Coordinate had similar latitude and longitude (+/- lat == +/- lon).abs(lat) == abs(lon)Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioNeeded? Covered by other tests?
77
107COORDINATE_ROUNDEDOriginal coordinate modified by rounding to 5 decimals.DO NOT DO THIS!Single RecordValidation and ImprovementLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeGBIFUnwise! (Anything more than 5 is centimeters rather than meters - not sure we have anyone recording that fine att the moment - AC)
78
112CONTINENT_DERIVED_FROM_COORDINATESThe interpreted continent is based on the coordinates, not the verbatim string information.Use generic replacement (what was done and how)Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeGBIFAs 28, similar to #39, Generalize, combine with other "data added or replaced flag class"
79
113Latitude truncatedLatitude has been truncated to a fixed number of decimals placesSingle Record/datasetValidation and ImprovementLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeBISONUnwise!
80
114Longitude truncatedLongitude has been truncated to a fixed number of decimals placesSingle Record/datasetValidation and ImprovementLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeBISONUnwise!
81
115geopoint_boundsGeographic Coordinate was out of bounds.Same as #55Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeiDigBioOut of bounds of what? Country? or values ranges? similar to #55
82
73rev_geocode_eezThe latitude and longitude fall outside of any countries land borders, but fall within the exclusive economic zone of a country.Single RecordValidationLocationdecimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitude, habitat + many othersiDigBioRaises point about EEZ for marine included in country.
83
7419COORDINATE_HABITAT_MISMATCHMarine species reported in terrestrial area or vice-versa. Detection is dependent on high-resolution coastline at the time of recording, e.g., estuaries can change quickly (LB). Also could be an identification or name match error instead of a geospatial error (MN)Single RecordValidationLocationdecimalLatitude, decimalLongitude,
terrestrial spatial layer
ErrorALA
84
75rev_geocode_lat_signGeographic Coordinate had its Latitude negated to place it in correct country.Alex to resolveSingle RecordValidation and ImprovementLocationdecimalLatitude, verbatumLatitude, countryiDigBioSee also #51 - This is an Improvement for the Validation in #51, Clarify naming of flag, possibly merge with other values
85
762NEGATED_LONGITUDERecord appears to be referencing a location in the wrong hemisphereSingle RecordValidationLocationdecimalLongitudeWarningGBIF, BISONNeeds more specificity. decimalLongitude conflict with country or locality? Flag only?
86
7743LOCATION_NOT_SUPPLIEDno indication of location (coordinates, locality, polygon, location ID, verbatim coordinates) suppliedSingle RecordValidationLocationdecimalLongitude, decimalLatitude, locality, footprtinWKT, locationID, verbatimCoordinates, verbatimLatitude, verbatimLongitudeErrorALA
87
78rev_geocode_lon_signGeographic Coordinate had its Longitude negated to place it in correct country.Single RecordValidation and ImprovementLocationdecimalLongitude, verbatumLongitude, countryiDigBioSee also #76 - This is an Improvement for the Validation in #76, Clarify naming of flag, possibly merge with other values
88
7930MISSING_GEODETICDATUMgeodeticDatum not supplied for coordinatesSingle RecordValidationLocationgeodeticDatumWarningALAICSM 2000
89
8035INVALID_GEODETICDATUMThe geodetic datum is not valid. The geodetic datum (spatial reference system) is not recorded, or is not in controlled vocabulary. Lack of datum may add a further 200 metre error to the spatial error.Resolve 59,60,81, 82,83 (Lee)Single RecordValidationLocationgeodeticDatumWarningALA, GBIFICSM 2000200 meters refers to only a few datums (Australia?) - In NAD-WGS84 can be as high as 480 meters (from memory) in Aleutian Islands, and greatest distance is around 3,520 meters with an Indian Datum (again from memory) (AC)
90
8151GEODETIC_DATUM_ASSUMED_WGS84Geodetic datum assumed to be WGS84 (EPSG:4326)Single RecordValidationLocationgeodeticDatumWarningALA, GBIF
91
8252UNRECOGNIZED_GEODETIC_DATUMGeodetic datum not recognizedSingle RecordValidationLocationgeodeticDatumErrorALAAs 80?
92
83geopoint_datum_errorGeographic Coordinate has Invalid Geodetic Datum.Single RecordValidationLocationgeodeticDatumiDigBioAs 80?
93
84geopoint_datum_missingGeographic Coordinate Missing Geodetic Datum (Assumed to be WGS84).Single RecordValidationLocationgeodeticDatumiDigBioAs 79 (NB Specification is same as 81 (AC))
94
108COORDINATE_REPROJECTION_SUSPICIOUSIndicates successful coordinate reprojection according to provided datum, but which results in a datum shift larger than 0.1 decimal degrees.Single RecordValidation and ImprovementLocationgeodeticDatum, decimalLatitude, decimalLongitude, verbatumLatitude, verbatumLongitudeGBIF
95
8542MISSING_GEOREFERENCE_DATEGeoreferenceDate not supplied with the recordSingle RecordValidationLocationgeoreferenceDateWarningALANeeded?
96
8631MISSING_GEOREFERNCEDBYGeoreferencedBy not supplied with the recordSingle RecordValidationLocationgeoreferencedByWarningALANeeded?
97
8732MISSING_GEOREFERENCEPROTOCOLGeoreferenceProtocol not supplied with the recordSingle RecordValidationLocationgeoreferenceProtocolWarningALANeeded?
98
8833MISSING_GEOREFERENCESOURCESGeoreferenceSources not supplied with the recordSingle RecordValidationLocationgeoreferenceSourcesWarningALANeeded?
99
8934MISSING_GEOREFERENCEVERIFICATIONSTATUSGeoreferenceVerificationStatus not supplied with the recordSingle RecordValidationLocationgeoreferenceVerificationStatusWarningALANeeded?
100
9037GEOREFERENCE_UNCERTAINThe georeference is uncertain. If doubts expresssed regarding geocode, e.g. 'requires verification' or 'doubtful' or 'uncertain' or similar then exclude.Should be sufficient to assess the contents of georeferenceVerificationStatusSingle RecordValidationLocationgeoreferenceVerificationStatusErrorALADo not exclude, just flag
Loading...
Main menu