How do custom POI files use GPS coordinates?
Fri, 10/04/2019 - 11:08am
 |
    5 years
|
I'm testing a new custom POI file. I used POILoader to install the .csx file and used the custom POI file to navigate to a point of interest in a Garmin GPS. I made a mistake in entering the street address for one local POI I was testing.
I would have thought the Garmin GPS would use the GPS coordinates in the POI file for navigation, but it doesn't. It's using the street address and ignoring the GPS coordinates in the custom POI file when the two data elements for one POI point to two different locations.
So what are the GPS coordinates in custom POI files used for, if not for navigation? Why do we need to enter them?
post the text string
Can you post the text string of the single line in the POI file that you are referring to?
dobs108
Custom POI
I'm testing a new custom POI file. I used POILoader to install the .csx file and used the custom POI file to navigate to a point of interest in a Garmin GPS. I made a mistake in entering the street address for one local POI I was testing.
...
It sounds like, after you pressed "Where To?" on the menu, that you then pressed "Address" rather than pressing "Custom POIs" on the next screen.
There is no way that your GPS is going to be able to search within your "Custom POIs" to see if there is an "address" that matches what you entered. When you select a Custom POI, the GPS will use the "coordinates" of the POI entry to navigate there.
Not my experience.
It has been my experience that the gps coordinates are used and the field address is ignored.
GPS coordinates
Thanks all for the quick answers.
Using the GPS coordinates in the custom POI is what I expected the Garmin GPS to do.
In the wake of your answers, I took the test file off the GPS, loaded an edited .csv file with mismatched GPS coordinates and street address, and it ignored the street address and went to the GPS coordinates as you say.
BTW I wasn't *trying* to see the first time what would happen if coordinates and address don't match; I was testing formatting of coordinates in the .csv file to make sure it navigated as intended. When the GPS wanted to go the wrong way, I backtracked and realized I had entered the address incorrectly. The only thing I can think of now is I must have also entered one of the coordinates just slightly off, because the GPS wanted to navigate just a few miles away from the intended destination. I did know you have to have the longitude number (negative 70s to 100s) first in the CSV file; omitting the negative sign or putting latitude first wasn't my issue either.
Good thought, JG, as an issue with command sequence is one way to go wrong, but I wasn't pressing Address (or typing in or selecting an address). I wasn't using the Search button within the Custom POI, just touching one POI in a file I'd loaded into Custom POIs on the Garmin.
Anyway I've got this working now as intended. Thanks all for your help.
"141 could draw faster than he, but Irving was looking for 143..."