Google Maps began labeling the lake that straddles the U.S.-Canada border as “Lake America” for U.S. users on May 4, 2024, following an executive order signed by President Donald Trump directing the Interior Department to rename the feature in the Geographic Names Information System (GNIS). Apple Maps added the same label on May 7, extending the change to millions of commuters, travelers and students who rely on the platforms for navigation.
The order, issued in early May, instructed the Interior Department to update the GNIS database. Interior Secretary Doug Burgum told Fox’s “Mornings with Maria” on May 6 that President Trump had asked the agency to make the change and had specifically requested Apple implement it. Google rolled out the update two days earlier, becoming the first major mapping service to comply; Apple followed three days later. MapQuest announced it would retain the historic name, citing a commitment to established geographic conventions.
The rename is limited to U.S. users. Canadian mapping services continue to display “Lake Ontario,” and many international providers show both names. The split raises questions about cross‑border data standards, the authority of an executive order over a feature that exists in two sovereign nations, and the cultural impact on Indigenous peoples who have called the waterway Lake Ontario for centuries.
The Seneca Nation immediately condemned the change, calling it a breach of a 225‑year‑old treaty and an affront to Indigenous heritage. Canadian officials expressed concern that a unilateral U.S. rename could cause confusion for travelers, emergency responders and shared environmental management.
Legal scholars note that presidential authority to rename a trans‑border geographic feature is unsettled. The order applies only to the U.S. side of the GNIS, which feeds data to private‑sector mapping services operating in the United States. Outside the United States, the GNIS has no jurisdiction, allowing other providers to retain the historic name. The situation underscores the limits of domestic policy when geographic features cross sovereign lines.
For tech companies, the episode illustrates the operational burden of complying with politically driven data requests. Updating a global geographic database requires coordination among engineering, legal and product teams and sets a precedent for future naming directives. A similar order last year renamed the Gulf of Mexico as “Gulf of America,” which Google and Apple also adopted.
The practical impact is immediate. Drivers using Google or Apple Maps in New York State will see “Lake America” on routes that skirt the shoreline, while Canadian users continue to see “Lake Ontario.” Educators, publishers and media outlets that source data from these platforms may need to reconcile the differing names in their materials.
The issue remains unresolved. No court has ruled on the scope of presidential power over trans‑border place names, and diplomatic talks between the United States and Canada have not publicly addressed the rename. As more mapping services decide whether to follow the order, the broader question will be how private‑sector data standards balance compliance with domestic policy against the need for consistent, internationally recognized geographic information.