POI Verifier II

Click on the Link Below

 Poi Verifier II
 What Does it Do?
 How Do I Install It?
 How Do I Use It?
 What Files Created?

 Revision Changes
 Support

How Do I Use This Program?

How do I use this program?
There are 'Tool-Tips' for each option and control. Place the mouse pointer on the item and a pop-up window will appears for a few seconds explaining the item. If more time is needed to read the pop-up, move the mouse pointer off and back onto the item.
(Selections 1 and 2 are required to construct the _V (verified) file.)

1. Select the geographical location of the POIs ('US 48 States', 'US, Canada, PR, and VI', or 'World').
If the POI only contains coordinates located in the 48 states, select that option. If the POI coordinates are limited to the US, Canada, PR, and VI, select that option. If the coordinates cover the entire world, select that option.

2. Check (or uncheck) the 'Check to Search for Duplicate Entries .....' option and change the Longitude/Latitude Variance window if desired.
Unless the POI is a very large file, leave this option checked. It will find duplicate longitude and latitude coordinates. They will not automatically be removed. Because of the fact that many times POIs will correctly contain duplicate coordinates, the user will be given an option to 'Selectively Remove Duplicates'.

3. Check (or uncheck) the 'Check to convert Standard Linebreaks to Nuvi' check box. This will add '_StoNU' to the modified file name.
If you have a nuvi 350 or nuvi360 and the POI contains linebreaks in field 3 and/or field 4, select this option. This will change the POI linebreaks to a format these Nuvis can recognize.

4. Check (or uncheck) the 'Convert Nuvi Linebreaks to Standard' option. This will add '_NUtoS' to the modified file name.
When POI files are constructed with linebreaks which are compatible with the nuvi 350/360, they will not display correctly on other GPS units. When selected, this option will change all of the Nuvi linebreaks in the custom POI file to standard linebreaks.

5. Check (or uncheck) the 'Check to Remove All Linebreaks' box. This will add '_rlb' to the modified file name.
If you are wanting to use this POI with a program that does not recognize linebreaks, select this option. It will remove all linebreaks.

6. Check (or uncheck) the 'Check to create file with POIs for this selected state' box and select the desired State/Province/Territory from the drop-down menu.  This will add '_(xx)' to the state file name.
This program can be used to extract POI line relating to a particular state. Since the extraction process is based on coordinates within a rectangle surrounding the state, often times POI lines in other states that closely surround the desired state will be included. If desired, use notepad to remove these undesired entries.

7. Check (or uncheck)  the 'Check to swap longitude and latitude coordinates' option. This will add '_sll' to the modified file name.
Some Garmin POI files are incorrectly uploaded with the longitude and latitude locations reversed. In addition, some GPS manufacturers require the latitude to be first, followed by the longitude. Also, when construction csv POI files, the information from the Geocoding programs will generally display the latitude first. Selecting this option will correct all of these problems by swapping the longitude and latitude coordinate locations in the selected Custom POI file.

8. Check (or uncheck) the 'Convert Odd Character Count to even in Field 3.  This will add '_OtoE' to the modified file name.
Some GPS units won't display field 3 correctly when the character count is an odd count, or when the count is a specific odd count. When this option is checked there will be a 'Select which Odd to Even Conversion Method" pop-up window for user selection.

9. Click the 'Start Verification' button and follow the prompts.

10. Select the file you want to verify/modify.

11. If there are 'apparent duplicates' in the file, a 'selectively delete duplicates' window will open and allow you to select the duplicates you want deleted.
After running the program, there will be a log file created. Use notepad to read this information and correct any problems shown.


Any reproduction is strictly prohibited.