
Maps ♥️ Open Source. Software Engineer at @Mapbox 🇫🇮 @stepankuzmin@mastodon.social
Helsinki, Finland
Joined May 2009
- Tweets8.7K
- Following2.5K
- Followers964
- Likes9.2K
StepanKuzmin retweeted
Leaflet v2 beta.4 released! Faster panning, more predictable tooltips, dozens of bug fixes and accessibility improvements and more as we get closer to the final release github.com/Leaflet/Leaflet/r…
Introducing the Mapbox plugin for ChatGPT. One plugin for Chat, Work, and Codex.
Mapbox brings location infrastructure for AI directly into ChatGPT — helping business teams, analysts, and developers turn location questions into decisions, interactive maps, and working applications.
📍 Compare potential store locations by drive time and proximity to existing stores.
📊 Map sales by territory to see where your team should focus next.
🗺️ Launch store locators and travel planning websites with ChatGPT Sites.
🛠️ Build web, iOS, and Android apps in Codex.
With 33 tools and 20 skills, the plugin connects ChatGPT to live location data and the knowledge to build with Mapbox.
Install the plugin, link your Mapbox account, and describe what you want to build. Learn more: mapbox.com/blog/introducing-…
#BuiltWithMapbox #LocationInfrastructureforAI #AImapping
StepanKuzmin retweeted
Leaflet 2.0.0-beta.3 is out! 🍃 Better keyboard and screen reader support, much faster events on layers with many listeners, zoomIn/panBy calls that add up during animations, stricter coordinate validation, and a pile of community bug fixes. Let's test! github.com/Leaflet/Leaflet/r…
StepanKuzmin retweeted
v2.0.0-beta.2 is out! Now with built-in fullscreen control, an i18n helper, improvements to canvas events, crisper zoom control, and a dozen bug and accessibility fixes. We're getting closer! Have a happy Friday and a nice weekend 🙌
github.com/Leaflet/Leaflet/r…
StepanKuzmin retweeted
🍃 1 year late, but finally here: Leaflet v2.0.0-beta.1 is out! ⚡️ Pure ES classes, fully tree-shakeable, first-class TypeScript types, faster rendering, much better accessibility, 40+ bugs fixed. Please please give it a try! github.com/Leaflet/Leaflet/r…
StepanKuzmin retweeted
It's been a while, but it's happening. ❤️ github.com/Leaflet/Leaflet/i…
StepanKuzmin retweeted
Save your AI tokens for what matters. We've got terrain generation covered worldwide.
terrain-atlas.pratikyadav.ch…
StepanKuzmin retweeted
realtime viewshed analysis in mapbox!
So many possible uses for terrain data in browser maps
StepanKuzmin retweeted
Pixelmatch, my image comparison library for visual regression testing, got a major overhaul: a new color difference metric (OKLab + HyAB) that's much closer to how we see color, a windowSize option to fight scattered noise, and more — while staying fast github.com/mapbox/pixelmatch…
StepanKuzmin retweeted
Next month is November, which means the #30DayMapChallenge 2026 themes are here!
More information on the official website: 30daymapchallenge.com/
StepanKuzmin retweeted
geojson-vt, which is responsible for GeoJSON processing in @Mapbox GL JS, just got a major overhaul — v5 now uses up to 4x less memory, so you can now visualize a lot more data without crashing the browser. Had a blast optimizing the hell out of it 🔥 github.com/mapbox/geojson-vt…
StepanKuzmin retweeted
For six months, Google Maps sent a slice of drivers in ten American cities down deliberately slower routes.
About 30 seconds slower on average, and under 2% of trips were touched. The experiment ran on roughly 100 of the most congested road segments in each city, switching on and off day by day so each city acted as its own control. The results are out now in Nature Cities, from Google Research with collaborators at Berkeley and Stanford.
The reasoning behind it is old and slightly counterintuitive. Every navigation app does the same thing: it finds you the fastest route right now, for you alone. When millions of phones do that at once they all pour onto the same handful of arteries, and those arteries stop being fast. Transport economists have been writing about the gap between what's good for one driver and what's good for the network since the 1950s. Nobody had tested a fix at city scale with real drivers, because you'd need to steer routing for a large share of a city's traffic, and about three companies on Earth are in that position.
So Google put a penalty on the worst segments during their worst hours, which nudged the routing engine towards alternatives of similar road class and comparable travel time, then measured what happened across the whole network on weekdays between 7am and 8pm.
On the targeted segments, traffic moved roughly 2% faster in the median city. Los Angeles got 4.56%, Atlanta 3.30%. Fuel burn on those stretches dropped between 0.5% and 1%. Across every road that saw a change in traffic, which covers around 80% of each city's driving, speeds rose 0.35%, reaching 0.5% during the morning and evening peaks. Total travel time on affected trips fell 0.69%. Their Bayesian model put the probability that the speed effect was genuinely positive at 99.8%.
That adds up to more than 1,000 tonnes of CO2-equivalent saved per year, per city, in most of the places studied. Cars and vans account for around 10% of global carbon emissions, and the average driver spends about 2.6 years of their life behind the wheel, so a fraction of a percent across an entire road network is a serious amount of fuel.
Per driver, the saving comes to about 0.25% of an average journey, roughly one fortieth of the normal day-to-day wobble in how long the same commute takes. Nobody in those ten cities noticed anything, in either direction, including the people sent the long way round.
The authors are careful about what they haven't shown. They measured the immediate effect, not what happens once drivers work out the freed-up route is quicker and pile back onto it, which is the standard way road improvements get eaten. Their penalty scheme was deliberately crude, so the ceiling on the approach is unknown. And the underlying Google Maps data is commercially confidential, so nobody outside can check the numbers.
The finding sitting underneath all this is that a private company's routing algorithm has become a piece of transport infrastructure, tunable in the way a traffic light or a congestion charge is tunable. The obvious follow-up experiments are the ones a city government would want to run, not the ones a mapping company would.
link to full article: nature.com/articles/s44284-0…
StepanKuzmin retweeted
Algú més es fan dels mapes de relleu? 🗺️
Fa temps que volia fer alguna eina per crear-los i, amb l'excusa d'aprendre una API de gràfics nova, vaig decidir posar-m'hi durant les vacances.
Les coses s'allarguen més del que toca, però el resultat és estrat.cat.
StepanKuzmin retweeted
I made a visual viewer for HTTP range requests when exploring a Cloud Optimized Geotif from a remote server
As you pan around, it shows you exactly which tiles are being pulled and exactly where the bytes are stored
Register for BUILD with Mapbox and share what you've built with the community.
Every great build starts with a challenge to solve. At BUILD with Mapbox, we're looking for stories from developers and teams creating better experiences with maps, search, navigation, AI, and location data.
Take the stage and bring us along:
📍25-minute presentation
📍10-minute Show & Tell
📣 Apply to present today: docs.google.com/forms/d/e/1F…
#BuiltWithMapbox #DeveloperConference #BUILDwithMapbox
















