new & interesting places for your GPS

MacGarminTools not correctly labeling proximity alarm POIs?

 

First off, must say, I just got my nuvi 350. So I'm relatively new to the Nuvi world but have been playing around with a Garmin eMap for a lot longer than I would have liked to. smile

I also have to say Simon's MacGarminTools are excellent - I have used them to create many POI files, complete with audio mp3 files.

However, I must be missing something because I can't seem to get MacGarminTools to set Proximity Alarms correctly.

I create my gpx file from my csv file, and when the template dialog pops up it asks me for Speed or Distance for my alarm. I set distance to 1000 feet, and after chugging away for a while, I get a gpx file which I then transform into a gpi file with his other tool. By the way, with a huge file like the Starbucks one it's quite impressive watching all the points in the US fly around!

When I download the file to the nuvi, I can see the POIs, and even get the little "speaker" in the upper left corner, which when I press it, plays back the mp3 file I included. Wonderful! Even the tiny Starbucks.bmp logos show up on the maps when zoomed!

Unfortunately it doesn't look like an actual Proximity Alarm point to my Nuvi, and, possibly as a consequence of that, the alarms never go off, even when I have them turned on under Proximity Points -> Alerts -> Custom Pois (checked).

Now, here's the thing... when I load the same CSV file with MP3 file in using the Garmin POI Loader for Windows (boo, hiss!) smile, if I browse the Custom POIs under Favorites, each entry looks different - it actually says Proximity Alarm Distance: 1001 feet. Unfortunately, no .mp3 sound file, so no speaker, which is surprising. It does see the Starbucks.bmp file, so the logos show up on the map.

Am I not doing something right?

New info:

Okay, so I finally figured it out and I can't believe I didn't notice this first.

First of all, in case anyone else didn't realize this, there are essentially 3 ways that POIs can be setup on the Nuvi - without proximity data, with proximity data, and with proximity data AND speed data. Additionally, you can choose to add BMP, JPEG and MP3 files to each of them.

When using a program like MacGarminTools, you have control over each of these elements, but the with the Garmin POI Loader tool, for the most part, you don't, at least not directly.

The ONLY way, as far as I can tell, on the Nuvi, to get an MP3 file to play whenever you get near one of your POIs is to have the POI function as a TourGuide. To do this, you have to run on AutoPlay mode for TourGuide under the Proximity Points menu, and NOT set the Speed data for the POI. It's important to actually NOT set any value, not just set a value of 0 mph, which is what the Garmin POI Loader seems to want to do. If the speed data is set, the POI will NOT be seen as a TourGuide point and will instead be seen as a Speeding POI, which will play a loud DING sound, as opposed to your MP3 file. Additionally, your POI will not be identified with its name and all you will get is a red rectangle warning you that you are going faster than 0 mph. Yeah, no kidding! smile

You still have to attach an MP3 file to the points, which you can do by naming it the same as your companion .CSV file when you run it through csv2gpx. When the template editor panel shows up, be sure to choose a reasonable distance (I choose 1000 feet) so you'll have a decent shot of getting close to your POI.

Different types of audio attachment

Assuming you're using the same input files (especially the MP3), then something's not quite right...

You should only see the little 'speaker' icon for TourGuide audio. The fundamental difference between TourGuide Audio and an ordinary MP3, is the 'controllability' of the audio. Usually, when an MP3 is associated with a Proximity Alert, it just plays from start-to-end; you get no option to start or stop it manually.

When using POI Loader (for Windows), the thing that determines which type of audio it is, is the name of the file. If the filename doesn't contain "TourGuide", then it is an 'ordinary' MP3 file. (This is POI Loader's interpretation, not the Nüvi's). Maybe Garmin have implemented it differently in the MAC version (consistency is not their strong point :-( ... or maybe it's just a bug?

--
------------------------ Phil Hornby, Stockport, England ----------------------               http://GeePeeEx.com - Garmin POI Creation made easy           »      

Ah...

That explains at least part of the mystery to me. I will not be so concerned with the absence of the Speaker icon now. smile

I do have a PC at my disposal so I'm going to learn about POIs on that first to make sure I'm doing something seriously wrong. I did notice that my Proximity Alerts somehow are getting mistaken as Speed=0mph alerts. Whenever I get in range of a Starbucks now, I get "Speed Alert: 0 mph" in red at the top of my screen! smile

BTW - I'm using a brand new Nuvi 350 with the latest firmware and US NT 2008 maps.

check your poi file name

Pretzel wrote:

That explains at least part of the mystery to me. I will not be so concerned with the absence of the Speaker icon now. smile

I do have a PC at my disposal so I'm going to learn about POIs on that first to make sure I'm doing something seriously wrong. I did notice that my Proximity Alerts somehow are getting mistaken as Speed=0mph alerts. Whenever I get in range of a Starbucks now, I get "Speed Alert: 0 mph" in red at the top of my screen! smile

BTW - I'm using a brand new Nuvi 350 with the latest firmware and US NT 2008 maps.

perhaps your file is named something like,
Starbucks_0.csv or Starbucks1.csv

--
........Garmin StreetPilot c550 / Nüvi 765...........

Should also add...

As far as I can tell, the nuvi 350 is not able to run Proximity WITH speed alerts and alter the sound file. It will always just play the DING default sound.

The only way to get Proximity without speed alert sounds to be different is to actually use the TourGuide feature which is controlled separately with the TourGuide AutoPlay feature. In that case what you are doing is technically not a Proximity POI, although it functions in much the same way. The TourGuide AutoPlay is actually better in many ways because instead of just showing you a red border, it will display the name of the particular POI you are encountering, which for Red Light cameras can contain something descriptive like the two streets involved in the intersection. This way you can decide whether the POI you are being alerted to is something you need to continue to pay attention to, since it will alert you even after you've passed through the intersection, or if you are approaching it from a different angle, but not passing through it.

sponsored links