it may be worth noting, too, that Android’s definition of positional accuracy is that the true location has a 68% probability of being within that number of meters from the recorded coordinates.
iOS’s positioning error is not defined publicly, as far as i know, except to say that their is as least as good as Android’s definition. this is why this should be expected at least some of the time:
note that this is very different from the recommendation from many people that observers make sure the accuracy circle will always include the true location when adding or adjusting the accuracy manually.
when people adjust accuracy values, they generally will do this in relation to some sort of map, but the accuracy of the maps / satellite images is not perfect, and generally you won’t know what their underlying error is.
there’s also no telling whether the coordinates represent the location of the subject or the observer’s device or something else entirely.
all that inconsistency is why recording arbitrary accuracy values just to satisfy some other user’s arbitrary requirements is totally unnecessary, as far as i’m concerned. it’s unlikely those other users really understand what any particular location / accuracy value actually represents anyway.