You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The centroid coordinates of the UTM5 squares in dagvlinders-inbo-occurrences seem truncated to 5 decimals, rather than rounded. Compare:
UTM5_VL_WGS84.xlsx
There is a reference file on Google Drive (
UTM5_VL_WGS84.xlsx
) with the correct, exact coordinates, calculated in QGIS.dagvlinders-inbo-occurrences
anddagvlinders-natuurpunt-occurrences
but other datasets as well. We should at least use the same reference file for all datasets.The text was updated successfully, but these errors were encountered: