NEW: The resulting KML from this app can now be imported/converted into a PurplePen file for more detailed course setting etc - See the 'Course file to PPEN' app.

Instruction:
MapRun Checksite functions include dropping waypoints along the route and adding a short text description to them if desired. The main use-case is setting up a MapRun CheckSite with a map (KMZ) and going out to look for locations to place controls - dropping waypoints at these locations. This conversion will pull out the waypoints and convert them to a (almost) MapRun formatted KML file. Note that the intent is to produce a draft MapRun KML that will likely need adjusting in Google Earth (correct all Control Codes, order correctly etc) to fully function in MapRun. The CLEANUP/RENUMBER KML App can be used to adjust a number of these potential MapRun requirements.

Any text added to the waypoint will be maintained under a <description> element in the KML that will be visible within Google Earth for each pin but will have no impact within MapRun. There is the option to inlude draft Control Codes in the Waypoint description. These will be parsed out as Control Codes for the KML as described below. This tool is offered as is with no guarantees so use at your own risk.

The ' Controls Start From ' buttons select whether to start assigning Control Codes, if not embedded in the Waypoint description, commencing at 1 or 31 (default is 31). This process will not duplicate any codes parsed from the description.

KML Control Codes (<name> tags) are produced as follows:

Waypoint Descriptions that:

Start with ' @ ' and have up to 3 characters followed by a space or no additional text will use the string following the '@' up to the space.
Have no content will be assigned a code in sequence from either 1 or 31 (with no duplicates).
Have a number up to 3 long with no other content will becomes the number.
Contains '@S' or '@s' becomes S1. Contains '@F' or '@f' becomes F1.

Examples:

' @31 corner of fence ' -> 31
' @32 ' -> 32
' 33 ' -> 33
' ' -> 34 (assigned by the system)
' @35B option ' -> 35B
' @s ' -> S1 (modified by the system)

Note Again: Some basic content screening is reported but the app is not intended to produce a fully functional MapRun KML. For example, if your S1/F1 controsl are not at the beginning and end (or missing) this will be reported but not corrected. If your code contains a letter this will not be corrected but used as is. Many of these things can then be adjusted in the Clean Up app provided.

Waypoint to Control example:

<wpt lat="45.322982" lon="-75.803162">
    <name>@S Start or further N</name>
</wpt>

<Placemark>
    <name>S1</name>
    <description>@S Start or further N</description>
    <Point>
         <coordinates>-75.803162,45.322982,0</coordinates>
    </Point>
</Placemark>