Mac POI Loader 2.1.0 Proximity Quirk - Anyone Else?
Thu, 04/30/2009 - 9:21pm
RKLLKR
17 years
Using OS X 10.4.11 and Garmin Mac POI Loader 2.1.0
I get the following quirky behaviour.
If I create a POI file using Manual Method and a Proximity Distance from a CSV file on my IMac and written back to the IMac then transfer the resulting GPI file onto my Nuvi 360, the proximity distances are not set in the GPI on the Nuvi.
However, if I create the same POI file but get POI Loader to write the file directly onto my Nuvi 360, the proximity distances are set correctly.
Anybody getting the same quirk? Anybody have an idea why beyond Garmin wrote "bad" code?
Using OS X 10.4.11 and Garmin Mac POI Loader 2.1.0
I get the following quirky behaviour.
If I create a POI file using Manual Method and a Proximity Distance from a CSV file on my IMac and written back to the IMac then transfer the resulting GPI file onto my Nuvi 360, the proximity distances are not set in the GPI on the Nuvi.
However, if I create the same POI file but get POI Loader to write the file directly onto my Nuvi 360, the proximity distances are set correctly.
Anybody getting the same quirk? Anybody have an idea why beyond Garmin wrote "bad" code?
Cheers
Bob
Ottawa,
Not the Illinois one.