Okay, I changed it. However, when I look under “Encompassing places”, it still says:
[East, NP] (State)
And I believe that stuff is true iNat attribution, not just an outside suggestion, right?
So it seems like something is still off there involving the mapping. The map clearly shows that that location is within West Bengal, India, and I placed it on a trekking route that is clearly on the Indian side of the border so far as I understand.
Also, the other issue is still there. I have all these other entries from that same route whose automatic place is West Bengal, India, and it looks like they should be in India based on the visual map, but their “encompassing place” is listed as Nepal as well.
I’m wondering if there’s something misaligned between the visual mapping and official mapping in that part of the world?
your observation does seem to fall within iNat’s standard place boundary for Nepal, which is based on a many-years-old definition from GADM. comparing this to the current OpenStreetMaps map, it looks like the iNat Nepal boundary (orange) is shifted to the the east:
i wonder if the GADM boundary was just defined this way? or was it projected incorrectly when iNat adapted it? or has there been a lot of tectonic shifting since the GADM boundaries were determined back in the day?
I have a similar Problem:
My observations at Mu Koh Surin National Park in Thailand are listed under Myanmar.
On the Google Map the location is correctly shown in Thailand, but if you click on ‘Details’ behind the adres you’ll see the ‘Encompassing Places’ here Myanmar is listed as country instead of Thailand.
based on a previous thread, it looks like maybe this is a known issue, and apparently this should be noted in a flag on the place:
iNat’s boundary for Belarus (in orange, adapted from GADM) looks shifted to the southwest vs the OSM boundaries. i’m guessing the boundaries may not have been projected quite right here when they were adapted from GADM, but i’m not sure. based on the Thailand example above, you might have to note the problem in a flag on the place, but probably it will not be corrected any time soon.