#comaps — Bluesky Posts

oliverW 🌲🌳🚲🌞🇪🇺

@oliverweinrich.troet.cafe.ap.brid.gy

6 hours ago

Tour Aufzeichnung mit #coMaps #osm

0 0 0 0

OliverW🇪🇺

@hotzenwaldkurier.bsky.social

6 hours ago

Heut die Route 📍mit @comaps.app aufgezeichnet .. mich interessieren die Höhenangaben 🚵‍♀️ der Tour. 2 Vergleiche.

Kaiser-Rudolf-Platz • 920 hm / coMaps - 964 hm

Hierholzer Weiher • 900 hm / coMaps - 962 hm

#osm 📍 #coMaps #Navigation

#dachsberg #südschwarzwald

1 0 0 0

Public Enemy Exposed

@pee.mastodon.online.ap.brid.gy

14 hours ago

@CoMaps

Just wondering why there is no way to stop downloading maps on Linux.

Erroneously double-clicked the top most 'countries' and now I need to download, what 90GB maps, only to delete them again. 🤦

Or is the cancel button hidden somewhere?

0 1 0 0

Pm4linuxmint🦋📯💎I❤️🇪🇺🇩🇪🆓🇺🇦

@pm4linuxmint.eurosky.social

1 day ago

CoMaps A community-led fork of Organic Maps. Reinforced with commitment to transparency, privacy and being not-for-profit.

Guten Morgen!
Mein Tipp:
Navi offline

#CoMaps
Ein von der Gemeinschaft geführter Fork von Organic Maps. Verstärkt mit Engagement für Transparenz, Privatsphäre und Gemeinnützigkeit.

f-droid.org/packages/app...

codeberg.org/comaps

1 0 0 0

UnitedWeStand🇪🇺🌻🫂

@johkra.mastodon.social.ap.brid.gy

1 week ago

@babble_endanger
at least #osmand and #comaps can handle OLC (aka plus-code)

0 0 0 0

GedankenPingPong

@gedankenping.mastodon.de.ap.brid.gy

1 month ago

Wandern, Radfahren, Autofahren – Offline navigieren mit Datenschutz Entdecke mehr von deiner Reise - Entwickelt von der Community

Ab heute #GoogleMaps durch @CoMaps (https://www.comaps.app/de/ ersetzt.

Jeden Sonntag eine gute Tat und wieder etwas #DUTgemacht.

#CoMaps #DIDit #diday

0 0 0 0

🇩🇰 Klaus Alexander Seiﬆrup 🇬🇱

@takis.eurosky.social

1 month ago

Hike, Bike, Drive Offline – Navigate with Privacy Discover more of your journey - Powered by the community

Ubetinget #CoMaps:

📍 www.comaps.app

CoMaps er en fork af OrganicMaps, som følge af en del drama omkring sidstnævnte:

🔗 openletter.earth/open-letter-... (lang læsning)

2 0 1 0

Ernst Schreier

@schreier.bsky.social

1 month ago

deGoogle
#G-Chrome ➡️ #Firefox + #Brave ✅
#G-Drive ➡️ #Nextcloud ✅
#G-Mail ➡️ #mailbox ✅
#G-Maps ➡️ #MapsMe ✅
#Google ➡️ #Startpage ✅

Seit Trump:
#Facebook ➡️ 🚫
#Instagram ➡️ 🚫
#Twitter/X ➡️ #Bluesky, #Fediverse ✅

und heute:
#MapsMe ➡️ #CoMaps (OSM) ✅
Anmeldung bei #Wero ✅

2 0 0 0

@linuxeasy.bsky.social

1 month ago

CoMaps, la navigazione offline che mette privacy e community al primo posto CoMaps è l’app di navigazione gratuita, offline e rispettosa della privacy basata su OpenStreetMap, ideale per escursioni, viaggi all’estero e percorsi senza connessione.

CoMaps è l’app di navigazione gratuita, offline e rispettosa della privacy basata su OpenStreetMap, ideale per escursioni, viaggi all’estero e percorsi senza connessione. #CoMaps #Software #Linux #Flatpak

0 0 0 0

⛏️ 𝔸𝕤𝕥𝕣𝕚𝕕 ℍ𝕚𝕝𝕥 🔨

@steinmetzin.gruene.social.ap.brid.gy

1 month ago

Original post on gruene.social

Hier ist die Liste meiner Apps von #froid, die ich auf meinem #fairphone nutze:

seit mindestens einem Jahr:
#nectcloud - mit #talk #Deck #Notes und seit zwei Monaten auch #memories und #News
In der Warteschleife/Einrichtung: #Passkey und #Geobookmarks

#openstreetmap #comaps #opencamera […]

0 0 0 0

Robert Lender

@roblen.microblog.at.ap.brid.gy

2 months ago

CoMaps in 2026: Planning for the future What we aim to achieve in 2026

www.comaps.app/news/2026-01-09/comaps-i...

Gedanken von @CoMaps zur Weiterentwicklung von #CoMaps.

Mitentwickler:innen werden auch gesucht.

0 1 0 0

The New Oil

@thenewoil.org

2 months ago

Google Maps alternative:Best open source maps in 2026 Visiting a bustling unknown city or finding a hidden restaurant has never been easier with the rise of Google Maps. But, this ease of navigation has not come without a price, that being the erosion of our privacy. Luckily today there are great alternatives to Google Maps that better respect your privacy.

#GoogleMaps alternative: Best #OpenSource #maps in 2026

https://tuta.com/blog/google-maps-alternatives-foss

#Google #privacy #naviagtation #FOSS #OsmAnd #OrganicMaps #CoMaps

0 1 0 0

Jan Penfrat

@ilumium.eupolicy.social.ap.brid.gy

2 months ago

Screenshot from CoMaps' download screen for more maps, showing an entry that reads "Paris London Canada" (probably there's a town called Paris that sits in a Canadian county called London or something?)

This feels just wrong. 🫣😄

#CoMaps #OSM #Paris #London #Canada

1 1 0 0

Subhan Gadirli

@subhanqedirli.mastodon.social.ap.brid.gy

2 months ago

RE: https://mas.to/@alternativeto/115843911655908798

I really love and use @CoMaps daily. And it feels really good to contribute that kind of projects 💚 (especially less well-mapped countries like Azerbaijan)

#OSM #openstreetmap #CoMaps #opensource

1 1 0 0

Home

@tzovar.as.web.brid.gy

2 months ago

Serving maps locally with CoMaps **tl;dr: You can now serve map files for _CoMaps_ from your own servers, including local ones. I made a small and simple command-line tool to help you download the maps to your computer and serve them in a local network.** _CoMaps_ is a mobile app for Android & iOS that provides offline maps and turn-by-turn navigation – based on data from _OpenStreetMap_ data – that forked from the _Organic Maps_ project in the first half of 2025. Being able to fully use the maps offline makes it ideal for hiking and traveling to places where internet connectivity is spotty at best. Plus, it allows for editing OSM offline too. But, while using the maps works offline, until recently you basically needed to have an internet connection to get maps on your phone/into the app. Since mid-December, this is not fully necessary any longer.1 While _CoMaps_ still expects to be fed the “official” maps (i.e. maps where the app recognized the checksums), you can now change where those maps come from. By default, _CoMaps_ still uses the _content delivery network_ (CDN) that is hosted by the _CoMaps_ team. This consists of a set of servers in different places, and a meta server picks the _“best”_ connection based on geolocating the user’s IP. Then one of those remote servers will be used to download the map data. And, for the most common use cases and users (having access to stable internet in regular intervals, updating maps only on a single device, …), this works perfectly fine. But removing the previous hard-coded CDN means less reliance on a fixed set of remote servers, and flexibility for other use cases. A big one use case for using a different server is **installing and updating maps in places with limited or no internet connectivity**. For example, if you have a household where you need to update the map data in more than one device and aren’t exactly having a broadband connection. In that case, downloading the same maps multiple times from remote servers, through a slow connection, is quite wasteful of your bandwidth – even more so if you are on a metered connection where you pay for traffic.2 An extended version of that _limited connectivity use case_ are _redes comunitarias_ (community networks), where families living in rural areas are connected to the internet via local networks that link up to the internet at certain points, and where saving communally shared bandwidth is similarly important. And another use case could be the deployment of maps in humanitarian settings, in places disconnected from the internet, but where having local maps is highly beneficial: By bringing along the _APK_ and local map files, a single laptop could be used to rapidly deploy _CoMaps_ and the needed maps on existing Android devices. The **other use case that comes to mind is long-term archival of maps**. Until now, older maps of _CoMaps_3 would at some point not be able to download maps any longer, as storing all historic maps on the _CoMaps_ CDN would be prohibitive due to the file size. As a result, while one could have archived those map files themselves, those couldn’t easily be used in the older apps, as getting them onto the devices wasn’t easy. And this goes beyond just “data backups”, historic maps and how people interacted with them is of historic/scientific interest too, so having pathways to ensure that these maps remain accessible and useable is great. Now, it’s a lot easier to just backup the old APK files alongside the maps and get them installed again. Of course, being able to host your own maps introduces another problem: How do people download and serve them? Traversing the paths of the _CoMaps_ CDN to get the maps isn’t necessarily easy. And standing up your own local web server to deliver the files isn’t either. Which is why I spent some time over the holidays to make a small python library that focuses on making the download and serving of those _CoMaps_ map files as easy as possible. At the heart of the `comaps-map-distributor` are three sub-commands, for downloading maps, updating local maps, and serving the maps. Using the defaults should work in settings, requiring little/no setup. And for selecting/downloading the maps, a basic, interactive interface runs people through the selection. Overall, installing, downloading and serving the maps should be as simple as using these three commands: pip install comaps-map-distributor comaps-map-distributor download-maps comaps-map-distributor serve-maps The serve command will show the IPs that people can use in the CoMaps app to use as the remote server. The header image shows two screenshots, and you can also see a small demo video on _Codeberg_. When it’s time to update to newer maps (and you’re in a place with internet), one can run `comaps-map-distributor update-maps`, and it will update the local maps that were downloaded in the last version. Under the hood, this little app is using `inquirerpy` and `rich` for the interface and visuals - both a first for me.4 If you’d like to help contribute/improve it, you can find all you need on Codeberg Happy map-using! ## References 1. Greshake Tzovaras, B. (2025, November 21). Mapping offline with CoMaps and Every Door. Bastian Greshake Tzovaras. https://doi.org/10.59350/8vcqj-tqe05 ## Footnotes 1. So far, this only is the case for the Android version of the app. ↩ 2. Incidentally, this is partially my personal use case. While not on a metered connection, our home internet is rather slow, and while we don’t have a large fleet of Android devices it’s still nice to avoid duplicate downloads. ↩ 3. All these limitations that come with a fixed, hard-coded map delivery network also apply to _Organic Maps_ as it is today. ↩ 4. Since then I made another little tool for sorting GoPro images for Panoramax ↩

0 0 0 0

⛏️ 𝔸𝕤𝕥𝕣𝕚𝕕 ℍ𝕚𝕝𝕥 🔨

@steinmetzin.gruene.social.ap.brid.gy

2 months ago

Nächster Schritt in die Daten-Souveränität:
#CoMaps einrichten und die Karten hier aus der Gegend, also #Saarland #Koblenz #Westpfalz, downloaden.
Ich bin gespannt, was sich noch so alles zeigt.

#Astroet

0 0 0 0

Totty Johnson

@6060764.bsky.social

3 months ago

Organic Maps Forked Over Governance Concerns: CoMaps is Born An Organic Maps fork has emerged due to broken trust.

itsfoss.com/news/organic... #OrganicMaps #CoMaps

0 0 0 0

Karmalakas

@karmalakas.mastodon.social.ap.brid.gy

3 months ago

Ar ne @mcSlibinas skundėsi, kad kažkurioj navigacijoj nėra lietuviško balso instrukcijų? Tai va @organicmaps jau paleido, vadinasi ir @CoMaps turėtų greitai atsirast 🤞

#OrganicMaps #CoMaps

0 0 0 0

Home

@tzovar.as.web.brid.gy

3 months ago

Mapping offline with CoMaps and Every Door For the first half of November, I’ve been in Peru to do some hikes close to Cusco with friends: First, we did a 5 day trek to the Inca site of Choquequirao and back. After a day and a half of rest back in Cusco, we then did the 4-day Inca trail to Machu Picchu as well. Of course, I wanted to use those opportunities to do some surveying and mapping for _OpenStreetMap_ (OSM) along the way as well. But there are (at least) two potential issues when doing so during multi-day hikes into at least somewhat remote areas: Having internet connectivity & managing phone battery levels. To give some context about the locations in question: Similar to Machu Picchu, Choquequirao is tucked away on the side of a mountain, surrounded by forests. But unlike its sister site, there is no way to reach that doesn’t involve hiking 25 km as first descending and then climbing 1,600 meters (That is one way, you then do the same in reverse to get back). Given this geography, there’s very little to no internet connectivity along the way, which makes live-mapping very hard. And while the Inca trail is more touristy, even along it there’s ~2 days where there’s no connectivity. Furthermore, most of the campgrounds one encounters have limited if any electricity to recharge batteries as well. To nevertheless be able to survey and contribute, I used a mix of strategies: Firstly, as I was recording the actual hiking paths with my Garmin _Fenix_ watch, I got GPX tracks of our routes somewhat as a side effect. On a full charge, and with a bit of integrated solar charging, it can record GPS tracks for ~24 hours. And similarly, by just taking holiday snapshots (as well as some more mindful surveying pictures) along the route using my phone, I created some geolocated reference images too. That left the question of how to more directly contribute to OSM, for which I settled for a combination of _CoMaps_ and _Every Door_. _CoMaps_ 1 is mainly a map & navigation app that is based on OSM and is available for iOS & Android. It works with maps that are fully offline after the initial download. This in itself was already super useful: While we had guides for our treks, it was super useful to be able to quickly pull out a map to check what a given mountain peak we were seeing was - and even read the associated offline Wikipedia article. Or being able to check the current or remaining elevation. Beyond looking at OSM data, _CoMaps_ also has a (simple) OSM editor, that allows adding & editing points of interest (POI), as well as leaving notes on OSM. And as _CoMaps_ is an _offline-first_ app, it works well offline too: It will queue your edits & notes and keep them safe until you’re back online, at which point the data is sent over to OSM. While this approach works well for many common POI, _CoMaps_ is by design limited to more common objects, to keep things simple. To be a bit more flexible, I also wanted to use _Every Door_ , which is a more powerful OSM editor designed specifically for surveying. Until recently, it didn’t work super well for pure offline-use, as the background map/satellite layers would not easily cache predictably. Luckily, _Every Door 7.x_ was released in September and has changed this2! This version has two changes that make fully working offline very easily possible: Firstly, one can now optionally work with vector tiles instead of just the previous raster tiles, thanks to the new plugin architecture. The vector tiles are significantly smaller, so it’s more feasible to have them available offline on a phone for larger regions – which comes at the cost of slower map-rendering speeds. Secondly, the 7.x version of _Every Door_ also allows managing its offline-available data. One can now select areas for which both the OSM data itself and the raster/vector tiles (or even satellite images) should be stored offline. Once downloaded, the background layer and OSM data are persistently stored, allowing browsing the corresponding regions in _Every Door_ without any connectivity. Unlike _CoMaps_ , _Every Door_ does not automatically push changes back to OSM, instead it requires actively pressing the _Upload_ -button. This is nice for prolonged offline-use, as one can then submit one larger changeset, which one can even annotate with hashtags. Now that we have ways to collect and edit data offline on the trail, **what about battery life** : Given the assumption that there’s no connectivity during the trek, the biggest battery saving comes from enabling airplane mode to disable the mobile radios. Otherwise the radios would continuously try to find and connect to cell towers, sucking up the battery. Using the phone otherwise for taking pictures and mapping with _CoMaps_ & _Every Door_ , that alone helped bring down the battery use to around ~30-35% of battery capacity in a hiking day. To further minimize battery use, I just switched off my phone in the evening, only turning it back on the next morning. Both _CoMaps_ and _Every Door_ handle a cold restart perfectly fine without losing the already downloaded/queued data. With that, my phone could easily last 2 days, maybe even a bit more. I carried a power bank to top up my phone every two days, as well as recharging my _Garmin_ watch to continue my GPS recordings too. I didn’t have any _battery anxiety_ with this approach, leaving my (20,000 mAh) power bank more than half-full after the 5 days of hiking. Overall, this was my first time trying to do some surveying while hiking in (somewhat) off-the-grid locations that are mostly without internet connectivity and electricity. And I wasn’t sure how well it would work, but it turns out **_CoMaps_ and _Every Door_ handled contributing in that way really well**: Once we came back to a place with stable WiFi, I uploaded all edits via both apps without any issues. And when I arrived back home, I used the GPS Tracks to adjust some paths that I had noticed as being slightly wrong along the way and uploaded some images to Panoramax and Wikimedia Commons. I will definitely continue using this approach for contributing to OSM on my next hikes, and if you plan to go out into nature you can give it a try too, just download the relevant map regions in advance and you’re good to go. Happy hiking! ## References 1. Greshake Tzovaras, B. (2025, May 9). Updates to the ‘Personal API’. Bastian Greshake Tzovaras. https://doi.org/10.59350/8fxh9-3vd91 2. Greshake Tzovaras, B. (2024, August 23). Openly licensed streetview with Panoramax. Bastian Greshake Tzovaras. https://doi.org/10.59350/cjnzq-6cs79 ## Footnotes 1. Since _CoMaps_ has forked from _Organic Maps_ , I’ve been trying to contribute and help out a bit where I can, as it’s one of my favorite OSM-based map tools. ↩ 2. _Every Door_ is generally one of my favorite surveying tools for OSM, I recently was involved in making a small _getting started_ -guide in Spanish for it. ↩

0 0 0 0

JesseBot

@jessebot.social.smallhack.org.ap.brid.gy

4 months ago

Is there a way to download a transit layer for Amsterdam for comaps?

#comaps #osm #openstreetmaps #organicmaps

0 1 0 0

CoMaps

@comaps.app

4 months ago

Photo of a freeway/arterial interchange from above. Below text "Improving routing data".

To calculate the "best" routes and more accurate arrival time estimates, #CoMaps assigns so-called penalties to road features like traffic lights.

For this to work, data needs to be available and correct in #OpenStreetMap. Check out how you can tag errors in data.

www.comaps.app/news/2025-10...

8 1 0 0

Hamilcar 🚲

@hamilcar117.mastodon.social.ap.brid.gy

4 months ago

Original post on mastodon.social

Aujourd’hui, les cartes visibles sur CoMaps datent du 5/9. Celles d’Organic Maps datent du 5/10. Pas trouvé pour OSMand mais je doute qu’elles datent d’aujourd’hui ou d’hier. Mais il y a le site Veggiekarte) (que je recommande) qui actualise bien son snapshot toutes les heures

Bref, j’ai omis […]

0 0 1 0

CoMaps

@comaps.app

6 months ago

Logos of each of the projects mentioned and below “Foundation projects leading to CoMaps”

Big thanks to the amazing projects that make CoMaps possible!

@openstreetmap.bsky.social

@organicmaps.bsky.social and MAPS.ME

@wikipedia.org

NASA's SRTM and Sonny's Lidar DTMs

JOSM, EveryDoor @streetcomplete.bsky.social plus more

#OpenSource #Mapping #CoMaps #OSM #CommunityPowered

23 3 1 0

CoMaps

@comaps.app

6 months ago

Photo of phone being held, a person at a laptop and compass being held. Below “News Page”

“Why I Use CoMaps to ...”

“The diversity of OpenStreetMap tools and ...”

Dive into real‑world stories:
www.comaps.app/category/blog/

Have a CoMaps‑related blog post or thinking of writing a piece? We’d love to showcase your voice!

Get started:
codeberg.org/comaps/websi...

#CoMaps #ShareYourBlog

6 1 0 0

Jakob Miksch

@jakobmiksch.mastodon.social.ap.brid.gy

6 months ago

OSMAnd vs. Organic Maps Comments

comparison #organicMaps #osmand
#openstreetmap #osm #CoMaps

blog.firedrake.org/archive/2025/09/OSMAnd_v...

1 0 0 0

djpanini

@djpanini.mastodon.uno.ap.brid.gy

6 months ago

Oggi ho finalmente usato #comaps per andare in un luogo dove non ero mai stato.
Ha funzionato alla grande!
Bravi @CoMaps !

0 0 0 0

uridl

@uridl.mastodon.social.ap.brid.gy

6 months ago

When downloading offline maps, does it save bandwidth to offer diffs between the versions, so people can update their maps and not redownload them?

#osm #openstreetmap #osmand #comaps @CoMaps

0 0 0 0

Damian Antonowicz

@damianantonowicz.pl

6 months ago

I’ve started using #CoMaps recently and from initial usage seems like good replacement for Google Maps

0 0 0 0

quaff

@quaff.thecanadian.social.ap.brid.gy

6 months ago

Original post on thecanadian.social

I am having one of those moments where I feel tech illiterate while using #OpenStreetMaps and #CoMaps.

How do I search for an address? No matter what OSM client/interface I use, when I search addresses in my city (maybe it's just #Vancouver ?), the results returned is of Primary Roads crossings […]

0 0 0 0