Issue 17683

hasCoordinate is always false in downloads

Reporter: peterdesmet
Type: Feedback
Summary: hasCoordinate is always false in downloads
Resolution: Fixed
Status: Closed
Created: 2015-07-13 18:12:16.048
Updated: 2017-10-05 14:18:27.308
Resolved: 2017-10-05 14:18:27.276
Description: I originally described this issue on January 15 while working on our GBIF datasets extension: I haven't tested it since.

In the download file, the field {{hasCoordinate}} is provided, which is [defined as|]:

bq. Boolean indicating that a valid latitude and longitude exists. Even if existing it might still have issues, see hasGeospatialIssues and issue.

In the downloads we tested however, that field was always {{false}}, even when valid coordinates were available. In the API, it works as it should.]]>

Author: hoefft
Created: 2017-10-05 14:18:27.304
Updated: 2017-10-05 14:18:27.304
this doesn't seem to be the case anymore neither for CSV nor dwC