| ▲ | mcv a day ago | |||||||||||||
That's exactly what every executive order is: it's what the federal government uses. It's not binding for anyone else. It doesn't have the power of law. Google is under absolutely no obligation to do this. They do it explicitly to appease Trump. | ||||||||||||||
| ▲ | labcomputer a day ago | parent [-] | |||||||||||||
> They do it explicitly to appease Trump Well, actually, no. The EO changes the official name of the geographical feature as recognized by the US government. All the large map providers ingest a data feed from the USG (and other governments for other localizations) which names various geographical and place entities. That data goes through a pipeline (basically a CI pipeline) to build the map artifact and tiles served to users. Google just has a particularly good and low latency pipeline. Google got there in a couple days. Apple will get there in a week or two. The USGS will get there in god-knows-when. Mapquest has said they’re not going to update the name, which presumably means their pipeline is old and creaky. The article itself even acknowledges that the USGS GNIS database has already been updated to reflect the change. Unless someone at Google manually edits the entity, it will be automatically renamed with no human input (although, for very large, highly visible entities the validation stage may block the build and flag it for manual review) | ||||||||||||||
| ||||||||||||||