Route Optimisation: Difference between revisions

From Acacia Support Wiki
Jump to navigation Jump to search
(Created page with "The Route optimisation process: * Loads all of the turning points from the GPX, KML or KMZ file. * Removes unnecessary intermediate turning points....")
 
No edit summary
Line 1: Line 1:
The [[Route]] [[Route Optimisation|optimisation]] process:
The [[Route]] [[Route Optimisation|optimisation]] process:
* Loads all of the turning points from the GPX, KML or KMZ file.
* Loads all of the turning points from the GPX, KML or KMZ file.
* Removes unnecessary intermediate turning points.  This tends to pick the shortest path to minimise your paddle time.
* Removes unnecessary intermediate [[Waypoints|Turning Point]]s.  This tends to pick the shortest path to minimise your paddle time.
* Pre-calculates all the statistics required to track your paddling including:
* Pre-calculates all the statistics required to track your paddling including:
** Distance from start and finish
** Distance from start and finish
** Turn angles
** Turn angles
** [[Bisect Line]] coordinates and angle
** [[Bisect Line]] coordinates and angle
** [[Waypoint]] locations and labels.
** [[Waypoints|Waypoint]] locations and labels.
* Stores the [[Route]] in an internal database for faster performance and allows KayakNav to handle as many routes of virtually any size without memory issues.
* Stores the [[Route]] in an internal database for faster performance and allows KayakNav to handle as many routes of virtually any size without memory issues.

Revision as of 16:03, 8 March 2017

The Route optimisation process:

  • Loads all of the turning points from the GPX, KML or KMZ file.
  • Removes unnecessary intermediate Turning Points. This tends to pick the shortest path to minimise your paddle time.
  • Pre-calculates all the statistics required to track your paddling including:
    • Distance from start and finish
    • Turn angles
    • Bisect Line coordinates and angle
    • Waypoint locations and labels.
  • Stores the Route in an internal database for faster performance and allows KayakNav to handle as many routes of virtually any size without memory issues.