search

gbif / portal-feedback

User feedback for the GBIF API, website and published data. You can ask questions here. 🗨❓
30 stars 16 forks source link

The lat and long do not correspond to the location on the herbarium label #2350

Open gbif-portal opened 4 years ago

gbif-portal commented 4 years ago

The lat and long do not correspond to the location on the herbarium label

User: See in registry System: Chrome 79.0.3945 / Mac OS X 10.15.2 Referer: https://www.gbif.org/occurrence/1098964837 Window size: width 1274 - height 616 API log&_a=(columns:!(_source),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499')),sort:!('@timestamp',desc))) Site log&_a=(columns:!(_source),index:'prod-portal-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499')),sort:!('@timestamp',desc))) System health at time of feedback: OPERATIONAL datasetKey: 7b9a08ea-f762-11e1-a439-00145eb45e9a publishingOrgKey: 0674aea0-a7e1-11d8-9534-b8a03c50a862

ManonGros commented 4 years ago

Contacted the publishers by email.

This record is located on the US centroid. In fact, it seems like this dataset contains a lot of centroids (see screenshot below), I mentioned it in the email. Perhaps this will help improving the over all quality of the data. plant_collection_Botanische_Staatssammlung_Munchen

jholetschek commented 4 years ago

Forwarded your message to the maintainers of the BioCASe installation at SNSB (Andreas and Hans-Joachim are the curators, I suppose) and described how to remove the coordinates from the BioCASe mapping.

jhnwllr commented 7 months ago

The dataset does fill in coordinatePrecision, but it looks like they should fill coordinateUncertainty instead. https://www.gbif.org/occurrence/354513611 @DanBIF

DanBIF commented 2 months ago

Thanx, I have forwarded the error to the publisher (NHMD)

DanBIF commented 2 months ago

The issue with coordinatePrecision that should be mapped as coordinateUncertainty in https://www.gbif.org/dataset/7f4ed916-f762-11e1-a439-00145eb45e9a has been fixed.