In reality there were two updates, with data from July 21st and July 28th, but those newer maps required having app version 2026.07.16 - so the Google Play folks needed to wait for Google to finish the app review before being able to access them!
A huge thanks to the ~25 folks that joined us for our virtual birthday party yesterday and made it a really great event! 🥳 Covering a range of 14 time zones, it really showed how global our community is. 🌏 Over the course of around 2.5 hours, we were joined by some long-standing CoMaps contributors, active members of the #OpenStreetMap community, and many new faces!
No worries! It all is based on the same data, but then the processing can be quite different (e.g. the calculation of penalties for the routing algorithms goes into the maps during this processing), or which POI types are shown on the maps etc. Converting the raw OSM DB into something usable for mobile apps is quite a heavy processing step 🙂
There's some duplication - but it's not that easy: Map applications like CoMaps and OsmAnd make their own choices on which types of data from OSM is included in maps and how it's displayed, and also how the data structure behind the scenes work. This is necessary to create maps that load fast and work well for route calculations etc. So having them compatible between apps is extremely hard.
Vespucci in contrast is a pure OSM editor, so this just gets the 'raw' data from OSM for a given region, as it focuses on only editing/adding data to OSM, but not on end-user search, can't navigate etc.
For that reason it's unfortunately not likely that a shared format will emerge, as different OSM data users and apps have different needs!
If you have particularly strange routings, feel free to send examples somewhere. As they can be due to OSM errors too, it's always good to have a look on whether the CoMaps routing is having an issue or if the underlying data can be fixed!
There's a lot of work going on to improve public transport, but so far it's still work-in-progress: https://codeberg.org/comaps/comaps/projects/36008
In reality there were two updates, with data from July 21st and July 28th, but those newer maps required having app version 2026.07.16 - so the Google Play folks needed to wait for Google to finish the app review before being able to access them!
oh, good catch! We'll let them know!
thanks!
there is a version on redbubble that does this, i'll check that we get that on the codeberg repo too!
no problem! donations via https://opencollective.com/comaps and https://liberapay.com/CoMaps are always an option that's a lot easier for us! :)
A huge thanks to the ~25 folks that joined us for our virtual birthday party yesterday and made it a really great event! 🥳 Covering a range of 14 time zones, it really showed how global our community is. 🌏 Over the course of around 2.5 hours, we were joined by some long-standing CoMaps contributors, active members of the #OpenStreetMap community, and many new faces!
The problem is that it becomes a bureaucratic overhead compared to simple donations, as then we'd become a vendor selling stuff for profit!
And if you want to join our birthday celebration community call, it'll happen today at 19:00 UTC, more details here: https://codeberg.org/comaps/comaps/wiki/First-anniversary-celebrations
No worries! It all is based on the same data, but then the processing can be quite different (e.g. the calculation of penalties for the routing algorithms goes into the maps during this processing), or which POI types are shown on the maps etc. Converting the raw OSM DB into something usable for mobile apps is quite a heavy processing step 🙂
So far it's fully manual, but an optional automatic check might come in the future!
There's some duplication - but it's not that easy: Map applications like CoMaps and OsmAnd make their own choices on which types of data from OSM is included in maps and how it's displayed, and also how the data structure behind the scenes work. This is necessary to create maps that load fast and work well for route calculations etc. So having them compatible between apps is extremely hard.
Vespucci in contrast is a pure OSM editor, so this just gets the 'raw' data from OSM for a given region, as it focuses on only editing/adding data to OSM, but not on end-user search, can't navigate etc.
For that reason it's unfortunately not likely that a shared format will emerge, as different OSM data users and apps have different needs!
there is https://rudokemper.com/google-maps-places-to-comaps/ for converting the Google Maps takeout to the GPX!
If you have particularly strange routings, feel free to send examples somewhere. As they can be due to OSM errors too, it's always good to have a look on whether the CoMaps routing is having an issue or if the underlying data can be fixed!
join the matrix room if you haven't yet, and you'll find some other map-loving folks who'll be there!
great name idea! In German the marks you make in books are also called "donkey ears"!
yes, it's here: https://translate.codeberg.org/projects/comaps/-/pt_BR/
See https://codeberg.org/gedankenstuecke/comaps-map-distributor for an example of setting up a local server to bring it to low connection/bandwidth areas!