Organic maps: Experimental feed based public transport mapping
github.com
github.com
I'm currently integrating Motis on a similar initiative (a french open source Web map, https://cartes.app). More is needed to provide a full transit map experience, but Motis does the essential part.
We're not far from transit calculation as an open source commodity in countries that publish their transit data as GTFS. E.g. in France there is a whole team called transport.data.gouv.fr that deploys a website + API and do the necessary to convince and help local transport agencies to respect the law.
Ingesting this whole dataset is not trivial, lots of bugs arise (e.g. Flixbus's agency id : 0 or conflicting calendar_dates.txt ids between different datasets) but a barebone version goes live in 4 seconds (per big agency) of parsing by Motis's Nigiri module.
The developer of Motis is quite involved, and came to Organic Maps's discussion here https://github.com/organicmaps/organicmaps/issues/5331#issue...
Then comes the hardest part IMHO : the UI. Motis provides intermodal routing with the choice of walk / reduced mobility / bicycle / car / car + parking before and after the bus, and all this needs to be integrated in a UI that can rival Google / Apple Maps / Transitapp.com / etc
Organic Maps have very beautiful transit lines representation in the style of Transit app's great work. https://blog.transitapp.com/how-we-built-the-worlds-pretties...
Would be cool if some demo of the extended transit lines could be provided by Organic Maps following this readme file.
I've just opened up Chicago in Organic Maps and it isn't anything like Transit app: https://u.ale.sh/omaps-chicago-loop.jpg
It works great for simpler transit systems, but certainly there’s some room for improvement!
Solving these problems would make the map not just prettier, but also easier to read and understand. Of course, doing this by hand isn't really feasible on Organic’s / OSM’s scale, but the blog post you linked is pretty much a how-to guide that can be implemented in code. I’d love to work on something like that, but don’t really know where to start.
The referred document concerns the existing static part, it's a rather cumbersome to build it yourself at the moment. There is some routing logic in the app - I think from the Maps.me time - but currently disabled. The idea is to redesign this - in the mentioned ticket - and divide it in static (e.g. stops, routes) and 'live' data (e.g. schedule changes). It requires an efficient infrastructure. It's all volunteer driven. If you want to help, feel free to contribute!
I was wondering if a torrent-based architecture, where clients share updates with each other would help reduce the load. Any idea if it's been considered or would it just overcomplicate it for the number of clients involved and/or the latency for updates be too much to be of use?
Cartes.app is quite like an Organic Maps for the Web. So I don't have any of the offline limitations that you have, but feel free to explore the code if anything looks interesting. The development is in french but the code is mostly in english.
For me the winning feature is the UX around dropping a pin and routing to it via trails just works and is very easy, and includes elevation gain etc. Too many hiking apps require you to navigate along fixed trails in their hike database.
1. Much traffic data is private / requires licensing, however some countries have reasonable public data. For example the TraffXML (https://gitlab.com/traffxml) project has some.
2. The project is free to use, but also volunteer driven. It requires setting up a privacy preserving "live data" infrastructure.
If you think this is a nice challenge and you can help, feel free to reach out!
https://github.com/organicmaps/organicmaps/issues/1160 would be a good starting point.
In the US at least, trains sometimes block crossings for upwards of 10 minutes, and it can be very worthwhile to drive around. Doubly so if you could know en-route and seamlessly reroute, rather than having to approach the crossing to discover the closure.
OSM has a lot of data that's only available in everything-maps like OsmAnd, such as location of bicycle parking spaces or quality of cycle lanes. It would be nice to have it in a nicer interface than that app.
I'm currently building a bike + public transit directions engine (bringing your bike on the train). I'm surprised that this doesn't exist yet; it's my favourite way to get around!
I agree though that something like this is missing in the offline-first maps space.
Care to share a link ? What does it provide compared to Motis's multimodal capabilities ?
Having only subway options (and not all of them) in the cities I've been traveling is was a good start, but just adding buses would be a tremendous increase in quality of life... no more going through all the buggy and slow local transit websites.
(Why do local transit authorities think it makes sense to front-load several MB of media files on the homepage of their route-finding website, and load the "itinerary" component last? This is beyond me)