Manual vs Express Mode when loading pois to device

 

Hello,

I hope someone will tell me which is the preferred option when installing the Red Light, Speed, and REst Stop pois onto my nuvi.

When I selected the Custom mode, I realized that I did not understand what I was supposed to do next for the rest stop poi. So, I elected Express Mode as my default.

I did the same when I sought to install the speed poi. I did not know what to place in the box that referred to speed speed when I tried the Manual Mode.

Help will be appreciated. Many thanks.mh5m6

But, I really do want to check to see if there is any distance (in feet or miles) that was set for the noise alert when approaching any one of the sites for activation of each of the three pois.

Frequently Asked Questions

Look here first

Then look here

POI Loader

I use POI Loader and always go with manual mode. I like the options it gives me especially when using my own POI files.
The redlight and speed files have default values that I leave as is. For the Rest Stop POI file I use both the speed and proximity settings (60 mph and 7920 feet) so I have ample time to get in the proper lane.

Most other POI's I find 1320 feet (.25 miles) is a good distance to be alerted to an upcoming location.

Since proximity is inputted in feet, I just think of 5280 feet in a mile and divide that number into distances I feel appropriate for various POI files.

Manual mode

chesler wrote:

Hello,

I hope someone will tell me which is the preferred option when installing the Red Light, Speed, and REst Stop pois onto my nuvi.

When I selected the Custom mode, I realized that I did not understand what I was supposed to do next for the rest stop poi. So, I elected Express Mode as my default.

I did the same when I sought to install the speed poi. I did not know what to place in the box that referred to speed speed when I tried the Manual Mode.

Help will be appreciated. Many thanks.mh5m6

But, I really do want to check to see if there is any distance (in feet or miles) that was set for the noise alert when approaching any one of the sites for activation of each of the three pois.

You can find a lot of information on your question using Poiloader help.Just pull up Poiloader and your will see help before you run it.

Click on manual mode on the idex to the left.Also click on speed information.Lots of info there.

--
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.

I use both

I load my Red Light, Speed camera and rest stop files with a manual load and all other POI files in the express mode.

I like to vary the distances for these things....shorter for the red light and speed, much longer for the rest stops.

My Preferences

I always use Poi Loader in manual because if it is used in auto, all proximity alerts default to 1320 feet (a quarter mile) and I feel that is too long a distance for red light cameras and too short for rest areas.

The recommended rest area file is Combined Rest Areas, not individual states. It is more up-to-date and it hardly takes up any room on the nuvi.

Your files should be arranged on the PC each in its own subfolder (for instance, Red Light Cameras) and all the subfolders should be in a folder you can name. I call it "Custom POIs." Each subfolder becomes a category inside the nuvi menu under Extras/Custom POIs.

When you run Poi Loader, first it recognizes your nuvi which is connected with the USB cable. Then browse to the location of your custom POIs folder. The files inside will be grayed out. There is no need to go down into the subfolders and files; Poi Loader does that.

When running Poi Loader in manual you get successive screens, one for each file you are loading. For all the files you mentioned except speed cameras, choose proximity alert and specify the distance you want for that file only.

I choose 600 feet for red light cameras because most of my area has low speed limits and the short distance makes it less confusing to know exactly which intersection has a camera. Out in the country with high speed limits and long distances, choose a longer distance.

For rest areas I use 11440 feet (two miles) so I have plenty of time to decide whether I am stopping and to change lanes.

Any other files like Diners, Drive-ins, and Dives or Walmarts I use 1320 feet.

For speed cameras choose a speed alert and the default speed is zero. Leave it zero, do not enter a number, because the speed for each speed camera is inside the file and overrides the default zero on being loaded into the nuvi.

After you get experience it is easy to run Poi Loader again to change the distances. Remember that Poi Loader is all-or-nothing. Every POI file is overwritten and reinstalled every time you run Poi Loader. That is why you leave your POI files in the same place inside the subfolders inside the Custom POIs folder on the PC!

Many forum participants are knowledgeable and will answer any questions. There is more than one way to skin a cat and I think others will tell you their favorite way to do the same thing!

dobs108 smile

Nice Post!

dobs108, that was a very well written and informative post. Thanks.

I agree - good post

dobs108,

I have seen similar questions in the past and have looked to see if there was a FAQ to point to, but did not find one. Yours was very good.

If you took most of this post, you could copy and paste it into a "create FAQ" screen with a name like "How do I load the camera and rest area files".

Maybe add a download link for POI Loader.

Thanks, perpster and jgermann

Thanks for the encouragement. Creating an FAQ is a good idea.

dobs108 smile

FAQ has been submitted

After Miss Poi posts it, let's think of ideas for improving it.

dobs108

I have linked the new FAQ to

I have linked the new FAQ to the top of the page, great job Dobs108.

Miss POI

Be honored to help

dobs108 wrote:

After Miss Poi posts it, let's think of ideas for improving it.

dobs108

Since the camera and rest area files are a good way to get members "hooked" on the site, we will be glad to make suggestions. I don't know whether a new person would be willing to give you feedback, but I have found (spent a lot of my career in information technology) that the questions a user asks after reading your instructions point out where improvements can be made.

Thanks again.

I normally use auto mode

I normally use auto mode since I live at the edge of the city. When I have to travel in Chicago, I do a manual mode so I can set the RLC distance to 660 feet-the default gives me too many warning for adjacent streets that I won't be traveling on.

Good Idea

nrbovee wrote:

I normally use auto mode since I live at the edge of the city. When I have to travel in Chicago, I do a manual mode so I can set the RLC distance to 660 feet-the default gives me too many warning for adjacent streets that I won't be traveling on.

That's a good idea that solves the problem. Making the alert distance different for different locations can be done but it isn't practical for files that are updated on a weekly basis...

...unless, a future .gpx Red Light Camera file available for download from Poi Factory could contain custom proximity alert distances - 660 feet for downtown Chicago and longer for out in the suburbs.

dobs108 smile

I manually set only these POIs for distance

I manually set only these POIs for distance as follows:
Rest Stop TourGuide: 10,560 feet (2 miles)
Cracker Barrel TourGuide: 10,560 feet (2 miles)
New Time Zone TourGuide: 5,280 feet (1 mile)
Redlight Camera: 660 feet (1/8 mile)

--
Politicians and Diapers must be changed often for the exact same reason...

Note TourGuide

koot wrote:

I manually set only these POIs for distance as follows:
Rest Stop TourGuide: 10,560 feet (2 miles)
Cracker Barrel TourGuide: 10,560 feet (2 miles)
New Time Zone TourGuide: 5,280 feet (1 mile)
Redlight Camera: 660 feet (1/8 mile)

I agree with koot as to the distances he uses.

We should point out that in three of the four cases, koot is loading a "TourGuide" file. If you want to use such a file, it must be named TourGuide. This type of file alerts at distances within a "radius" from your GPS {front, back and to either side). Distinguish this from the redlight camera file which will alert when the GPS is traveling on a road where the POI is within 75 feet of that road AND when the redlight camera is 660 feet ahead of you (in koot's example above).

Alerts

koot wrote:

I manually set only these POIs for distance as follows:
Rest Stop TourGuide: 10,560 feet (2 miles)
Cracker Barrel TourGuide: 10,560 feet (2 miles)
New Time Zone TourGuide: 5,280 feet (1 mile)
Redlight Camera: 660 feet (1/8 mile)

koot kind of curious why you have TourGuide for rest stops?If it is the combined file the coordinates are set at the entrance to the rest stop.Never had a problem with getting alerted using along the road of travel alert.

--
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.

so what is the advantage of

so what is the advantage of using a tourguide as a rest stop poi instead of just using it as a poi file???

i only want to be alerted about the rest stops coming up ahead of me. what option is better for that?

Manual Mode

I always use manual mode

I always use manual... This

I always use manual...
This way you can set your alerts to what you want..

--
Nuvi 350 Born Oct 07 - Nuvi 660 Unit #2 (re)Born Sept 08 - Nuvi 360(Gift to 'the chick' yet maintained by myself) Born July 08

Advantage TourGuide

neoneo wrote:

so what is the advantage of using a tourguide as a rest stop poi instead of just using it as a poi file???

i only want to be alerted about the rest stops coming up ahead of me. what option is better for that?

Welcome to the site neoneo .Using TourGuide in a file name will give you a radius alert instead of the along the road of travel.If you have alerts set up using manual mode for poiloader or built in alerts using gpx files and you have not selected go.The alerts will not sound unless in most cases you are traveling on the same road and the coordinates are no more then 50 to 75 ft off the road of travel.Using TourGuide in the file name changes that.You get a radius alert and along with poiloader or gpx files you can expand the radius to get the alert.For example most Cracker Barrels are located off the interstate and you will not be alerted using the along the road alert unless you selected go.Put TourGuide in the file name and set radius to 2 to 3 miles and you will be alerted from interstate in navigation mode for most locations..

--
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.

thanks for taking the time

thanks for taking the time for explanation.

@neoneo

I use gpx files for all my custom poi files that I set up for alerts except the redlight and speed cameras since they have the alerts built in .Using the gpx files I can build the alerts into the other files and run poiloader in the manual mode.See http://www.poi-factory.com/node/28521 .

--
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.

Manual vs express

I use manual for offbeat attractions and set if for 5 miles, since some are not near interstates. I also give a greater distance for auto dealerships.

.

dobs108 wrote:

Thanks for the encouragement. Creating an FAQ is a good idea.

dobs108 smile

Dobs108, thank YOU and Miss POI. The FAQ is excellent.

thank you

charlesd45 wrote:

I use gpx files for all my custom poi files that I set up for alerts except the redlight and speed cameras since they have the alerts built in .Using the gpx files I can build the alerts into the other files and run poiloader in the manual mode.See http://www.poi-factory.com/node/28521 .

thank you

speed camera files

just got confused with the speed camera poi file. which alert option should be set for this? am i specifying the distance in feet or nothing at all and just leaving it alone?

I use poi loader in manual

I use poi loader in manual mode because I have differing settings for my POI's...

The Speed and Redlight one's come with presets that I keep as is....

All poi's except Cracker Barrel and Restarea's use 2000 feet settings.... Cracker Barrel and Restarea's I've set at 12000 feet. Furthermore, I've set Crakerbarel as a TourGuide.

Jan

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

Speed camera files

neoneo wrote:

just got confused with the speed camera poi file. which alert option should be set for this? am i specifying the distance in feet or nothing at all and just leaving it alone?

If you run POI Loader in manual, choose speed alert and leave the default speed as zero. The file has a custom speed for each speed camera location which overrides the default zero on being loaded into the GPS. If you choose the speed alert there is no entry for distance in feet.

dobs108 smile

THANKS!

I didn't know that...

Slight difference

dobs108 wrote:

If you run POI Loader in manual, choose speed alert and leave the default speed as zero. The file has a custom speed for each speed camera location which overrides the default zero on being loaded into the GPS. If you choose the speed alert there is no entry for distance in feet.

dobs108 smile

Using the method you describe (for speed cameras.csv) I find that I get a .2 mi alert with no speed shown (viewing the poi on the unit under Custom Pois) for all of the pois. When I append @ plus the speed number to each poi name however, I get an alert that (when viewed as above) shows speed and an alert of .1 mi for each 10mph of speed.

Subtle difference, but your method corresponds with the PoiLoader help file regarding 0 speed/.25 mi proximity (always alert). If I'm not mistaken, a varying proximity for each poi as well as a speed threshold needs to have @xx (where xx is the speed) in each poi name regardless of using either Manual or Express mode.

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

You are right!

JD4x4 wrote:

Using the method you describe (for speed cameras.csv) I find that I get a .2 mi alert with no speed shown (viewing the poi on the unit under Custom Pois) for all of the pois. When I append @ plus the speed number to each poi name however, I get an alert that (when viewed as above) shows speed and an alert of .1 mi for each 10mph of speed.

Subtle difference, but your method corresponds with the PoiLoader help file regarding 0 speed/.25 mi proximity (always alert). If I'm not mistaken, a varying proximity for each poi as well as a speed threshold needs to have @xx (where xx is the speed) in each poi name regardless of using either Manual or Express mode.

You are right - it would be an improvement to have varying alert distances for speed cameras.

I am advising a new member who may be loading POIs for the first time, and my goal is to make it as simple as possible for him to succeed in loading the speed camera file, as supplied by POI Factory, and make it work. As a result of succeeding in this, I hope he will gain the confidence to make improvements such as you describe.

Among the hundreds of thousands who read these posts, there is a need that ranges from the most basic to the highly technical.

dobs108 wink

Same

Pointing out that the current format of the speed number in the poi name in Speed-Cameras.csv has no effect, and running PoiLoader on the file in express mode produces the same effect as running it in manual mode with Speed Alert/0 mph default.

Besides, I'm old school & I'd rather have all of the facts even when I'm asking someone for help.

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

I've updated the format,

I've updated the format, adding an "@" before the speed as recommended. This change will be included in the file we publish this Wednesday.

JM

Very cool

JM wrote:

I've updated the format, adding an "@" before the speed as recommended. This change will be included in the file we publish this Wednesday.

JM

Thank you Jon and also to those that have made the request.

Miss POI

Thanks for this thread

This is one very insightful thread. Learnt a lot of new things by reading this thread. Thanks to all those who contributed to this thread!

Correcting My Error!

dobs108 wrote:

If you run POI Loader in manual, choose speed alert and leave the default speed as zero. The file has a custom speed for each speed camera location which overrides the default zero on being loaded into the GPS. If you choose the speed alert there is no entry for distance in feet.

TITNTUFF wrote:

Thanks! I didn't know that...

JD4x4 wrote:

Using the method you describe (for speed cameras.csv) I find that I get a .2 mi alert with no speed shown (viewing the poi on the unit under Custom Pois) for all of the pois. When I append @ plus the speed number to each poi name however, I get an alert that (when viewed as above) shows speed and an alert of .1 mi for each 10mph of speed.

Subtle difference, but your method corresponds with the PoiLoader help file regarding 0 speed/.25 mi proximity (always alert). If I'm not mistaken, a varying proximity for each poi as well as a speed threshold needs to have @xx (where xx is the speed) in each poi name regardless of using either Manual or Express mode.

Thanks for your support, TITNTUFF, but I was wrong! JD4x4 discovered my error and JM and miss poi decided to make me right by changing the POI coding to do what I had only imagined possible! So my advice holds true beginning Wednesday.

dobs108 surprised

Thanks for this thread

jakas wrote:

This is one very insightful thread. Learnt a lot of new things by reading this thread. Thanks to all those who contributed to this thread!

I agree and I also have learned a lot from this thread!

dobs108 grin

Updated the format for Speed Cameras

JM wrote:

I've updated the format, adding an "@" before the speed as recommended. This change will be included in the file we publish this Wednesday.

JM

Thanks, JM and miss poi for the improvement!

dobs108 smile

Kudos to dobs108

dobs108 wrote:

Thanks for your support, TITNTUFF, but I was wrong! dobs108 surprised

Not many of us are willing to "fess up" when we are wrong. Those that do are the ones that I respect and listen to.

Ditto on the thanks

Ditto on the thanks to JM & Miss Poi for changing the file format (even if it makes my Excel programming obsolete surprised ).

I only discovered the difference myself after looking closely at a compiled poi on my unit after all these months. An alert was an alert, & it seemed to work so I never bothered to look before.

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

No problem.

dobs108 wrote:
dobs108 wrote:

If you run POI Loader in manual, choose speed alert and leave the default speed as zero. The file has a custom speed for each speed camera location which overrides the default zero on being loaded into the GPS. If you choose the speed alert there is no entry for distance in feet.

TITNTUFF wrote:

Thanks! I didn't know that...

JD4x4 wrote:

Using the method you describe (for speed cameras.csv) I find that I get a .2 mi alert with no speed shown (viewing the poi on the unit under Custom Pois) for all of the pois. When I append @ plus the speed number to each poi name however, I get an alert that (when viewed as above) shows speed and an alert of .1 mi for each 10mph of speed.

Subtle difference, but your method corresponds with the PoiLoader help file regarding 0 speed/.25 mi proximity (always alert). If I'm not mistaken, a varying proximity for each poi as well as a speed threshold needs to have @xx (where xx is the speed) in each poi name regardless of using either Manual or Express mode.

Thanks for your support, TITNTUFF, but I was wrong! JD4x4 discovered my error and JM and miss poi decided to make me right by changing the POI coding to do what I had only imagined possible! So my advice holds true beginning Wednesday.

dobs108 surprised

It's a learning process, and we all make a misstep occasionally.
There's still a LOT to learn.