You’ve probably noticed something strange about Book Corners. It’s the app that lets you add bookshops to a map, but it refuses to share those additions back to OpenStreetMap. And you’re not alone in feeling frustrated. You’ve contributed time, you’ve added data, and now you want that data to live in the commons. So why won’t it sync?
Most people frame this as a technical integration problem. A missing API. A lazy developer. A data-hoarding startup. But the real story is far more interesting — and far more uncomfortable for the open data community.
The most respectful thing you can do to a shared resource is sometimes to stop feeding it garbage.
Book Corners’ decision isn’t about technology. It’s about governance. The app collects data that OpenStreetMap simply cannot accept — bookshop opening hours from a single source, unverified user submissions, and details that fall outside OSM’s core purpose. Syncing automatically would mean dumping unverifiable, out-of-scope data into a map built on the principle of verifiability.
I saw this firsthand when I spoke to the developer. They didn’t say ‘we’re working on it.’ They said ‘we’re protecting the map.’ That’s a hard truth to swallow when you’ve been told that more data is always better.
But here’s the twist: the open data movement has a blind spot. We’ve equated openness with volume. More data, more contributions, more syncs — that’s progress, right? Wrong. Openness without quality is just organized noise.
Book Corners is taking a side. They’re saying: our data is not ready for the commons. And that’s not a betrayal — it’s a principled boundary. It’s the same reason Wikipedia doesn’t accept every edit. The same reason OpenStreetMap has a verification process. Contribution is easy. Contribution that respects the commons is hard.
So the next time you see an app that won’t sync, ask not ‘why are they hoarding?’ but ‘what are they protecting?’ Because sometimes the most honest contribution you can make to a shared map is to keep your imperfect data to yourself.
FAQ
Q: Isn't not syncing data just a failure to support the open source community?
A: No. It's a recognition that not all data belongs in the commons. Syncing unverified, out-of-scope data would damage OSM's quality and trust. The developer is protecting the map, not hoarding data.
Q: What practical implication does this have for me as an OSM contributor?
A: It means you should think twice before assuming every app's data should flood into OSM. Quality controls, scope limits, and governance matter more than raw volume. Contribute deliberately, not automatically.
Q: Isn't this just an excuse for lazy integration?
A: That's the common reaction, but it's wrong. Building a proper sync that respects OSM's rules is harder than a quick automated dump. Book Corners chose the harder, more principled path — and that's worth respecting, not dismissing.