Marble/OnlineRoutingImplementation

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This page lists more concrete steps to integrate online routing support. Code is currently available at http://nienhueser.de/git/marble.git

Step 1: Basic workflow (done)

UI to select source and destination via map clicks
UI to select source and destination via runners (esp. OSM namefinder)
UI to display routing instructions
Implement a routing provider base
Implement routing provider for Google maps, parse resulting KML and feed to routing display
Implement routing provider for CloudMade, parse resulting gpx and feed to routing display

Step 2: Integrate with search UI

Merge UI in MarbleControlBox: Search via runners and routing can be done from the same widget similar to how Google Maps does it
Default Search is pretty much the same, but has a "Routing mode" button which adds a second search widget (likely more to support intermediate targets)
Search results are shown in the list view as before. The selected search result is kept track of and taken as the source/destination point.
Once all routing points are known (user selected a search result or clicked on the map for both routing source and destination and intermediate points, if any), the "Get Directions" button can be used to fetch routing instructions from the current routing provider
Routing results are shown in the same list view as marble runner search results

Step 3: Marble Widget Layer

Make a custom routing paint layer which displays routing points: Start, destination, intermediate points. Waypoints, possibly connected. Routing instructions.
Bonus points for
- Making the paint layer a QAbstractItemView working on the same model as the routing instructions list view and sharing the selection model with it
- Make source/destination points movable directly in the map
- Provide tooltips / unfolding for routing instructions
Integrate the paint layer with MarbleWidget/MarbleMap. Eventually extend LayerManager to support adding layers not via plugins.

Step 4: Plugins

Refactor marble runners to be plugins
Refactor routing providers to be plugins
Does it make sense to generalize runners as a common base for both coordinate searchs (current runners) and routing providers?

Step 5: Configuration

Support routing customization: By car, by bycyle, ...

Step 6: More routing providers

Integrate openrouteservice.org (permission to use in Marble kindly granted by them)
Integrate yournavigation.com