Difference between revisions of "Projects/Marble/OnlineRoutingImplementation"

Jump to: navigation, search
(Nice to have)
Line 8: Line 8:
 
* CloudMade
 
* CloudMade
  
== Marble Widget Layer (done) ==
+
== 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. Extend LayerManager to support adding layers not via plugins.
+
  
 
== Integrate with search UI (done) ==
 
== Integrate with search UI (done) ==
 
* Merge UI in MarbleControlBox: Search via runners and routing can be done from the same widget similar to how Google Maps does it
 
* 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)
+
* Default Search is pretty much the same, but has a "Add destination field" 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.
+
* 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
 
* 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
 
* Routing results are shown in the same list view as marble runner search results
Line 29: Line 28:
  
 
== Nice to have ==
 
== Nice to have ==
* Download progress indicators
+
* Progress indicator for route download
 +
* Reverse geocoding via osm nominatim
 +
* Route instruction localization
 
* Support context menu in MarbleWidget
 
* Support context menu in MarbleWidget
 
* Support routing customization: By car, by bycyle, ...
 
* Support routing customization: By car, by bycyle, ...
Line 39: Line 40:
 
== Artwork ==
 
== Artwork ==
 
Ask the oxygen guys if they can help out with some icons:
 
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-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)
+
  
 
== Shipping ==
 
== Shipping ==

Revision as of 00:04, 18 March 2010

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

Contents

Routing providers (done)

Support data download from

  • openrouteservice.org
  • yournavigation.com
  • Google Maps
  • CloudMade

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

Integrate with search UI (done)

  • 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 "Add destination field" button which adds more search widgets (each representing one position to be included in the route)
  • 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

Plugins

  • Refactor marble runners to be plugins
  • Refactor routing providers to be plugins
  • Routing providers and marble runners share a common base

Nice to have

  • Progress indicator for route download
  • Reverse geocoding via osm nominatim
  • Route instruction localization
  • Support context menu in MarbleWidget
  • Support routing customization: By car, by bycyle, ...
  • Load routes via File -> Open Map
  • Export routes to .gpx, .kml
  • Support printing routes (map with waypoint layer and instructions)
  • 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)

Shipping

  • Check which routing providers can be shipped / enabled by default
  • OpenRouteService allows non-commercial usage. Exact definition todo
  • Google Maps cannot be used at all (license terms)
  • CloudMade can possibly not be used (cumbersome pricing model)
  • YourNavigation is currently too limited (server often busy, routing data only for UK? No route instructions atm, only waypoints)

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal