Our latest version, 2026.01.08, is available in all release channels!
Updates include more visual refreshes on Android (moving to Material 3) and an expanded #OpenStreetMap editor.
The OSM editor now supports a number of POI types that require multiple tags, like adding statues, Buddhist temples, coffee vending machines, etc.
See the full release notes for details!
https://codeberg.org/comaps/comaps/releases/tag/v2026.01.08-11
@CoMaps praying for fuller public transit stuffs ^_^
MOTIS, GBFS, accessibility.cloud, etc 🙏
@tobifant in principle this already works, by typing a whole address one can find it (eg this search was made when the map was centered on a small village in Argentina).
Having said that, we're aware that the search needs to get some love to work better, as depending on the amount of maps you've downloaded etc the experience can be not perfect!
@CoMaps Are any visual/UX refreshes coming to iOS as well? 👀 One of the biggest feature mismatches currently between CoMaps and Organic is the overall routing workflow, which is still very unintuitive on CoMaps (I can’t immediately change the route endpoints for example, and the various route settings aren’t in one place, like in Organic and proprietary competitors). It’s actually a place where y’all can supersede Organic, which I think is also still complex (Route to/Route from v Change Stop).
@moshimotsu cherry picking this from the upstream is unfortunately not possible as it seems commits for that are missing, see https://codeberg.org/comaps/comaps/issues/584
So unfortunately it's more work and will take more time.
@CoMaps Very reasonable, I wish you luck on finding the time and contributors to make it happen. 💪 On the plus side, maybe that gives you guys a chance to implement it in an even better way? Who knows!
@moshimotsu thanks! If you hear of any iOS (or Android) devs looking for a fun project with a bunch of welcoming other contributors that are happy to help with the onboarding, send them our way!
@CoMaps I see "Removed fictional speed limits for link roads" in the changelog. I didn't even know that was possible before.
Does that mean that before:
if one section of road was 80 km/h, the next one had no information and the one after that was 80 km/h again... Then the section between the two was also calculated as 80 km/h in the route calculation?
@JBrickelt963 similar, it inferred limits for some links, and even showed them to the user. See https://codeberg.org/comaps/comaps/issues/1000 for a much longer explanation of the problem that's now solved 🙂
@CoMaps OK, thank you for the link to the solved problem. I understand better now... In addition to being used for estimates (which is understandable), it was also displayed in some cases, and since that's not reality, it's not very good.
