All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

NUKEMAP's Migration from Google Maps to Mapbox+Leaflet: A Technical History

By

fanf2

4mo ago· 15 min readenInsight

Summary

The article explains why NUKEMAP, a nuclear effects visualization tool created in 2012, switched from Google Maps to Mapbox+Leaflet. The creator details how Google Maps API was initially ideal for the project due to its free access, active developer community, and ease of use for creating mapping mashups. However, changes in Google's API pricing and policies eventually made it unsustainable for the project, leading to the migration to alternative mapping solutions. The piece provides historical context about the tool's development and the technical considerations behind the platform switch.

Key quotes

· 3 pulled
When I created the NUKEMAP in 2012, the Google Maps API was amazing. It was the best thing in town for creating Javascript mapping mash-ups, cost literally nothing, had an active developer community that added new features on a regular basis, and actually seemed like it was interested in people using their product to develop cool, useful tools.
NUKEMAPs of days gone by: On the left is the original NUKEMAP I made way back in March 2005, which used MapQuest screenshots (and was extremely limited, and never made public) and was done entirely in PHP.
The top-secret story of why NUKEMAP switched from Google Maps to Mapbox+Leaflet.
Snippet from the RSS feed
The top-secret story of why NUKEMAP switched from Google Maps to Mapbox+Leaflet.

You might also wanna read