We'd love to have your input for improved transit in CoMaps! I agree it's an important priority. Last GSoC there was a project for ingesting GTFS feeds against OSM data, since local agencies are often much better about their details than OSM is, but as a student project it was slow and limited in scope.

Un(?)fortunately, us Organic Maps forkers have been with the project since Organic Maps was OMaps, and before. The only people with more commits than the senior fork member are the OM co-owners themselves. We really tried getting OM to deliver on their promises, but it seems silence is preferable to accountability for them.

Yeah it's unfortunate. Allegedly Roman wrote those goals but the other co-founders never really went along with them.

There's a lot of discussion about bicycle routing improvements, as well as displaying alternate routes. I expect these conversations to be continued in CoMaps, so your input is valued and welcome there! https://github.com/organicmaps/organicmaps/issues/9748

I agree, the issue is that the map data is highly customized. I believe StreetComplete uses online map tiles so that's less of a concern, but i.e. with Organic Maps the map data is highly tied to the app version: support for a data entry needs both app/rendering/logic support and presence in the data structure, and full forwards/backwards compatibility isn't always possible. The map files also need to be optimized for Organic Maps' speed/usability improvements over apps like OsmAnd: pre-indexing, etc. Maybe someday there's one standard format for it, but for now each app makes its own map files.

Also, mobile apps often have strict privacy lately around what files they can access: they're not just sitting on the filesystem, they're in access-controlled app-specific folders. That's good for privacy/security, but a dealbreaker for first-class sharing of information between apps.

Keep a list of those missing tags, it's worth filing an issue for adding support in the future!

Originally Alexander said that it was just too hard to register a nonprofit. I think the real answer is that he always intended to use it as an investment and sell it off (open source, but basically selling the userbase, just like Maps.ME.) Hopefully we can prove all that wrong and get a not-for-profit organization assembled and sustainable!

Nope, I'm only angry if I go telling all my friends that some app is the future of freedom and privacy, and printing flyers and driving them around town, and then that app turns and sells out their values to crypto scammers. I need reasonable assurance that my family can keep using an app I'm working on indefinitely without waking up one day to an auto-update that asks them to buy Bitcoin or something.

The "updates" link is for news and the "download" page has buttons that are inactive, are you seeing anything "Organic" remaining on the site? We've been trying to clean things up but may have missed something.

Also with mobile apps, app store users are the most "valuable" thing -- much like Maps.Me, the "app" could be sold tomorrow and what really happens is the FOSS code is thrown away or sunsetted and the users wake up to an update where their map app is now a crypto scam, or whatever. The source code can be forked, but Organic Maps "owns" millions of app store users, and can "sell" that, in a way that violates users' trust. Us volunteer developers are very against that, but unable to stop it besides protesting.

Happened with Firefox. Mozilla now has unlimited rights to use and publish, anything you see, type or upload in Firefox. And it is still marketed as "privacy" friendly. Even Micro$ft has better license in their browser!