Route Optimisation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The [[Route]] [[Route Optimisation|optimisation]] process: | The [[Route]] [[Route Optimisation|optimisation]] process: | ||
* Loads all of the | * Loads all of the [[Waypoints|Turning Point]]s from the GPX, KML or KMZ file. | ||
* Removes unnecessary intermediate [[Waypoints|Turning Point]]s. 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: | ||
Revision as of 16:06, 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.