Difference between revisions of "Marble/RoutingRoadmap"

(Created page with '== 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 posi...')
 
Line 9: Line 9:
  
 
== KDE 4.6 (Marble 0.11) ==
 
== KDE 4.6 (Marble 0.11) ==
−
* Route printing (map and instructions, configurable)
+
 
−
* GPX import
+
=== GPX/KML Import ===
−
* Automatic state saving (route and preferences)
+
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureTodo|Marble|Check parsing of route related gpx and kml elements|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Connect to FileManager and import routes, if any|[email protected]|Dennis Nienhüser}}
 +
|}
 +
 
 +
=== Route Printing ===
 +
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureTodo|Marble|Extend current print dialog with Marble option page for configuration|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Optional inclusion of legend and routing instructions|[email protected]|Dennis Nienhüser}}
 +
|}
 +
 
 +
=== Route state save ===
 +
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureTodo|Marble|Check KML export of route elements|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Auto-save route to kml file at appropriate times|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Auto-load kml route at startup, if any|[email protected]|Dennis Nienhüser}}
 +
|}
 +
 
 +
=== Worldwide and Offline Routing ===
 +
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureInProgress|Marble|Include gosmore-instructions in Marble|[email protected]|Dennis Nienhüser}}
 +
{{FeatureInProgress|Marble|Also parse routino output|[email protected]|Dennis Nienhüser}}
 +
|}
 +
 
 +
=== Routing API ===
 +
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureTodo|Marble|Rename RouteSkeleton to RouteRequest|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Routing API review|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Decouple RoutingWidget, RoutingLayer and RoutingManager|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Export RoutingManager and RouteRequest headers|[email protected]|Dennis Nienhüser}}
 +
|}
 +
 
 +
=== Turn-by-turn Navigation ===
 +
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureTodo|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)||}}
 +
{{FeatureTodo|Marble|Swap z-order of current position indicator and route waypoints||}}
 +
{{FeatureTodo|Marble|Make current position indicator better visible (e.g. include half-transparent indicating position dop)||}}
 +
{{FeatureTodo|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||}}
 +
|}
 +
 
 +
=== General Polishing ===
 +
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
 +
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 +
! Status
 +
! Project
 +
! Description
 +
! Contact
 +
{{FeatureTodo|Marble|Reset stored position in via point input widgets when user starts editing it|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Use geodatacoordinates string as via input widget text only when reverse geocoding fails|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Custom, i18ned display of (nominatim) reverse geocoding results also respecting the altitude (zoom)|[email protected]|Dennis Nienhüser}}
 +
{{FeatureTodo|Marble|Minimize the total number of MarbleRunnerManager instances|[email protected]|Dennis Nienhüser}}
 +
|}
 +
 
  
 
== Undecided ==
 
== Undecided ==
 
* Tour height profiles (using SRTM data)
 
* Tour height profiles (using SRTM data)
 
* Multiple routes (one active route)
 
* Multiple routes (one active route)
−
* KML import and export
 
−
* Support for other routing services
 
−
* Offline routing
 

Revision as of 14:32, 22 August 2010

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)
Retrieved from "https://techbase.kde.org/index.php?title=Marble/RoutingRoadmap&oldid=53844"

This page was last edited on 22 August 2010, at 14:32. Content is available under Creative Commons License SA 4.0 unless otherwise noted.