Marble/OnlineRoutingImplementation: Difference between revisions

Latest revision as of 08:05, 21 October 2016

This page lists more concrete steps to integrate online routing support.

Routing providers (done)

Support data download from

openrouteservice.org
yournavigation.com
Google Maps
CloudMade
Eventually http://permalink.gmane.org/gmane.comp.gis.openstreetmap.routing/849

Marble Widget Paint Layer (done)

A custom paint layer which displays routing points: Start, destination, intermediate points. Waypoints, connected.
- Paint layer reuses the selection model of the routing instruction list view
- Source, destination and via points are movable in the map
- Instructions are shown in the mapping when clicking on the corresponding waypoint
Paint layer is included in Marble's model

Route/Search UI

Search results are shown in the list view. 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
Reverse geocoding via runner plugins
Route instruction localization
Route preferences: By car, by bycyle, ... avoid highways, avoid toll roads

Plugins (Marble Runners)

Reverse geocoding
Routing

Nice to have

D-Bus interface

Artwork

Ask the oxygen guys if they can help out with some icons:

route-instruction (Intermediate route point with turn instructions)
route-select (Action to pick route point in the map)

@@ Line 1: / Line 1: @@
-This page lists more concrete steps to integrate online routing support. Code is currently available at http://nienhueser.de/git/marble.git
+This page lists more concrete steps to integrate online routing support.
-== Step 1: Basic workflow (done) ==
+== Routing providers (done) ==
-* UI to select source and destination via map clicks
+Support data download from
-* UI to select source and destination via runners (esp. OSM namefinder)
+* openrouteservice.org
-* UI to display routing instructions
+* yournavigation.com
-* Implement a routing provider base
+* Google Maps
-* Implement routing provider for Google maps, parse resulting KML and feed to routing display
+* CloudMade
-* Implement routing provider for CloudMade, parse resulting gpx and feed to routing display
+* Eventually http://permalink.gmane.org/gmane.comp.gis.openstreetmap.routing/849
-== Step 2: Integrate with search UI ==
+== Marble Widget Paint Layer (done) ==
-* Merge UI in MarbleControlBox: Search via runners and routing can be done from the same widget similar to how Google Maps does it
+* A custom paint layer which displays routing points: Start, destination, intermediate points. Waypoints, connected.
-* 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)
+** Paint layer reuses the selection model of the routing instruction list view
-* 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.
+** Source, destination and via points are movable in the map
+** Instructions are shown in the mapping when clicking on the corresponding waypoint
+* Paint layer is included in Marble's model
+== Route/Search UI ==
+* Search results are shown in the list view. 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
+* Reverse geocoding via runner plugins
+* Route instruction localization
+* Route preferences: By car, by bycyle, ... avoid highways, avoid toll roads
-== Step 3: Marble Widget Layer ==
+== Plugins (Marble Runners) ==
-* Make a custom routing paint layer which displays routing points: Start, destination, intermediate points. Waypoints, possibly connected. Routing instructions.
+* Reverse geocoding
-* Bonus points for
+* Routing
-** 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 ==
+== Nice to have ==
-* Support routing customization: By car, by bycyle, ...
+* D-Bus interface
-== Step 6: More routing providers ==
+== Artwork ==
-* Integrate openrouteservice.org (permission to use in Marble kindly granted by them)
+Ask the oxygen guys if they can help out with some icons:
-* Integrate yournavigation.com
+* route-instruction (Intermediate route point with turn instructions)
+* route-select (Action to pick route point in the map)