Live data from Hacker News

CoMaps integration with the wider FLOSS ecosystem

comaps.app

41–43 of 43 posts

Re: CoMaps integration with the wider FLOSS ecosystem

#41

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 ad…

I would also like to see manageable amounts of update traffic. In the old days I had De Lorme street maps of the whole US. It was sold on a CD-ROM so the whole dataset was at most 700MB. It didn't have updates. I also have paper maps (Thomas Guide) of my local region in my car, from the 1990s, and they're still perfectly good in most places. Roads don't move around THAT often. But I have Organic Maps (predecessor of…

Well, California is 423'970 km². And Germany is 357' 684 km². I only use OsmAnd, not CoMaps. So almost the same size. The street card of Germany is 2848 MB, so even larger than the number you gave.

We also have cards for the places we live, e.g. I have the "full" map (not just streets) of Hessen, one of the 16 federal states. And that is only 485 MB. If that would be too much for me, I could also only download the governmental areas of Darmstadt, Gießen or Kassel (roughtly southern Hessen, middle Hessen, northern Hessen). But that is, in the OsmAnd case, also the case for California. You can download all of it, or or several of 16 parts.

Also: you can't compare OpenStreetMap with the detail of this old CD-ROM or printed maps. It contains WAY more data. Are you old enough to know the times where you bought a city plan if you visited some city? Well, this OsmAnd/CoMaps data set has a very details city map of all cities. And of all villages. And of about any dwelling. In OsmAnd, you cans search for almost everything, even esoteric things. Example: if you search for "Kneipp treading pool" you find them. And usually they are nice picknick areas, too. Try that with a printed map.

I personally experience you "EVERY MONTH" issue. My map of "Hessen" was last downloaded half a year ago --- I do this manually, and only every so often. OsmAnd allows that.

And if I would experience it ... I'd rather care. We have high speed DSL and glass fiber with 1000 MB/s in Germany, so 2 MB is almost nothing these days.

Still I would not recommend OsmAnd to everyone, e.g. not to "Aunt Mary". It has a clunkier, more techy UI. It isn't for everyone.

Re: CoMaps integration with the wider FLOSS ecosystem

#42

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 ad…

Waze got hugely popular by gaming their maps; people would install it just to get a high score. I wish the FLOSS mapping ecosystem would do similar.

StreetComplete has a but of gamification. Only internal, for you. But still.

It works by giving you points and achievements. And as you progress, the achievement give you popups with links to interesing OSM-data-using size. Or to add one more category to the things you can complete.

Re: CoMaps integration with the wider FLOSS ecosystem

#43

Earlier quoted context omitted.

> 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…

No, it should be local-first. Private and offline by default. There could certainly be sync integrations using AT, Dropbox, iCloud, etc. Those could even be separate apps, using the same API to access the data. But that sort of thing should be secondary and optional.

OsmAnd already can store an unlimited amount of POIs locally. With text, icon, color, coordinates of corse.
Post reply on HN