User Tools

Site Tools


en:notecoords

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
en:notecoords [2020/08/19 19:35] – [Automatic creation of waypoints] eddiemucen:notecoords [2020/08/19 19:54] – [Using keywords for waypoint types] eddiemuc
Line 34: Line 34:
 |{{ :waypoint_flag.png?nolink&40 |}}|Final Location|FINAL|F| |{{ :waypoint_flag.png?nolink&40 |}}|Final Location|FINAL|F|
  
-c:geo will recognize the following keyword formats as waypoint type identifiers:+c:geo will recognize the following keyword formats as waypoint type identifiers (all of them case-insensitive):
   * the keyword itself    * the keyword itself 
   * the ShortId surrounded by parenthesis (e.g. "(f)" to define a waypoint of type "Final")   * the ShortId surrounded by parenthesis (e.g. "(f)" to define a waypoint of type "Final")
-  * the shortId as a single word directly before the coordinate+  * the ShortId as a single word **directly before** the coordinate
  
 Additionally localized waypoint type names (in the language you are using c:geo) will also work, however as c:geo is available in many languages we only list the English keywords here. Additionally localized waypoint type names (in the language you are using c:geo) will also work, however as c:geo is available in many languages we only list the English keywords here.
  
-In our example we created the following personal note:+As an example look at the following personal note which uses some variants of the above to create waypoints for different types:
  
-{{:en:personalnote_wp_3.png?direct&600|}}+{{:en:pn_with_waypoints.png?direct&600|}}
  
 which then automatically creates these waypoints for you: which then automatically creates these waypoints for you:
  
-{{:en:personalnote_wp_4.png?direct&600|}}+{{:en:pn_created_waypoints.png?direct&600|}}
  
  
en/notecoords.txt · Last modified: 2021/11/23 11:09 by lineflyer