The laws Google asked for changes were not limited to the mapping laws but any law to require domestic data centers, which might trigger the domestic tax issue at any moment. Your explanation that Borg couldn't handle domestic clusters doesn't clearly explain that Google eventually established SK data centers and started supporting vector maps anyway---and given that South Korea is not the only country with such requests (e.g. EU), not being able to cope with such laws is just a Google's fault.
Google data centers != Google cloud data centers
The two are logistically very different and consequently that means the types of workloads they host are also different. The latter is really for GCP usage only (both customers and Google-internal cloud infra necessary to host GCP). Compare https://www.google.com/about/datacenters/locations/ with https://cloud.google.com/about/locations.
1. SK vector maps were generated using domestic servers (but no Borg) as SK govt demanded.
2. Google "secretly" exported SK maps and generated vector maps using Borg anyway.
And both scenarios are problematic. The former would mean that the GP's claim that vector map generation requires Borg is not true or at least exaggerated (this scenario was what I had in mind when reading my sources, hence no verification). The latter would mean that... well, Google is in direct violation of SK law and not even trying to hide that.
Tax reasons might have arisen since, but maybe we're talking about different laws? I don't know. Do you?
The fact that there's no mention of Seoul at "Discover our data center locations" https://www.google.com/about/datacenters/locations/ tells me that its GCP region is most likely rented space in someone else's buildings and there are no full-blown Borg clusters with their usual tenants. Choosing where to build was always a complex process. There have been cases where announcements were made and land was bought, but nothing ever got built.
My explanation that.. "Borg couldn't handle domestic clusters"? What does that even mean? You could probably bring up a toy single-master Borg cell on a workstation with the right 283 command line flags and a toy Chubby cluster, but that still won't give you any map tiles.
Back in the days before incremental map updates, the whole globe's data came from a pipeline of pipelines and mapreduces, stitched together by a number of teams (the project's codename started with O). It was tracked with advanced technology (Google sheets) by PMs that had a taste for suffering. The latency was measured in weeks and months. If you missed the build, your data or code changes would take who knows how long to go live. I think that sometimes builds might have been abandoned altogether. These were the days when mobile Maps, if they existed at all, lagged desktop tiles by weeks or months (there wasn't one set only...). Same with navigation. The amount of data has only increased since, but there's obviously a much more advanced process at work nowadays. I don't know what they changed or how.
Anyway, back then, to build the SK tiles with the same tools you would have needed Borg, yes, but also Bigtable, GFS and a wide assortment of ancillary services. How are they doing it now? Maybe they finally got a license. Maybe they got a sufficiently limited subset of the full feed. Maybe they did a major rewrite of the code, pipelines and even binaries to make it feasible for that chunk of the planet to be handled by a bunch of bare Linux machines on GCP or AWS in South Korea. You might be able to deduce something by comparing updates there vs the rest of the world, but that takes time and dedication.
The South Korean mapping law allows for the domestic service (still subject to slight censorship), but Google didn't want to put any servers other than edge servers to South Korea so as a sort of protest it essentially froze the map for South Korea from November 2016 to December 2021, when Google finally gave up and established a new domestic data center.
Probably referring to this:
https://news.ycombinator.com/item?id=1873285 ("Nicaragua Raids Costa Rica, Blames Google Maps")
Speaking of, if you go click on the Ukraine label right now on Google Maps, you won't get the red outline showing their border. Click on a neighboring country label for a comparison.
Belarus: https://www.google.com/maps/place/Belarus/@53.696013,25.7358...
Ukraine: https://www.google.com/maps/place/Ukraine/@48.2486332,26.694...
https://www.google.se/maps?q=catalunya
Another explanation would be the dispute with Morocco about Perejil Island:
https://www.google.se/maps?q=isla+perejil
Or even the dispute regarding Gibraltar with Britain.
Whomever did this...
Militaries should probably prohibit personal smartphones completely. But I imagine such a prohibition would be a pretty big hit to morale and would also be very difficult to enforce, especially for non-combat areas where soldiers might not see the point.
https://www.abc.net.au/news/2004-05-23/rumsfeld-bans-camera-...
ISIS and the other Islamist factions in the Syrian Civil War were also using it extensively when fighting the Syrian Government forces and when planning their suicide attacks, but because Assad was the bad guy no Google action was taken (like restricting GMaps access in the area).
So it is not like the regulations are saying "you must shift the coordinates by this amount", which would be stupid. It's just that foreign map publishers have not obtained the license to use the correct datum for Mainland China, so they make do with another one.
Wikipedia: "GCJ-02 (colloquially Mars Coordinates, officially Chinese: 地形图非线性保密处理算法; lit. 'Topographic map non-linear confidentiality algorithm') is a geodetic datum formulated by the Chinese State Bureau of Surveying and Mapping and based on WGS-84. It uses an obfuscation algorithm which adds apparently random offsets to both the latitude and longitude, with the alleged goal of improving national security."
What I don't completely understand, for two reasons, is why foreign map publishers would allow this pseudorandom offset to exist on their mapping apps:
1. The obfuscation algorithm has basically been cracked.
2. I don't think the Chinese gov can do much about foreign companies, except maybe by proxy, by pressuring the national trade liaisons or some such.
Google famously left China, but still has offices there. It's impossible to ignore China if you want to develop the OS that runs on so many phones manufactured there (though I believe Google's own phones are built elsewhere). Apple obviously is completely reliant on China almost to a crazy degree. Microsoft caved to China on censorship to keep Bing from being blocked, they never left the way Google did. Facebook doesn't cooperate with China at all in their software products which are all banned, but they're increasingly getting into hardware and can't manufacture their hardware products without China.
Amap works as expected.
And militaries all over the globe do use Google Maps extensively, if not by policy then just by soldiers doing their own thing. Wrong borders in Google Maps have nearly led to international incidents when soldiers ended up on the wrong side of a border. And then there are the disputed borders that Google is forced to display differently in different countries. There is no globally accepted map and as a result the map Google shows you changes depending on where you're located.
[1] Actually I am out of date, it looks like the South Korea maps are vector based now. Maybe the law changed. It definitely used to be the case.