Bulk upload issue - neg. GPS latitude incorrectly uploaded as positive

In which Wildbook did the issue occur? ACW

What operating system were you using? Win 10

What web browser were you using? Latest chrome

What is your role on the site? admin

What happened?
Bulk upload - spreadsheet contained decimal latitude as a negative (-19.239619999999999) but latitude in encounter record shows as a positive
Ex#1: https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=a9f87742-acbf-4c0f-9668-7137f10ec1bf

Ex.#2: https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=d4148996-4f78-4fec-aba6-207811584241

There are 2 sets of bulk uploads that have this issue.

What did you expect to happen? I expected the system to correctly upload the negative to ensure location is correctly mapped

What are some steps we could take to reproduce the issue?

Thanks for reporting this, that’s a serious problem.
We’ll be investigating this issue and tracking it under WB-599.


Can you provide me with the excel file where this occurred? I was unable to replicate with other excel samples I have so there must be something unique about the file.



This is now fixed, and has a two tiered explanation. The file I was able to replicate this in was Mini_upload_folder_144_06112020.xlsx a file that had lat/lon for all encounters. If you edit the
fields for these numbers, there is a leading apostrophe.

This non numeric character triggered some error handling that attempted to to clean the value up,
and ended up stripping off not only the apostrophe but the negative symbol. Since the result is a valid value, it was set on the encounter and not rejected.

I’ve made a small change to allow negative symbols through so this should not occur in the future, even if the fallback behavior is triggered. The change is now deployed on ACW.