Marble/RoutingRoadmap

From KDE TechBase
Revision as of 14:32, 22 August 2010 by Earthwings (talk | contribs)

KDE 4.5 (Marble 0.10)

  • Online-Routing using OpenRouteService
  • GPX export

GSOC 2010 (KDE 4.6?)

  • Offline support (data pre-fetching)
  • Routing mode (follow GPS position, display instructions)
  • UI improvements for small devices (Maemo, Nokia N900)

KDE 4.6 (Marble 0.11)

GPX/KML Import

Status Project Description Contact
TO DO Marble Check parsing of route related gpx and kml elements Dennis Nienhüser <[email protected]>
TO DO Marble Connect to FileManager and import routes, if any Dennis Nienhüser <[email protected]>

Route Printing

Status Project Description Contact
TO DO Marble Extend current print dialog with Marble option page for configuration Dennis Nienhüser <[email protected]>
TO DO Marble Optional inclusion of legend and routing instructions Dennis Nienhüser <[email protected]>

Route state save

Status Project Description Contact
TO DO Marble Check KML export of route elements Dennis Nienhüser <[email protected]>
TO DO Marble Auto-save route to kml file at appropriate times Dennis Nienhüser <[email protected]>
TO DO Marble Auto-load kml route at startup, if any Dennis Nienhüser <[email protected]>

Worldwide and Offline Routing

Status Project Description Contact
IN PROGRESS Marble Include gosmore-instructions in Marble Dennis Nienhüser <[email protected]>
IN PROGRESS Marble Also parse routino output Dennis Nienhüser <[email protected]>

Routing API

Status Project Description Contact
TO DO Marble Rename RouteSkeleton to RouteRequest Dennis Nienhüser <[email protected]>
TO DO Marble Routing API review Dennis Nienhüser <[email protected]>
TO DO Marble Decouple RoutingWidget, RoutingLayer and RoutingManager Dennis Nienhüser <[email protected]>
TO DO Marble Export RoutingManager and RouteRequest headers Dennis Nienhüser <[email protected]>

Turn-by-turn Navigation

Status Project Description Contact
TO DO Marble Recentering when needed could use a future (predicted) position for recentering. The prediction can be based either on the current speed and direction or on the expected route waypoint at a future point (e.g. in 20 seconds) [mailto: <>]
TO DO Marble Swap z-order of current position indicator and route waypoints [mailto: <>]
TO DO Marble Make current position indicator better visible (e.g. include half-transparent indicating position dop) [mailto: <>]
TO DO Marble Selection of autzoom/recenter mode should be possible whenever a position provider is selected, not only when a position is known. Otherwise the user has to wait for the GPS signal to come in, which can take long [mailto: <>]

General Polishing

Status Project Description Contact
TO DO Marble Reset stored position in via point input widgets when user starts editing it Dennis Nienhüser <[email protected]>
TO DO Marble Use geodatacoordinates string as via input widget text only when reverse geocoding fails Dennis Nienhüser <[email protected]>
TO DO Marble Custom, i18ned display of (nominatim) reverse geocoding results also respecting the altitude (zoom) Dennis Nienhüser <[email protected]>
TO DO Marble Minimize the total number of MarbleRunnerManager instances Dennis Nienhüser <[email protected]>


Undecided

  • Tour height profiles (using SRTM data)
  • Multiple routes (one active route)