Hello All,

Thank you for your thoughtful comments and suggestions!

Note: The GitHub link has been updated: https://github.com/Archit1706/temporary-road-closures

Reply to Mxdanger: You raise excellent points about agency integration and in-app reporting! While we initially planned OsmAnd integration, we’ve now pivoted our approach. Instead of direct OSM integration, we’re building a closure-aware routing system that can handle multiple transportation modes (car, bicycle, pedestrian). This means users can get optimal routes that account for temporary closures—regardless of their preferred mapping platform.

Reply to stanton: Thank you for the detailed information about TraFF! Your work on traffic information exchange formats is impressive, and I appreciate you sharing the specification. You’re absolutely right about keeping event data separate from core OSM data—this aligns perfectly with our new direction. The TraFF format could be very valuable for data exchange between systems.

Reply to 4004: Thanks for mentioning Magic Earth! You’ve highlighted exactly why we changed direction. Instead of relying on OSM conditional tags or parsers, we’re creating a dedicated closure-aware routing engine. This allows us to provide real navigation that avoids closures, rather than just displaying them.

Reply to stanton (second comment): Your note about the OSM rule for temporary features (lasting at least a week) reinforces why we’ve moved away from direct OSM integration. Our new approach keeps closure data completely separate and offers closure-aware routing as a service, which can work with any map data source.

We’re now focused on building a routing system that can intelligently handle temporary closures for cars, bikes, and pedestrians—making it more practical for real-world navigation scenarios.

Thanks again for all the valuable feedback and support! —Archit

Hello All,

Thank you for your comments!

Note: The GitHub link has been updated: https://github.com/Archit1706/temporary-road-closures

Reply to Yod4z: The openeventdatabase is a great project—thanks for sharing! However, it only supports point closures. The Temporary Road Closures project now supports LineStrings (road segments) with directional data, as well as point closures. It also includes infrastructure closures that affect only specific transportation modes such as cars, bicycles, or pedestrians.

Reply to !i!: Thanks for sharing the live data sources. I’ll explore how they can be integrated into the database. Until now, I’ve only had access to Swiss Hiking Data. I’m also working on detailed documentation so that anyone can report live closures more easily.

Thanks again for the support! —Archit