This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:notecoords [2021/04/27 14:54] – [Backup waypoints in personal note] lineflyer | en:notecoords [2021/11/23 11:09] (current) – [Using keywords for waypoint types] use SVG icons lineflyer | ||
---|---|---|---|
Line 30: | Line 30: | ||
^ Icon ^ Waypoint type ^ Keyword in personal note ^ Short ID in personal note ^ | ^ Icon ^ Waypoint type ^ Keyword in personal note ^ Short ID in personal note ^ | ||
- | |{{ : | + | |{{ : |
- | |{{ : | + | |{{ : |
- | |{{ : | + | |{{ : |
- | |{{ : | + | |{{ : |
- | |{{ : | + | |{{ : |
- | |{{ : | + | |{{ : |
c:geo will recognize the following keyword formats as waypoint type identifiers (all of them case-insensitive): | c:geo will recognize the following keyword formats as waypoint type identifiers (all of them case-insensitive): | ||
Line 56: | Line 56: | ||
It is possible to create a textual backup of all your user-modified waypoint data in the personal note. You can upload this note to the geocaching server (if the used geocaching provider supports it) and thus easily backup your custom waypoint data. Due to the above described waypoint parsing this data can then be restored to your waypoint list in case it gets lost or is deleted from your local device. | It is possible to create a textual backup of all your user-modified waypoint data in the personal note. You can upload this note to the geocaching server (if the used geocaching provider supports it) and thus easily backup your custom waypoint data. Due to the above described waypoint parsing this data can then be restored to your waypoint list in case it gets lost or is deleted from your local device. | ||
- | To create the textual backup, use the icon {{:ic_menu_upload.png? | + | To create the textual backup, use the icon {{:ic_menu_waypoint_sync.svg? |
- | To refresh the textual waypoint backup, tap button '' | + | To refresh the textual waypoint backup, tap the icon {{: |
As an example, when executed on the following waypoints: | As an example, when executed on the following waypoints: | ||
Line 85: | Line 85: | ||
* **Waypoint type**: same rules apply as discussed in previous sections. | * **Waypoint type**: same rules apply as discussed in previous sections. | ||
* **Coordinate**: | * **Coordinate**: | ||
+ | * **Formula**: | ||
The geocaches waypoint list is modified with this information as follows: | The geocaches waypoint list is modified with this information as follows: | ||
Line 94: | Line 95: | ||
* For predefined waypoints the only things that can be modified are the coordinate (if the cache owner defined it empty) and the user note. | * For predefined waypoints the only things that can be modified are the coordinate (if the cache owner defined it empty) and the user note. | ||
* In existing waypoints, fields are only overridden when they are empty or filled with a default value (e.g. system-generated waypoint name) | * In existing waypoints, fields are only overridden when they are empty or filled with a default value (e.g. system-generated waypoint name) | ||
+ | * A formula in '' | ||
The following examples show different texts on the left and the waypoints created out of them on the right | The following examples show different texts on the left and the waypoints created out of them on the right | ||
Line 100: | Line 102: | ||
| '' | | '' | ||
| '' | | '' | ||
- | | '' | + | | '' |
+ | | '' | ||