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 |
ansell
changed the title
|
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 97731494indr376) doesn't look like it is sensitive, but thedecimalLongitudeon it has been modified by the processor.https://biocache.ala.org.au/occurrences/8b621b42-7829-4b52-b618-98945b5598ef
The original line in the
dr376dump that it was loaded from is the following, which includes25asdecimalLatitude,135.4asdecimalLongitude,"25,00,,S;135,24,,E"asverbatimCoordinates, and10000ascoordinateUncertaintyInMeters:The record in Cassandra appears correct for
decimalLongitudebut notdecimalLongitude_p:Running
biocache process-single 8b621b42-7829-4b52-b618-98945b5598efin verbose logging mode shows the following which I can't find any further clues in as whendecimalLongitudefirst appears on the processed record it shows up as135.0:The text was updated successfully, but these errors were encountered: