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.

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

Coordinates truncated instead of rounded to 5 decimals #108

Open
peterdesmet opened this issue Mar 8, 2016 · 1 comment
Open

Coordinates truncated instead of rounded to 5 decimals #108

peterdesmet opened this issue Mar 8, 2016 · 1 comment

Comments

@peterdesmet
Copy link
Member

The centroid coordinates of the UTM5 squares in dagvlinders-inbo-occurrences seem truncated to 5 decimals, rather than rounded. Compare:

source code latitude longitude
UTM5_VL_WGS84.xlsx 31UFS37D 51.187358423409357 4.96755503170692
Vlinderdatabank record 31UFS37D 51.18735 4.96755
Waarnemingen.be record 31UFS37D 51.18735 4.96755

There is a reference file on Google Drive (UTM5_VL_WGS84.xlsx) with the correct, exact coordinates, calculated in QGIS.

  • We should probably load that set of coordinates in our DB to retrieve and round coordinates per UTM square or figure out the process of how the coordinates were calculated in the DB table we're currently using.
  • Depending on where the file is used, this might not only apply to dagvlinders-inbo-occurrences and dagvlinders-natuurpunt-occurrences but other datasets as well. We should at least use the same reference file for all datasets.
@stijnvanhoey
Copy link
Contributor

  • The IPT of the vlinderdatabank gets the coordinates in the NBNdatabase, so I expect indeed that this will be a problem that appears in other data sets generated from NBNdata as well
  • Moreover, this is the accuracy of the original dbase table, so the dbase-admin has been asked to change this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants