User Tools

Site Tools


route_transfer

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
route_transfer [2020/06/15 19:37]
admin
route_transfer [2021/04/23 15:16] (current)
walterg
Line 1: Line 1:
 ====== Route Transfer (Import, Export) ====== ====== Route Transfer (Import, Export) ======
  
-Kurviger allows to load and store routes in many different formats. This allows you to open routes from different sources in Kurviger, but also to save routes planned with Kurviger on your computer and to export these routes to 3rd party devices and services. Using the same technique you can also save your Kurviger route and load it again later.+Kurviger allows to load and store routes in many different formats. This allows you to open routes from different sources in Kurviger, but also to save routes planned with Kurviger on your computer and to export these routes to 3rd party devices and services. Using the same technique you can also save your Kurviger route and load it again later.\\ 
 +This document is a starter document that links to a lot of information regarding Route Transfer.
  
 ===== Basics ===== ===== Basics =====
  
-When transferring data between different systems, the systems need to speak the same language, in order to get it right. That's why there are different standardized route formats. The most common one is ''GPX'', but there are many others including ''ITN'' and ''KML''. In many ways these formats work with the same mechanics, so understanding the basics will help a lot to understand the greater picture. +  * [[route_transfer:basics|]]
- +
-Usually there are up to three ways to represent route data: +
-  The ''Track'' is an exact copy of the planned route. From a technical perspective, there will be a point every few meters, these points are connected by a line, the Track does not contain any waypoints.  +
-  * The ''Route'' and the ''Waypoints''both contain the waypoints of the planned route and optionally additional waypoints to support the route. Usually the ''Route'' is used to characterize a succession of points which form a route. ''Waypoints'' are often used to visualize points on a map that might not need to be visited in order (for example POIs).  +
- +
-So should you use the ''Track'', the ''Route'', or maybe both? Unfortunately, there is no right answer. It depends on your navigation device / app and on your preferences. The ''Track'' is an exact copy of the planned route, but it's relatively unflexible, you can't just change a part of the planned route. The ''Route'' is relatively flexible, you can delete a waypoint or change a part of the route, but it might be different to the originally planned route. +
- +
-{{ ::route-track-waypoints.png?600 |}} +
- +
-**Left**: Originally planned route\\ +
-**Middle**: Track\\ +
-**Right**: Waypoints / Route +
- +
-Here you can clearly see, when you choose the Waypoints / Route, that the navi can choose the route between the points. In this example, there aren't many places where it could go wrong, but we also placed quite a lot of additional points. +
- +
-The best results are achieved with the [[https://play.google.com/store/apps/details?id=gr.talent.kurviger.pro|Kurviger App]]. +
-For iOS devices it's recommended to use the [[https://apps.apple.com/app/id1089668246|Scenic App]].+
  
 ===== Transferring Routes within Kurviger ===== ===== Transferring Routes within Kurviger =====
route_transfer.1592242656.txt.gz · Last modified: 2020/06/15 19:37 by admin