Vibe Coding and the Fragmentation of Open Source
The MapScaping Podcast - GIS, Geospatial, Remote Sensing, earth observation and digital geographyShow Notes
Why Machine-Writing Code is the Best (and Most Dangerous) Thing for Geospatial:
The current discourse surrounding AI coding is nothing if not polarized. On one side, the technofuturists urge us to throw away our keyboards; on the other, skeptics dismiss Large Language Models (LLMs) as little more than "fancy autocomplete" that will never replace a "real" engineer. Both sides miss the nuanced reality of the shift we are living through right now.
I recently sat down with Matt Hansen, Director of Geospatial Ecosystems at Element 84, to discuss this transition. With a 30-year career spanning the death of photographic film to the birth of Cloud-Native Geospatial, Hansen has a unique vantage point on how technology shifts redefine our roles. He isn’t predicting a distant future; he is describing a present where the barrier between an idea and a functioning tool has effectively collapsed.
The "D" Student Who Built the Future Hansen’s journey into the heart of open-source leadership began with what he initially thought was a terminal failure. As a freshman at the Rochester Institute of Technology, he found himself in a C programming class populated almost entirely by seasoned professionals from Kodak. Intimidated and overwhelmed by the "syntax wall," he withdrew from the class the first time and scraped by with a "D" on his second attempt. For years, he believed software simply wasn't his path. Today, however, he is a primary architect of the SpatioTemporal Asset Catalog (STAC) ecosystem and a major open-source contributor. This trajectory is the perfect case study for the democratizing power of AI: it allows the subject matter expert—the person who understands "photographic technology" or "imaging science"—to bypass the mechanical hurdles of brackets and semi-colons. "I took your class twice and thought I was never software... and now here I am like a regular contributor to open source software for geospatial." — Matt Hansen to his former professor.
The Rise of "Vibe Coding" and the Fragmentation Trap
We are entering the era of "vibe coding," where developers prompt AI based on a general description or "vibe" of what they need. While this is exhilarating for the individual, it creates a systemic risk of "bespoke implementations." When a user asks an AI for a solution without a deep architectural understanding, the machine often generates a narrow, unvetted fragment of code rather than utilizing a secure, scalable library. The danger here is a catastrophic loss of signal. If thousands of users release these AI-generated fragments onto platforms like GitHub, we risk drowning out the vetted, high-quality solutions that the community has spent decades building. We are creating a "sea of noise" that could make it harder for both humans and future AI models to identify the standard, proper way to solve a problem.
Why Geospatial is Still "Special" (The Anti-meridian Test)
For a long time, the industry mantra has been "geospatial isn’t special," pushing for spatial data to be treated as just another data type, like in GeoParquet. However, Hansen argues that AI actually proves that domain expertise is more critical than ever. Without specific guidance, AI often fails to account for the unique edge cases of a spherical world. Consider the "anti-meridian" problem: polygons crossing the 180th meridian. When asked to handle spatial data, an AI will often "brute force" a custom logic that works for a small, localized dataset but fails the moment it encounters the wrap-around logic of a global scale. A domain expert knows to direct the AI toward Pete Kadomsky’s "anti-meridian" library. AI is not a subject matter expert; it is a powerful engine that requires an expert navigator to avoid the "Valley of Despair."
Documentation is Now SEO for the Machines
We are seeing a counterintuitive shift in how we value documentation. Traditionally, README files and tutorials were written by humans, for humans. In the age of AI, doc
More from The MapScaping Podcast - GIS, Geospatial, Remote Sensing, earth observation and digital geography
Point clouds still feel a little bit like magic to me. You walk through a room, a city, or even just your living room with a scanner or your phone, and you can recreate it afterwards. But on their own, point clouds aren't actually that smart. So what would it mean for every single point to know not just where it is, but what it is, and how it relates to everything around it? My guest this week is Dr. Florent Poux, an adjunct professor, director of the 3D GeoData Academy, and author of 3D Data Science with Python. Florent has spent around 15 years on this one problem, and he developed the idea of the smart point cloud. And, as he pointed out just before we hit record, he's also a human, which we can't take for granted these days. In this conversation, we get into:
Cloud-Native Geospatial for Small Teams: How the Utah Geological Survey Did It What happens when a small, technical team at a state agency decides to go cloud native? They don't have terabytes of satellite imagery. They have lots of small datasets, lots of scientists and lots of people who just want to get at the data. In this episode, I talk with Marshall Robinson and Clinton Lunn from the Data Management Program at the Utah Geological Survey. They moved from a traditional ArcGIS Server setup to Postgres and GeoServer, and then to a cloud-native pipeline built on GeoParquet, PMTiles, and a STAC catalog. What I really wanted from this conversation was recipes. Picture a GIS person at a local council (say, here in New Zealand) who's curious about this stuff and needs a proof of concept to take to their manager. Where do they start? We talk about:
We already have a map. Actually, we have lots of maps. So why did Overture build another one? My guest in this episode is Amy Rose, CTO of the Overture Maps Foundation, and she makes a pretty compelling case. Overture isn't trying to replace OpenStreetMap — it sits downstream from it, and from hundreds of other sources, doing the unglamorous work of standardising all of that into something you can actually put into production. A light touch, as Amy puts it. Enough structure to be usable, not so much that the dataset starts trying to be everything for everybody. We spend a good chunk of the conversation on GERS — the Global Entity Reference System. It's a persistent ID stamped on buildings, roads, places, and addresses, which means the same building in OpenStreetMap, Google, Microsoft, and the City of Vancouver all share one identifier. If you've ever wrestled a messy spatial join into submission at 11pm, you'll understand immediately why this matters. And because Overture keeps all the source records, you're not stuck with their choice of polygon. You can go and pick your own. We also get into metadata, which Amy points out has been a dirty word for most of our careers — everybody wants it, nobody wants to write it. Except now it matters more than ever, because the biggest users of geospatial data aren't people anymore. They're machines. Humans are good at filling in missing context. Machines just produce a plausible answer and move on. That's a problem when there's critical infrastructure or human lives involved. Plus: whether "authoritative" still means anything, how signals and evidence might replace traditional contribution models, why there's no best representation of anything — only fit for purpose — and what Amy would add to Overture next if every other problem were magically solved. A really enjoyable conversation, and one that changed how I think about what a map actually is.
Republished Episode - I wanted to resurface this episode because positioning is everything, and it's a great overview of how it works.
Earlier this year I ran a small experiment called the Geospatial Launchpad — six weeks of working closely with a couple of people to help them push their geospatial projects forward. West was one of them. His project is Sentinel Bird (sentinelbird.com): an archive of every Sentinel-2 visit over the Gaza Strip since 2015, with 10-meter resolution imagery for each district, interactive comparison sliders, change-over-time timelapses, and a downloadable press pack — all free, no accounts, no paywall, licensed for anyone to use for anything. In this conversation, we get into what Sentinel Bird is, why West built it, and everything he ran into along the way — the marketing, the SEO, the feedback, all the stuff that has nothing to do with the tech but everything to do with whether a project actually goes anywhere. We talk about: