# Book Corners Halts Data Sync to OpenStreetMap Unexpected challenges of open data sharing for small projects revealed. - **Source:** [Hacker News (news.ycombinator.com)](https://brifing.si/source/13c923cd-6d99-442b-9b8b-1181f4d8cd91) - **Published:** 2026-08-03 - **Original article:** - **On Brifing:** https://brifing.si/s/07fbb599-2964-4cff-ad4c-d186948191bd ## Project Starting Point Book Corners began with OpenStreetMap data containing thousands of public bookcases worldwide. Users could submit new library locations and photos, which became public after moderation. The project aimed to create a fair system to send missing bookcases back to OSM. ## Technical Integration Plan The idea of sending data via API initially seemed simple: user consent, contribution tracking, preview generation, and OSM authentication. However, OSM's Automated Edits rules and Import Guidelines introduced unexpected administrative burdens for a small project. Even individually reviewed submissions fell under script-assisted changes category. ## Licensing Challenges OSM requires all data to be shared with compatible licenses. Transferring a bookcase submission from Book Corners to OSM requires separate licensing agreements. New consent mechanisms would be needed to help users understand this distinction. ## Ongoing Responsibilities Sending data to OSM isn't just technical integration but an ongoing process requiring continuous monitoring. Establishing operational infrastructure for documentation, community feedback, error management and potential data rollbacks represents long-term commitment for small teams. ## Data Quality Dilemma OpenStreetMap has strict rules against bad imports that could create thousands of duplicate records or overwrite local knowledge. A 2021 study showed 34% of OSM errors originated from automated imports. The community considers these controls necessary to maintain map quality. ## Opportunity Cost Time spent on OSM integration would come at the expense of Book Corners' core development. Investing in user experience, moderation tools and mobile apps offers more sustainable value for a small project compared to maintaining data export pipelines. ## Future Scenarios The decision could be revisited if the project grows significantly or if OSM community develops lighter workflows. Alternatively, indirect methods like letting users propose changes through existing OSM editors might be considered, though these still require community discussions. ## Lessons for Open Data Ecosystem This experience highlights administrative barriers small projects face in open data sharing. Beyond technical feasibility, organizational commitments must be evaluated. OSM's strict rules maintain data quality but can inadvertently discourage contributions from side projects. ## Sources covering this story - https://www.andreagrandi.it/posts/why-book-corners-wont-sync-contributions-back-to-openstreetmap/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._