But. Location accuracy 2kms https://www.inaturalist.org/observations/275802264 When I ID it displays on the map as a green dot (no green shaded circle!) I must remember to - either zoom out, or open the map in a new tab - to see that it is NOT AT the green dot, but within a much bigger circle - which does include the right location. Since I can see a familiar hotel in this picture, I know it is not up the mountain above the the houses where the dot is. (But first I wrote an indignant comment - no bullrushes up here! Check again … deleted my comment)
I regularly trip over this. Any chance we could have Location Accuracy displayed without all the extra clicks. It is not even visible if I open an obs in a new tab. I must still click again for Details.
If Location Accuracy was not hidden away, it might prevent some of the mistakes. Location Accuracy not recorded. Same difference if I try to work out - is this IN your garden, or a bit further over within the National Park?
(If the links are deleted you can find your own examples - with right or wrong location accuracy)
PS I am usually zoomed in on the map - especially on the Cape Peninsula.
Now I am confused. What was implemented in 2019? Rereading the threads - before my time on iNat - Location Accuracy was not displayed as a ‘hidden’ value ?
I do work from Identify. Now I realise my problem is with - Location Accuracy Not Recorded.
@tiwane Displaying the Accuracy in metres or kilometres is good. But if Not Recorded - that should also be displayed. Which would also help where I battle to convince an observer that (hidden) information is missing.
Please fix your locality resolution (or locality accuracy or locality error). Too large an accuracy, or missing accuracy, means that the data are not incorporated into checklists for the smaller nature reserves and places, and cannot be used for conservation planning and red listing purposes.
Ideally we like it to be 2-5m accuracy, but often one is uncertain, or does not know quite where one was, in which case it might be 100s of metres. but please if you genuinely dont know exactly where you were dont make them too precise, even if it is to the nearest km or two.
You need to enter this in when you add your observations. It shows up as a circle showing the area in which you were where you are uncertain as to exactly where the point should be. You can enter the value directly in metres for the radius of the circle.
Please see how to enter these when uploading you data in this tutorial: https://vimeo.com/167431843
To fix it, please click Edit (up top) and type in the value in the “Acc (m)” box, and/or adjust the circle around your locality in the map. While at it please give a decent locality name (the Googlemap names are atrociously vague) - but be careful not to press “search” after entering the name as that will corrupt your coordinates.
and save …
((please note: the app should record your locality accuracy automatically, if you take the photographs with the app. It wont if you add the photographs afterwards, in which case it needs to be manually inserted))
Oh my! Why do I have over 3,500 with accuracy not recorded?!?!
Quite frankly, I don’t want to go through each of these to add accuracy information, but I would be interested in figuring out why iNaturalist isn’t adding this from my cellphone submissions. Any idea?
If you read thru the copypasta comment from TR above - he understands how iNat works. I parrot what I find across iNat obs and here in the Forum.
I know my hiking companions - who use cellphones and add to iNat as they go - sometimes get slightly weird locations, when I know they were not There Then. We have poor cellphone reception on our mountain hikes.
As far as I can tell all of mine are from cellphone submissions, and I have mostly been in areas with good reception (UK, northern Ohio, Tampa Florida, Tucson Arizona). I am confident that the vast majority of those 3,500+ are extremely accurate, but that doesn’t explain why my submissions don’t enter accuracy. =/
I had a quick scan of these, and have checked my Android’s settings. Accuracy should be enabled, but alas, that is not transferring to iNat when I add my images. I’m going to put this to the back of my mind, as I have no intention of going through that many observations.
If there were a way to bulk-update them, that would be a different matter…
Perfect. I was aware of the Batch Edit screen here, but I had no idea accuracy was one of the fields that could be updated in this manner. I appreciate your help.
Edit: I’ve tested this a few times and I’m already down to just 3000. Thanks again
I take the photos first with my cellphone, then later (usually) I create a new observation on iNaturalist using ‘Choose Image’, which collects most of the metadata (location, date, time, etc) before submitting. Rarely do I take photos within the iNaturalist App.
Thanks! I do the same, and normally the accuracy/precision value is imported into the app. I just checked with both versions of the iPhone app and both are working ok with this workflow. If you can replicate, it would be great to file a bug report including your phone model, operating system and app version, as this is likely affecting many other users too.
I did find some 40-odd of my >13,000 observations lacking an accuracy value through Diana’s link, so it’s not clear to me if this is an intermittent bug, occurs in only some versions of the app, or something else.
