You’ve probably tried to pull Spanish land data before. Maybe you needed property boundaries for a real estate app, cadastral parcels for an agricultural analysis, or zoning info for a construction project. And after spending an hour wrestling with a SOAP envelope, staring at WSDL files that looked like they were beamed in from a previous millennium, you probably swore and walked away.
That’s because Spain’s official cadastre API — the gateway to one of Europe’s most complete land registries — runs on SOAP from 2003. Yes, the same protocol that made sense when George W. Bush was president and the iPod was still a novelty. It’s technically open data. But open data that requires a time machine to use isn’t really open at all.
“Open data isn’t open if it requires a Ph.D. in legacy systems to access it.”
Here’s the rub: the Spanish government didn’t lock the data behind a paywall. They didn’t even require an API key for basic queries. They just… stopped updating the interface. The SOAP API works. It’s just built for a developer world that no longer exists. Modern apps communicate over JSON, REST, and GraphQL. So every time a developer hits the cadastre endpoint, they have to parse complex XML, deal with arcane authentication flows, and write code that feels like a museum piece.
I hit this wall myself. And after a day of existential dread, I did what any pragmatic developer would do: I built a JSON wrapper. It sits between the ancient SOAP service and the modern world, translating every endpoint into clean, RESTful JSON. It also supports MCP (Model Context Protocol) for AI agents, because why not make the future feel easy?
“The real bottleneck isn’t data availability. It’s the accumulated technical debt of a government that refuses to upgrade.”
Let’s talk about that debt. Spain isn’t an outlier — governments everywhere run on code from the early 2000s. The problem isn’t that the data is secret. It’s that the pipes are rusty. The cadastre contains over 70 million parcels, millions of owners, and a century of property history. That dataset is a goldmine for developers, researchers, and startups. But the SOAP barrier turns a goldmine into a minefield.
My wrapper changes that. Now any developer can query the cadastre with a simple HTTP request: GET /parcel?ref=12345. No SOAP, no XML namespace hell, no parsing guide required. The response is clean JSON. And because it’s an MCP server, AI tools can ask it questions natively. “What’s the land area of parcel X?” becomes a natural language query.
But here’s the twist that most people miss: this wrapper is a band-aid. A brilliant, useful band-aid — but still a band-aid. The real fix would be for the Spanish government to modernize their API. But governments move slowly, and developers need solutions now. So wrappers like this are the de facto bridge between what’s available and what’s usable.
“Every wrapper you build is a confession that the system isn’t working. But it’s also a lifeline for the people who need the system to work.”
If you work with Spanish real estate, geographic data, or public sector APIs, this wrapper will save you hours of pain. But more importantly, it’s a case study in why open data ≠ accessible data. The data is free — but the cost of accessing it has been your time. Now it’s just a URL.
The API is live at prediohq.com. Go fetch some parcels. And maybe send a polite email to your local government asking them to upgrade. Because the only thing worse than a SOAP API from 2003 is a SOAP API from 2003 that nobody bothered to wrap.
FAQ
Q: Why can't developers just use the SOAP API directly?
A: They can—if they enjoy writing XML parsers, managing complex envelope structures, and handling authentication flows that feel like a puzzle from 2003. The protocol is archaic, poorly documented, and requires hours of setup for even a simple query. Most developers give up before they get a single response.
Q: What practical applications does this JSON wrapper unlock?
A: Anything that needs Spanish land data: real estate valuation platforms, agricultural analytics, construction planning, environmental studies, or even AI agents that need to verify property boundaries. The wrapper turns a nightmarish integration into a clean REST call, enabling startups and researchers to build features that were previously too painful to implement.
Q: Isn't this just a temporary hack? Shouldn't we push the government to modernize instead?
A: Yes and yes. The wrapper is absolutely a workaround—a band-aid on a systemic wound. But governments move at the speed of legislation, not code. Incumbents have every incentive to not upgrade (budget constraints, inertia, risk aversion). While we wait for that modernization, wrappers like this are the only path to actually using open data. They're not a solution; they're a bridge. Use the bridge, and send a letter demanding a better road.