Suggestion for POI Contributors regarding changes

 

When you update your POI files please remember to update the POI's LOGBOOK so the change history can be noted. OR alternatively, please note the change within the text of the POI file node.

This makes it easy for everyone to decide if the new POI is worthy of a download. If just one minor change was made I often don't download the file.

My GPS is a pain when I upload an updated file to it. Every and all custom POI's lose their "Warn when near" POI settings, even if I upload one updated POI. I've got about 20 custom POI's so the addition of just one updated upload affects all of them, and it's very time consuming to then go in and reset all the parameters. So often times I do not update if there is a minor change to a POI file. I'm assuming I'm not the only one with this dilemma.

This is why it is good to note the changes of your POI file when indeed you make a change. Bottom line: there is power in knowledge.

Thanks.

--
Amazing GPS: I once was lost but now am found.

Change Log

I have a just a few modified custom poi. All of those contributors do keep up with the change log.

Quote:

My GPS is a pain when I upload an updated file to it. Every and all custom POI's lose their "Warn when near" POI settings, even if I upload one updated POI. I've got about 20 custom POI's so the addition of just one updated upload affects all of them, and it's very time consuming to then go in and reset all the parameters.

I don't understand how one file affects all of your other files. Mine do not.

--
1490LMT 1450LMT 295w

not all

spokybob wrote:

I have a just a few modified custom poi. All of those contributors do keep up with the change log.
I don't understand how one file affects all of your other files. Mine do not.

Not all maintainers use the change log when updating their files. Some just continue text to the end of the description which makes it cumbersome when you have to scroll through all the description text to find out they corrected a location.

If you convert the CSV files to GPX you can add the alert information as part of the file which means you don't need to do a manual update with POI Loader and reenter all the proximity or speed information.

--
Illiterate? Write for free help.

Reset Prox Alert

spokybob wrote:

I have a just a few modified custom poi. All of those contributors do keep up with the change log.

Quote:

My GPS is a pain when I upload an updated file to it. Every and all custom POI's lose their "Warn when near" POI settings, even if I upload one updated POI. I've got about 20 custom POI's so the addition of just one updated upload affects all of them, and it's very time consuming to then go in and reset all the parameters.

I don't understand how one file affects all of your other files. Mine do not.

I presume you're using Garmin. If not this is likely all irrelevant. "Warn when near" does not sound like a Garmin phrase, but might be for some models.

If you have "Warn when near" (Proximity Alert) and you use POI Loader to set the Prox Alert Distance, then you must reset the Prox Alert for each and every file that uses them.

BoxCar is right about converting csv to gpx. I do that and then use Extra POI Editor and go to Edit-Replace Field. Scroll down to Proximity and type in an appropriate Prox Distance. Then click "Replace All". That will set the prox distance and you will be able to load the file as you would any other file, without having to set individual Prox Distance.

I also agree with spokybob. Neither my NUVI2555, nor my NUVI 350 acted like that. No other files are affected.

--
NUVI2555LMT, NUVI350

I believe Vito uses the truck TomTom

TomTom is .csv only. sad

--
Striving to make the NYC Metro area project the best.

To clarify...

Yes I'm saying my TomTom behaves this way when uploading an updated POI file. All the alerts have to be reset for distance, type, audible sound, and whether the POI is on the route or not. That's 4 settings for just one "proximity" warning. Imagine the time it takes when having to reset 20 POI's.

It takes less than 30 seconds to update the Logbook. For everyone's benefit.

Just a suggestion, that's all.

--
Amazing GPS: I once was lost but now am found.

tomtom

camerabob wrote:

TomTom is .csv only. sad

is ov2 only

I stand corrected.

At least I knew it wasn't .gpx. grin

--
Striving to make the NYC Metro area project the best.

I'd say

you're both right. When uploading a TomTom POI, we must upload in .csv However, the actual file that the TT uses is .ov2

--
Amazing GPS: I once was lost but now am found.

i'm curious

Vito wrote:

you're both right. When uploading a TomTom POI, we must upload in .csv However, the actual file that the TT uses is .ov2

I'm curious if any TT users have tried adding alert information to a GPX file using EPE and then outputting the file in OV2 format. I wonder if the proximity information would be saved in the OV2. I don't have a TT, so I can't test.

--
Illiterate? Write for free help.