|
Option |
Effect
when enabled |
| GENERAL |
|
| Default Country (for Geocoder). |
This provides a default Country for Geocoding operations. It should probably be specified as an ISO 3166 string (US,GB,CA etc), though phrases such as "United Kingdom" work as well. |
| Do not write "Country" field to gpx file |
Most units do not write address data in the correct order. In most cases, this is not noticeable if the Country field is omitted. |
| Pad Waypoint names to overcome line 2 formatting bug |
On some units, data is repeated on the 2nd line of the display in a huge font!. This option prevents this from happening by appending a "." to Waypoint names - when necessary. If the name already ends in ".", it is removed instead. |
| Measurements are metric |
This alters the interface units to their metric equivalents. You should select the equivalent setting in POILoader. |
| Write Relative Links |
To facilitate sharing data with others, references to image & sound files can be stored relative to the referencing GPX file, instead of as hard-coded references to your PC file system. |
| DUPLICATE HANDLING |
|
| Auto-rename duplicates |
When opening an existing file (not Merging, when the option is implicitly enabled), this option will deal with duplicate Waypoint names, by appending digits. |
| Flag duplicates in grey and de-select for output |
Any detected duplicates will be shown in grey and the [ ] check box will be cleared, so that, by default, they will NOT be written to the output file. |
| Allow duplicates in output file. |
This option strips any digits that were automatically added to duplicates to make them unique. The original (duplicate) names are then written to the output file. [This is work in progress] |
| CSV-RELATED |
|
| Col 4 is Address, not Description |
Although column 4 (in a CSV file) is described as a 'comment' field, and is therefore logically Page 2 data, many people seem to use it for Address information. When this option is enabled, column 4 data will be placed on Page 1. |
| Attempt telephone number recognition in CSV files |
GeePeeEx will use its internal rules to try and detect valid telephone numbers in CSV column 4 data. Any that are detected are placed in the field - and will be 'auto-diallable' when used in a compatible unit. |
| Minimum length for a telephone number |
An addition rule that limits false matches when searching for telephone numbers. Especially useful when ZIP codes are present and are adjacent to telephone numbers. |
| Custom Search String |
This is an additional rule for the telephone number search facility. It is an arbitary string to search for, that is known to prefix telephone number data. It is utilised first and is NOT saved for subsequent runs. |
| Enable automatic 'Header' recognition |
This determines whether or not GeePeeEx Editor should try and interprete the first line of a csv file as column headers. If unrecognised headers are detected, GeePeeEx will switch to standard '4 column' mode automatically. This option is provided to prevent GeePeeEx Editor misinterpreting DATA as a column header. |