Marble/OnlineRoutingImplementation: Difference between revisions

← Older edit

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 sample routing providers
+* CloudMade
+* Eventually http://permalink.gmane.org/gmane.comp.gis.openstreetmap.routing/849
-== Step 2: Marble Widget Layer (in progress) ==
+== Marble Widget Paint Layer (done) ==
-* Make a custom routing paint layer which displays routing points: Start, destination, intermediate points. Waypoints, possibly connected. Routing instructions.
+* A custom paint layer which displays routing points: Start, destination, intermediate points. Waypoints, connected.
-* Bonus points for
+** Paint layer reuses the selection model of the routing instruction list view
-** Making the paint layer a QAbstractItemView working on the same model as the routing instructions list view and sharing the selection model with it
+** Source, destination and via points are movable in the map
-** Make source/destination points movable directly in the map
+** Instructions are shown in the mapping when clicking on the corresponding waypoint
-** Provide tooltips / unfolding for routing instructions
+* Paint layer is included in Marble's model
-* Integrate the paint layer with MarbleWidget/MarbleMap. Eventually extend LayerManager to support adding layers not via plugins.
-== Step 3: More routing providers (in progress) ==
+== Route/Search UI ==
-* Integrate openrouteservice.org (permission to use in Marble kindly granted by them)
+* Search results are shown in the list view. The selected search result is kept track of and taken as the source/destination point.
-* Integrate yournavigation.com
-* Implement scoring, auto-choose the best provider/result
-* Google Maps can not be integrated due to its terms of service
-* Check terms of service for cloudmade
-== Step 4: Integrate with search UI (in progress) ==
-* 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 "More" button which adds more search widgets (each representing one position to be included in the route)
-* 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
+* Reverse geocoding via runner plugins
+* Route instruction localization
+* Route preferences: By car, by bycyle, ... avoid highways, avoid toll roads
-== Step 5: Plugins ==
+== Plugins (Marble Runners) ==
-* Refactor marble runners to be plugins
+* Reverse geocoding
-* Refactor routing providers to be plugins
+* Routing
-* Routing providers and marble runners share a common base
-== Step 6: Configuration ==
+== Nice to have ==
-* Support routing customization: By car, by bycyle, ...
+* D-Bus interface
-== Step 7: Icons ==
+== Artwork ==
 Ask the oxygen guys if they can help out with some icons:
-* route-start (Starting point for routing)
-* route-destination (Destination point for routing)
-* route-alternative (Ambiguous source/destination search string: User needs to pick one of several alternative points)
 * route-instruction (Intermediate route point with turn instructions)
-* route-select-start (Action to pick route start in the map. Might be equal to route-start)
+* route-select (Action to pick route point in the map)
-* route-select-destination (Action to pick route destination in the map. Might be equal to route-destination)