Two things I would love to see in the FLOSS mapping ecosystem:
1. A POI/favorites app that maintains a local database with an API for other apps to access it. Apps could then store markers there instead of in their own private db, so that points added on one map app can be instantly available in other apps.
2. A shared traffic data service. Any OSM map app could contribute to the same data, helping reduce Google's advantage in live traffic data.
Obviously, both of these would need privacy protections and be subject to user choice. And there should also be some requirement that both reading and writing be supported, to ensure apps reading POI data don't lock in new data, and to prevent apps reading traffic data from freeloading.
> 1. A POI/favorites app that maintains a local database with an API for other apps to access it. Apps could then store markers there instead of in their own private db, so that points added on one map app can be instantly available in other apps.
Would an AT Protocol app or extension meet this need and requirements? By being stored in a PDS, the data can be permissioned, owned by the user, and easily migrated and/or shared.
Yess!
Please make an effort to improve underlying OpenStreetMap dataset:
https://streetcomplete.app - basic task-based, on-the-ground, app for Android
https://every-door.app - intermediate on-the-ground app for smartphones
https://rapideditor.org - AI-assisted mapping in browser
https://www.hotosm.org - task-based mapping in browser
https://josm.openstreetmap.de - advanced editor for desktop
Two things I would love to see in the FLOSS mapping ecosystem:
1. A POI/favorites app that maintains a local database with an API for other apps to access it. Apps could then store markers there instead of in their own private db, so that points added on one map app can be instantly available in other apps.
2. A shared traffic data service. Any OSM map app could contribute to the same data, helping reduce Google's advantage in live traffic data.
Obviously, both of these would need privacy protections and be subject to user choice. And there should also be some requirement that both reading and writing be supported, to ensure apps reading POI data don't lock in new data, and to prevent apps reading traffic data from freeloading.
> 1. A POI/favorites app that maintains a local database with an API for other apps to access it. Apps could then store markers there instead of in their own private db, so that points added on one map app can be instantly available in other apps.
Would an AT Protocol app or extension meet this need and requirements? By being stored in a PDS, the data can be permissioned, owned by the user, and easily migrated and/or shared.
https://atproto.com/blog/atproto-spaces-alpha
ATProto spaces: A new extension to ATProto that enables non-public data - https://news.ycombinator.com/item?id=49379732 - August 2026
Neat, I was not aware of this mechanism. Is there any way to get map (tile) data from CoMaps into another app?
There are converters between different OSM formats and other formats (Garmin comes to mind). It depends on the target. E.g. here: https://www.mapfileconverter.com/free-gis-conversion-tools