there must be an alternate path in the code though, since based on the examples in this thread and what i’ve seen myself in the past, the upload does seem to sometimes (randomly?) determine location based on iNat places. for example, if the reverse geocoding service fails to respond or if there’s some sort of race condition, then maybe the fallback is to get a location based on iNat standard place boundaries?