Observations with locations at 0,0

There are a number of observations with these coordinates (0,0). Perhaps these could be bulk edited to be set as location inaccurate?



Edit: I misread your post as asking why so many were set at 0,0, with my answer below. They do get to a project called “NULL”, but maybe some other marker would be useful as you suggested.

I suspect they may happen when someone tries to manually set a location in the app. When you upload a picture without any location information, it leaves location blank, so you click edit “location” then “edit location” and it starts your marker at 0,0. If something happens at this point and the user doesn’t select a more accurate location, then that’s what is recorded.

1 Like

Interesting thanks. That is something that should be changed then, Null should not be the same as 0,0.

This seems like a good idea. The “Null” project, as someone mentioned, captures these, but it does not capture observations with location (0,0) which are auto-obscured. You can see this clearly here, for example this observation. Some of these observations achieved Research Grade - I just went through and marked these “location inaccurate”.

In most cases, observers seem not to be aware there is a problem. Could there be a way of alerting observers that some of their locations have been mapped to the middle of the ocean, perhaps with a notification?


I went and left a comment with instructions as well as voting no to the location is accurate on the records which were : research grade, birds, reptiles or mammals (I grew tired of the repetition, so others can try other families)

The reality is almost all of these come from users who

  • use the mobile app so are unlikely to see the comment
  • or have very low observation counts suggesting they used the app once or twice and have since stopped

So the reality is a very low number will likely ever get fixed by the user.

Thanks Chris. I have done the same with the rest of the Research Grade observations there for other taxa.

One other thing I noticed: observations stay in the “NULL” project even after their location has been fixed. It would be good to convert the NULL project to a collection project, an option which was not available when this project was created - @silversea_starsong as the creator of this project, is that something you agree with? It should be a square of the same size as the bounding box that encompasses obscured observations.

I still think an automated way to fix this problem would be good. Another idea is that once a day/week/month, a script could check for newly created (0,0) observations and add a vote for “location inaccurate” to the DQA. This could be easily over-ridden by the observer in the unlikely case that anyone actually observes something at precisely (0,0).


I will look into this. Thanks for the notification!

I updated the project – it now also includes observations that are auto-obscured and marked at Lat/Long (0,0).


FWIW I was recently alerted by someone commenting in half a dozen of my obs that they were in the null project. I had no idea they were there, and missing from their collection Projects. After that I searched for any more in the null Project, but it would have been good to know straight away. And I have not remembered to check that project since - must do that.

I don’t use the mobile app, and have over 11,000 obs. I don’t know how I failed to provide a location, but I have had other obs since lose their location data, while I was editing location I think. But with those ones I was aware of it and fixed it straight away.

1 Like

Great! Does that mean that if due to a Conservation status something becomes auto-obscured, we will see it in the Null Project?

1 Like


I checked in again in the region of 0,0 and 13 observations had reached Research Grade in the last week: about two per day. I’ve marked them as location inaccurate with a note to the observer, but if anyone else wants to check in periodically to do the same, you can do so here.

All but one of these observations was also found through the NULL project. The exception was this observation - I am not sure why it didn’t get included in the NULL project.


Not certain but I suspect the 16,000 kilometer accuracy circle might be the cause of it not being in the project.


I added this as one of the ways to help out on iNat, as well as drafted some example text to leave for users who mistakenly saved their obs at 0,0:


Nice! Thanks Cassi!