User Tools

Site Tools


Using Personal Notes to create and store waypoint information

Automatic creation of waypoints

If your personal note of a cache contains valid coordinates (e.g. N50 10.123 E010 34.876) c:geo will automatically create a waypoint from it in the waypoint tab of this cache.

If for example this is the content of your personal note:

c:geo will automatically create this waypoint for it:

Subsequent coordinates in your personal note will also be transferred to a waypoint in the same way and the waypoint name numbered accordingly.

If the waypoints of a cache already contain the same coordinates as found in your personal note, c:geo will not create a new waypoint for these coordinates as it assumes them to be an unnecessary duplicate in this case. Two coordinates are consideres “same” in this sense when they are identical written in Geocaching standard Decimal-Minute Format (e.g. N50 10.123 E010 34.876)

Using keywords for waypoint types

Normally c:geo will define the waypoint type for coordinates found in the personal note as Reference Point, however you can use keywords in your personal note to enforce another waypoint type being used.

You just place one of the following keywords in front of the coordinates:

Icon Waypoint type Keyword in personal note ShortId in personal note
Parking AreaPARKINGP
Question to AnswerPUZZLEX
Stage of a Multi cacheSTAGES
Reference PointWAYPOINTW
Final LocationFINALF

c:geo will recognize the following keyword formats as waypoint type identifiers (all of them case-insensitive):

  • the keyword itself
  • 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

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.

As an example look at the following personal note which uses some variants of the above to create waypoints for different types:

which then automatically creates these waypoints for you:

Backup waypoints in personal note

It is possible to create a textual backup of all your user-modified waypoint data in the personal note. You can upload this PN and thus backup your waypoint data. Due to 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 button Add/Update waypoints under the personal note. A textual section will be created in your personal note starting with {c:geo-start} and ending with {c:geo-end}. It contains all user-defined waypoint data from the waypoint list in advanced waypoint syntax (which is explained in the next section).

To refresh the textual waypoint backup, click button Add/Update waypoints again. To removeit, click button Remove waypoints.

As an example, when executed on the following waypoints:

This function will create this textual backup:

Advanced waypoint syntax

Perhaps you noticed that waypoints from personal note were created with default names like e.g. Personal Note 2. If you want to perform more advanced waypoint operations from your personal notes you have to use advanced waypoint syntax. With this you can:

  • Modify properties of predefined waypoints (=waypoints which were predefined by the cache owner in the listing): coordinate and user note
  • Create or modify waypoint type, name and user note in user-defined waypoints

To do this, use the following syntax in your personal note:

@[<prefix>]<name> (<waypointTypeId>) <coordinate> “<user note>”

Advanced format is recognized when it starts with a @ at the beginning of a new line. The following content is parsed:

  • Waypoint Name: everything between the @ and the coordinate is considered to be a part of the waypoint name, except when it is in parenthesis ()
  • Prefix: If the @ is directly followed by square brackets [], then the content of these brackets is considered to be the prefix of the waypoint you want to edit
  • User note: If the coordinate is immediately followed by (in same or next line), then everything between this and the next is considered to be part of the waypoint's user note (including line breaks). If the coordinate is not followed by but has additional content on same line, then this content is considered to be the waypoint's user note
  • Waypoint type: same rules apply as discussed in previous sections.
  • Coordinate: same rules apply as discussed in previous sections. Additionally there is a “special” coordinate tag (NO-COORD) which can be used to specify an empty coordinate (this is necessary in the very special case that one wants to modify the user note of a predefined waypoint which has no coordinate)

The geocaches waypoint list is modified with this information as follows:

  • If a prefix is parsed and a waypoint is found with the same prefix, then it is assumed that this waypoint should be modified. This is usually only used for predefined waypoints.
  • If a waypoint is found with the same coordinate as the waypoint parsed, then it is assumed that this waypoint should be modified.
  • Otherwise a new waypoint is created.

In case a waypoint is modified, the following rules apply:

  • 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)

The following examples show different texts on the left and the waypoints created out of them on the right

Personal note text produced waypoint
@ A good parking place N50 11.456 E010 35.345 park under the oak tree
@ (X) marks the spot N50 12.010 E010 33.783
@[S5]Station 5 (X) (NO-COORD) “We have to think about this later”
(Note: this example assumes that there is a predefined waypoint in the listing with prefix S5)
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information
en/notecoords.txt · Last modified: 2020/08/19 23:24 by eddiemuc