Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

-1 coordinate precision should not be interpreted as 1 #65

Closed
gbif-portal opened this issue Feb 7, 2017 · 1 comment
Closed

-1 coordinate precision should not be interpreted as 1 #65

gbif-portal opened this issue Feb 7, 2017 · 1 comment
Labels
bug duplicate

Comments

@gbif-portal
Copy link
Collaborator

-1 coordinate precision should not be interpreted as 1

Should we not simply discard, rather than alter that?
Looking at the record diagnostic view, it seems "-1" is used for NULL

fbitem-occurrence1135583752
Reported by: @timrobertson100
System: Chrome 55.0.2883 / Mac OS X 10.11.5
Referer: https://demo.gbif.org/occurrence/1135583752
Window size: width 1721 - height 1099
API log
Site log
datasetKey: 38b4c89f-584c-41bb-bd8f-cd1def33e92f
publishingOrgKey: b8323864-602a-4a7d-9127-bb903054e97d
@cgendreau
Copy link
Contributor

Moved to gbif/occurrence#9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cgendreau @gbif-portal