Great, thanks, looks like the null validation is live and there aren’t new observations coming in at 0, 0.
I was trying to test out what exactly happens when I try to make an observation at 0, 0 on Android, and it looks like it just won’t upload the observation. Weirdly though, it totally disappears from my list of observations, so I’m also not able to find it in order to try editing the location, or even just to delete it, in order to make the “Sync 3 observations…Upload” message go away. I had made 3 observations trying to see if adding a different date, or adding an ID that I could search for would make it appear. But searching for the ID I added (human) still does not show the new/“null” location observation in my list of observations. Samsung S7 using 1.12.4 (363).
Short version: I tried to add an observation at 0, 0 on Android, but now I can’t find it on my app.
(cc: @kueda@budowski)
Here’s the message I’ve been using if anyone wants to help out:
Hi, it looks like the location was accidentally saved at coordinates 0,0 — in the Atlantic Ocean! :) To add a location, click the “Edit” button, and use the map to drop a push-pin to more accurately depict where you were when you made this observation. Even just a general location is helpful. For now, I marked this observation as having an incorrect location in the Data Quality Assessment section, so please reply here letting me know once you’ve fixed it. Thanks!
@bouteloua, how exactly are you making a 0,0 observation in the Android app? That should be close to impossible unless you’re using the simulator / virtual device and forcing the OS to always return 0,0 coordinates.
Create a new observation by choosing an image that doesn’t have any GPS coordinates, then try to add a location (“edit location” ) but save without making any changes. I’m not sure how all those other Android observations got created at 0, 0. This is the only way I know how to.
In reply to the other thread asking how to DQA these… it was suggested that a comment should be made in the first instance rather than just put the DQA, but I think they should be marked “location not accurate” immediately and the comment put as well, as the observer might never come back with a reply. If you know you yourself will be around to change your DQA should they respond and fix, then marking it inaccurate from the outset is a better option.
This may be too late to the game to help -
But about 1 in 10 of my observations’ location metadata gets stripped when uploading photos. When that happens 10/10 times all I have to do is reupload one photo and the coordinates will sync.
Even when I have bad service my Android always records a location, but the location may be inaccurate (but never set to 0,0). If I don’t catch the coordinates have been stripped it get puts to 0,0 (or used to at least). Thanks @bouteloua for catching those!
I’m looking forward to seeing how this new fix works out!
