Comprehensive guidance for migrating from Google Maps Platform to Mapbox GL JS. Provides API equivalents, pattern translations, and strategies for successful migration.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmapbox-google-maps-migrationExecute the skills CLI command in your project's root directory to begin installation:
Fetches mapbox-google-maps-migration from mapbox/mapbox-agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate mapbox-google-maps-migration. Access via /mapbox-google-maps-migration in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
40
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
40
stars
Comprehensive guidance for migrating from Google Maps Platform to Mapbox GL JS. Provides API equivalents, pattern translations, and strategies for successful migration.
.setMap(map)Key Insight: Mapbox treats everything as data + styling, not individual objects.
const map = new google.maps.Map(document.getElementById('map'), {
center: { lat: 37.7749, lng: -122.4194 },
zoom: 12,
mapTypeId: 'roadmap' // or 'satellite', 'hybrid', 'terrain'
});
mapboxgl.accessToken = 'YOUR_MAPBOX_TOKEN';
const map = new mapboxgl.Map({
container: 'map',
style: 'mapbox://styles/mapbox/streets-v12', // or satellite-v9, outdoors-v12
center: [-122.4194, 37.7749], // [lng, lat] - note the order!
zoom: 12
});
Key Differences:
{lat, lng}, Mapbox uses [lng, lat]| Google Maps | Mapbox GL JS | Notes |
|---|---|---|
map.setCenter(latLng) |
map.setCenter([lng, lat]) |
Coordinate order reversed |
map.getCenter() |
map.getCenter() |
Returns LngLat object |
map.setZoom(zoom) |
map.setZoom(zoom) |
Same behavior |
map.getZoom() |
map.getZoom() |
Same behavior |
map.panTo(latLng) |
map.panTo([lng, lat]) |
Animated pan |
map.fitBounds(bounds) |
map.fitBounds([[lng,lat],[lng,lat]]) |
Different bound format |
map.setMapTypeId(type) |
map.setStyle(styleUrl) |
Completely different approach |
map.getBounds() |
map.getBounds() |
Similar |
| Google Maps | Mapbox GL JS | Notes |
|---|---|---|
google.maps.event.addListener(map, 'click', fn) |
map.on('click', fn) |
Simpler syntax |
event.latLng |
event.lngLat |
Event property name |
'center_changed' |
'move' / 'moveend' |
Different event names |
'zoom_changed' |
'zoom' / 'zoomend' |
Different event names |
'bounds_changed' |
'moveend' |
No direct equivalent |
'mousemove' |
'mousemove' |
Same |
'mouseout' |
'mouseleave' |
Different name |
Google Maps:
const marker = new google.maps.Marker({
position: { lat: 37.7749, lng: -122.4194 },
map: map,
title: 'San Francisco',
icon: 'custom-icon.png'
});
// Remove marker
marker.setMap(null);
Mapbox GL JS:
// Create marker
const marker = new mapboxgl.Marker()
.setLngLat([-122.4194, 37.7749])
.setPopup(new mapboxgl.Popup().setText('San Francisco'))
.addTo(map);
// Remove marker
marker.remove();
Google Maps:
const markers = locations.map(
(loc) =>
new google.maps.Marker({
position: { lat: loc.lat, lng: loc.lng },
map: map
})
);
Mapbox GL JS (Equivalent Approach):
// Same object-oriented approach
const markers = locations.map((loc) => new mapboxgl.Marker().setLngLat([loc.lng, loc.lat]).addTo(map));
Mapbox GL JS (Data-Driven Approach - Recommended for 100+ points):
// Add as GeoJSON source + layer (uses WebGL, not DOM)
map.addSource('points', {
type: 'geojson',
data: {
type: 'FeatureCollection',
features: locations.map((loc) => ({
type: 'Feature',
geometry: { type: 'Point', coordinates: [loc.lng, loc.lat] },
properties: { name: loc.name }
}))
}
});
map.addLayer({
id: 'points-layer',
type: 'circle', // or 'symbol' for icons
source: 'points',
paint: {
'circle-radius': 8,
'circle-color': '#ff0000'
}
});
Performance Advantage: Google Maps renders all markers as DOM elements (even when using the Data Layer), which becomes slow with 500+ markers. Mapbox's circle and symbol layers are rendered by WebGL, making them much faster for large datasets (1,000-10,000+ points). This is a significant advantage when building applications with many points.
const infowindow = new google.maps.InfoWindow({
content: '<h3>Title</h3><p>Content</p>'
});
marker.addListener('click', () => {
infowindow.open(map, marker);
});
// Option 1: Attach to marker
const marker = new mapboxgl.Marker()
.setLngLat([-122.4194,<Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
glebis/claude-skills
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
wispbit-ai/skills
mapbox-google-maps-migration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: mapbox-google-maps-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: mapbox-google-maps-migration is focused, and the summary matches what you get after install.
mapbox-google-maps-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend mapbox-google-maps-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: mapbox-google-maps-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in mapbox-google-maps-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend mapbox-google-maps-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added mapbox-google-maps-migration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
mapbox-google-maps-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 44