News for hackers. Stuff that matters.
Re:Map Data: False Assumptions by iso1631 on Tuesday June 21, 2022 @06:35AM (#31822351)
I note the page didn't specifically mention disputed territory (only in passing). Crimea, Western Sahara, Israel and that area, Navassa Island, etc.

What country does your program display for Tiraspol? Jericho? Jerusalem?

Re:Map Data: False Assumptions by dme1 on Tuesday June 21, 2022 @08:14AM (#31822960)
Hi, author here. Thanks for reading my stuff! :-) I did not go into details of geopolitical issues because I covered that in an earlier article: https://solutionspace.blog/2022/05/23/map-data-ii-the-role-o...
Re:Map Data: False Assumptions by Lex-2008 on Tuesday June 21, 2022 @07:08AM (#31822548)
I'm not sure if your question is rhetoric, but somewhere I've read that some map providers show it depending on what country the user (website visitor) is in - so users in country A see the disputed territory as belonging to country A, users in country B see it as belonging to their country, and everyone else sees this territory as "disputed between A and B".

Governments of both A and B might have opposite demands from the same map-making company and threat it with legal consequences.

Also, in recent news: https://yandex.com/maps/ decided not to show country borders at all: https://techcrunch.com/2022/06/09/yandex-maps-no-borders/

Re:Map Data: False Assumptions by fleddr on Tuesday June 21, 2022 @08:11AM (#31822947)
In Google Maps, when reverse geocoding a point on the map that is disputed, the result will not return any country identifier. They base this logic on the UN list of disputed areas.
Re:Map Data: False Assumptions by fatnoah on Tuesday June 21, 2022 @08:09AM (#31822933)
This is how things were handled at Facebook. Your view of a disputed border depends on your country. i.e. You'll see whatever borders are favorable to your own country's interpretation.