-
Notifications
You must be signed in to change notification settings - Fork 24
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
Why is decimalLongitude being modified during processing on these records #324
Comments
Two tickets on helpdesk referencing this:
The other is for another record in https://biocache.ala.org.au/occurrences/c69255a5-55bc-4d9d-8b68-382b2616c4a7 |
On first look, I think it's reprojection of AGD84 to WGS84 (EPSG:4326), and GDA94 to WGS84. |
Thanks, I knew I was missing something but didn't click that it was that. |
A further query from the support ticket has been made, as it doesn't appear that AGD84 to WGS84 explains this issue by a few orders of magnitude. There may be something else occurring.
|
Also, coordinate conversion on functional test data seems for be failing for datums supplied as AMG66 or GDA94. |
The following record, (
AD 97731494
indr376
) doesn't look like it is sensitive, but thedecimalLongitude
on it has been modified by the processor.https://biocache.ala.org.au/occurrences/8b621b42-7829-4b52-b618-98945b5598ef
The original line in the
dr376
dump that it was loaded from is the following, which includes25
asdecimalLatitude
,135.4
asdecimalLongitude
,"25,00,,S;135,24,,E"
asverbatimCoordinates
, and10000
ascoordinateUncertaintyInMeters
:The record in Cassandra appears correct for
decimalLongitude
but notdecimalLongitude_p
:Running
biocache process-single 8b621b42-7829-4b52-b618-98945b5598ef
in verbose logging mode shows the following which I can't find any further clues in as whendecimalLongitude
first appears on the processed record it shows up as135.0
:The text was updated successfully, but these errors were encountered: