TourGuide proximity alert troubleshooting

Did you have the characters "TourGuide" in the name of the file on which you set the 10,000 proximity alert?

You must use those characters exactly - NOTE the capital "T" and the capital "G". I believe POILoader is looking for that character string to change from an "along the route" alert to a "radius" alert.

It soes not matter is the character string is at the beginning, middle, or end of the file name - they just must be somewhere.

Try letting the POI loader transfer the file instead of manually.

Yes, I have that exact case-sensitive string in the filename.

Will try it and report back...

Seems like it should make no difference but since he has the exact case sensitive character string, you may be right.

Ok, listen to this. Since I couldn't get a TourGuide file to work, I called Garmin. They transferred me to the "software department". They told me that my unit is not compatible with TourGuide files (it does not have an MP3 player), and nor do any new models (customers doesn't use it).

But more significantly, they told me standard alerts work at a radius like I wanted (you don't have to be on the same street). This would make sense to me from a software standpoint, because the unit doesn't know what "street" the POI is on, just the lat/long. The street information in the poi file is just a note that displays right? He said they've tested this and that's the case. I guess I have more testing to do on mine to confirm that. That would be welcome news to me, but it contradicts a lot of what I've read about proximity alerts (supposedly they only work if you're on the same street as the POI).

I learn something new everyday!

To be an TourGuide file it have to have an sound file , mp3 or wav. No sound file no TourGuide. In all Nuvi the ordenery PoiLoader proximity are"along road", if the nuvi40 makes it an 360 degrees alert I would say its a bug.
In garmins xml schema they have Along road (PoiLoader type),Proximity (360degrees type)and TourGuide.
If the nuvi40 get an 360 degrees with PoiLoader this really mess it up.

I have several TourGuide files and I have always had a .wav file (even though my unit will use .mp3s) so never had the problem. However, Gary Hayman's site seems to imply that you must have one.

So also does POILoader Help

"TourGuide is a feature available on compatible Garmin devices. TourGuide files include Custom POIs with descriptive .mp3 audio files. When you approach a TourGuide point, the .mp3 file plays and provides you with information about that point, much like a guided tour. TourGuide files must be saved as .gpx files.

To create TourGuide points, follow the steps for creating Creating Custom POIs in MapSource and use the File/URL field to attach the appropriate .mp3 files to the points. The .mp3s must contain the word “TourGuide” in the file name to activate the TourGuide feature. For example, “TourGuide.mp3”, “TourGuide USA.mp3”, or “TourGuide 12.mp3” are all valid TourGuide file names."

Sorry I missed that in my initial reply.

The files I use for alerts are "Food" files. I have all my food files in a folder called "Food". I use csv files. Some are "redlight alerts" and some are "TourGuide alerts". I get alerted along the route for redlight and radius for the TourGuide.

Some have wav files and some don't. I get alerted as I expect.

My first GPS was a Streetpilot 340 and would not play wav files. I used TourGuide for Cracker Barrels and it worked giving me the standard bong alert.

Being on the same road that the business is located does not mean the coordinates are set there.The alert is based on coordinate location.They could be at the street entrance,off ramp or the business location itself.

TourGuide in the file name will give you a radius alert.Set a standard alert for something like Cracker Barrel and ride down a interstate and see how many alerts you get. Put TourGuide in the name and note the big difference.A lot of users on this site use TourGuide files and can give you a better insight on TourGuide files then Garmin.They don,t even offer information on wav files.

The OP stated they saved it as a CSV, not a GPX.

A test for a TourGuide alert might be to create, then either drive or simulate a route to one of TourGuide POI locations. With a 10,000' Tourguide alert, you should get a visual and audio alert about 2 miles before arriving at the final destination. This should avoid errors due to POI location variation, especially with big box stores with multi entrances and ginormous parking lots.

If this doesn't give an alert, we need to look at how the POI file was set up. If it does alert at the proper radius, then POI location issues may come into play--either due to the POI location be offset from its real location or the possibility that the location you're driving to may not be part of the POI file line items.

My only TourGuide is a csv--and it works.

But the issue that a TourGuide must have an associated audio file could be the culprit if the OP didn't load one--or if there's a wav/sox sort of error preventing a successful audio load.

This FAQ to me is one of the best on TourGuide in the file name posted http://www.poi-factory.com/node/13958 using csv or gpx.

deere478, did you load a wav file (plus an optional icon) along with your TourGuide csv? If so, and if you're on a PC, did you install sox.exe on your computer to allow the wav file to be loaded? vestenfjell states that TourGuides require an audio file.

PS--re: your call to Garmin CS. I think you'll find that for this sort of issue, you'll receive quicker and more accurate info from POI Factory members here than you will from Tech Support. Garmin's Customer Service is better than us for some issues but this is one that I believe is not one of their their strong suits. Here at The Factory, we have many folks that have gotten TourGuides to work with most nuvi models and know the likely problem areas, so my 2 cents is with us here for this problem.

I haven't given up on the TourGuide files, but I am guessing my 40LM software doesn't even recognize this since it doesn't have the .mp3 capability. I will try a .wav yet too.

I need to prove/disprove Garmin Tech support info that the standard Custom POI alerts (with no particular code words in the file name) are always based on a radius. He described this as a large circle, drawn on a map around the coordinate which is exactly what I would want. Granted I can understand a Redlight POI not working that way, it needs to be on the road traveled or you'd get false alerts from cross streets or adjacent streets. He said that's the case with all their GPS's. I specifically asked if this was a recent change and he said no its always been this way. I would hope they know what they are talking about but I gotta see it to believe it And I believe the experiences of others shared here.

Its easy to try. Make an TourGuide without wav/mp3 files and open with an Hex editor and see if it have the number for TourGuide alert.The alert should be an 02. along Road 01. 00 is also an 360 degrees .
And maby earlier PoiLoaders didnt needed the sounfiles to make Tourguide. The Sound files are not needed at all to make a Tourguide poi file if you change the alert in an gpi file with an hex editor from 01 to 02 (Along road to TourGuide), its just PoiLoader who needs them.

I would suggest that he work with only 1 file that he wants as a TourGuide. And it might be looking for a wav file. That could be the culprit.

Your Garmin CS agent stating that Custom POIs are and have always been radius alerts is false. Don't try to convince them of their error as you have better things to do with your time, like getting your TourGuide with an associated wav audio file, to work with your nuvi. Unless you're using a Mac, be sure to read and exactly follow the instructions for installing sox.exe on your PC. Do not try to use a newer version of sox:

http://www.poi-factory.com/node/25730

Although yours is a new 2012 nuvi model and therefore may have features and issues that we're not used to, I'd be very surprised if your nuvi won't play wav audio and equally surprised if your nuvi can't do TourGuides.

You're all right, Garmin tech support was confidently WRONG! I drove down a side street right past a POI with no alert till I got to the address street (well within my alert limit range) and then it went off. I'll follow up with the posted suggestions to get a TourGuide working. I think they need a file-name Keyword for this besides TourGuide, especially if they are eliminating the TourGuide functionality. A large radius alert is primarily what I wanted a GPS for. If all else fails I'll return this 40 and get something that works for me.

Working with Windows XP here. Not sure I'd have a hex editor or I'd take a look. I opened the GPI with a notepad and it was odd characters, along with all the CSV text that was in Quotes.

It's not just Garmin, it's most Tech Support (and the service techs sent out in trucks by businesses like ISP companies, for instance). Your first communication or visit is almost always with a Level 1 person. These folks are frequently reading from a script and many don't realize when it's time to boot your call to a higher level. Yes, if you're like me, the most aggravating among these folks is the group that insists they are right, even when presented with information that clearly shows their statements to be wrong.

We need to cut the Customer Service folks some slack since these are the folks that deal with people calling in during a power failure in their home asking why their desktop computer isn't working and I can see how previous calls like these can jade the CS staff into thinking that their answers should be accepted as fact.

I'm not sure if it's still true but in the past Garmin did not acknowledge that with sox.exe for PCs, that POILoader could install wav file audio alerts to nuvis. The discussion of Junction View files in the past six months or so has also shown where Level 1 techs are "confidently wrong" in your words. That's a great phrase, by the way

Actually the Level 1 was quick to say he found nothing in their documentation about this and passed me up to the "software department" which was an additional 20 minute wait. Thank goodness for a cordless speakerphone. And to think they make glass Avionics which include aircraft crash avoidance systems But that's all water over the dam, on to trying the suggestions here...

But, avionics aren't going for $100-$400, are they? Add a few zeros.

Nonetheless, most of these reps aren't career reps. It's a filler while they go to school etc. Add to that fray by outsourcing, and low pay, you won't get people who are knowledgeable or care.

I just loaded my TourGuide file with and then without wav.

Thanks, that is a good guide.

Ok I read all the suggestions here and have set up some TourGuide POI's to test for 360-degree alerts tomorrow.

*Added the Sox.exe files to the POI Loader directory
*In a folder named TourGuidePOIs I created:
TourGuide alert.csv (2 known poi test locations)
TourGuide alert.wav file to the directory
*Used POI Loader with the direct file transfer to the unit (note the POI Loader didn't put the .wav file on my gps, I had to drop that in the GPS POI folder manually.)
*Set specific limit distances at 500 feet in POI Loader manual mode
*The GPS POI folder now contains:
TourGuidePOIs.gpi
TourGuide alert.wav
(I believe I'm correct naming the .wav to match the .csv filename, rather than the .gpi file name)

Should I expect the typical text flag alert on the screen, or only the .wav file sound? My standard alerts 'ding' and display the "Description" and Icon if any.

I have 2 weeks to decide whether to Return this 40LM to radio shack. May just have to do that and check out the 1350's etc.

You (should) get the text balloon, and the wav sound. And yes, you were correct in putting the wav in the same folder as the poi.

When you run poiloader both files become one gpi file. You don't drop the wav file in the poi folder.Should look like this when you run poiloader

TourGuidePOIs= Main folder
TourGuide alert.csv
TourGuide alert.wav

Its working when loaded with the .wav file! I approached some TourGuide points from several directions and instead of an on-screeen "Alert: ***", I got the "TourGuide: ***" and also the .wav file played. Oddly one of them played the audio .wav pretty randomly while within the radius, the other just seemed to play it once when I entered the radius. These were just 2 different coordinates in the same source .CSV file

Thanks thanks thanks for the suggestions, several of you were correct in that the .wav is required (I didn't even know my unit would play .wav files). "vestenfjell": Do you think perhaps the POI Loader marks it as a radius alert if there is a .wav file in the source folder, but it is not required in the GPS POI folder in order to work? Your comments about the Hex file numbers I think infer that. I'll have to try that. That would be nice if I wanted visual alerts but no audio alerts, with no other way to mute particular POI's.

Anyway, glad its working. Now I can keep this 40LM

One odd issue I have is, in my Settings menu of the GPS (Proximity Alerts>Change), only the default Garmin Safety Cameras are in there. Previously with custom POIs loaded there was a checkbox here to shut off the "Custom POI" alerts. (Only my TourGuide POI's were loaded when I tested this morning)

Well done.

It appears therefore that for TourGuides to work, the characters TourGuide must appear somewhere in the file name and there needs to be an included audio file (wav or mp3).

If you want a radius alert with only a visual alert and no audio, you could create a wav file with no sound lasting a second or so.

That's a good idea. When I loaded it with other POI's and the Custom POI Alerts were turned off in Proximity Settings, the TourGuide .wav files still played so there is no way to mute them short of muting everything.

No need of an wav file in GPS Poi folder, all you need is inside the .gpi file, collected and converted from your source folder with PoiLoader.Gpx/csv + wav + TourGuide name suffix + proximity = successful TourGuide poi file.

To make an TourGuide file with no sound alert, then it is easiest using the method CraigW discribe, with a wav file of silence.

Thank you for contacting Garmin International.

I'd be happy to assist you with this.
While navigating, the proximity point will need to be within 30 meters of the route, regardless of the distance set in the POI Loader, to trigger an alert. This helps to reduce false alerts that can occur if you are traveling on a road close to a proximity point even if it is not affected by the alert.

There are no other settings that can be changed to have separate alerts.

Although Garmin's response is correct when dealing with standard Custom POIs (which seems to be what the agent is answering), it is incorrect for Custom POIs that are TourGuides, the subject of this thread. In fact, the reason for using TourGuides is exactly to get around this issue.

Is it possible to use the default proximity alert like the one used for the red-light cameras poi file for a tour guide file? If I don't include an audio file with my tour guide file will it default to the boing boing? I'm running a Nuvi1450.

Thanks.

Tour guide files REQUIRE an audio file. If you don't specify a distance, the file defaults to 1320 feet or approximately 400 meters.

While the official POI Loader help file is woefully out of date, it does provide some guidance:

Creating TourGuide Files

TourGuide is a feature available on compatible Garmin devices*. TourGuide files include Custom POIs with descriptive .mp3 audio files. When you approach a TourGuide point, the .mp3 file plays and provides you with information about that point, much like a guided tour. TourGuide files must be saved as .gpx files. [Note: Newer units don't use MP3 files as the MP3 decoders have been deleted from all the currently offered units. There is a third-party utility, SOX.exe which will allow WAV files to be heard. http://www.poi-factory.com/node/25730 ]

NOTE: TourGuide files are usually created by third party developers. [Most users on this site use the alerting capability of a TourGuide file rather than building a true TourGuide file which would have a different audio file for each point.]

To create TourGuide points, follow the steps for creating Creating Custom POIs in MapSource and use the File/URL field to attach the appropriate .mp3 files to the points. The .mp3s must contain the word "TourGuide" in the file name to activate the TourGuide feature. For example, "TourGuide.mp3", "TourGuide USA.mp3", or "TourGuide 12.mp3" are all valid TourGuide file names.

After you have created all your TourGuide points, save them as a .gpx file. See Creating Custom POIs in MapSource for more information. [Note: you can add the keyword TourGuide to a CSV file as well if you want just the alerting capability. You will need the audio file and an optional icon.]

After you have saved your TourGuide points in a .gpx file, you can save them on an SD card or load them on your compatible GPS unit using Express Mode or Manual Mode.
Adding Pictures to TourGuide Points

You can add .jpg images to your TourGuide points by following the steps for creating Creating Custom POIs in MapSource. Save the .jpg images and TourGuide .mp3 files in a directory, then use the File/URL field to link to that directory.

You can also include the path to the .jpg image in the ID3 data of your TourGuide .mp3 file. Search the internet for more information on ID3 tags for .mp3 files.

*Except for our basic handhelds and older Rino® two-way radio GPS units, all of our current Outdoor and Automotive products are compatible with custom POIs. Tour Guide POIs are only compatible with our MP3 capable nüvi® and zumo® units. Please check your particular Garmin model’s spec sheet for custom POI compatibility."

[NOTE: I don't think any of the active users on this site have ever created a 'true' Tour Guide file which has separate audio files for each location or JPEG photos. Most of us use TourGuide to change the alert type from an "along the route" to an area alert. The commercial Tour Guides I have seen for use in Garmin units have all been compiled into GPI files rather than being made available as GPX files with their associated audio files and images. A 'true' TourGuide file would have to be in GPX format as it is the only format allowing you to associate different images or audio files to individual locations. Just adding the keyword to a file, sound and icon associates the same image and sound to all locations within the file.]