Formatting of POI file.
Mon, 03/24/2008 - 12:54pm
 16 years
|
I created a poi file and decided to use the multi-line format for the comments (using quotes). I have a Nuvi 350 on which it looks fine, but does this cause problems for other models as far as compatibility. In other words, should I not put breaks in the file if I plan to upload my file for other to use?
my take
When I create files I do it for my 260 GPSr, before uploading it is tested in my unit and then I leave it for others that may have different formatting needs to do the fixing they require.
Garmin 38 - Magellan Gold - Garmin Yellow eTrex - Nuvi 260 - Nuvi 2460LMT - Google Nexus 7 - Toyota Entune NAV
Linebreaks revisited
I created a poi file and decided to use the multi-line format for the comments (using quotes). I have a Nuvi 350 on which it looks fine, but does this cause problems for other models as far as compatibility. In other words, should I not put breaks in the file if I plan to upload my file for other to use?
If you're talking 'linebreaks', the nuvi 350/360 requires a <br> for a linebreak instead of the standard linebreak. Using this form of linebreak on other units will not display correctly. If you want to use linebreaks, I'd suggest using standard linebreaks and let the user convert to <br> via POI Verifier or some other method.
RT
"Internet: As Yogi Berra would say, "Don't believe 90% of what you read, and verify the other half."
Recommended CVS File Format
Is there a doc that lays out the required CVS file format, for a POI file. I want to create some custom CVS files for conversion to OV2 format? Thanks for any input or help with this.
POI Loader
Is there a doc that lays out the required CVS file format, for a POI file. I want to create some custom CVS files for conversion to OV2 format? Thanks for any input or help with this.
The 'Help' section of Garmin's POI Loader is a good place to start. Also has info on setting alerts.
RT
"Internet: As Yogi Berra would say, "Don't believe 90% of what you read, and verify the other half."
That's strange
If you're talking 'linebreaks', the nuvi 350/360 requires a <br> for a linebreak instead of the standard linebreak. Using this form of linebreak on other units will not display correctly. If you want to use linebreaks, I'd suggest using standard linebreaks and let the user convert to <br> via POI Verifier or some other method.
RT
I didn't use the tag, I just put the entire address in quotes and inserted a new line before the City, State, Zip to format the address correctly. Am I missing something, or is the "br" optional on the 350/360? If so then like you said using the Quote method is fine for other models?
nuvi 350/360 linebreaks
Am I missing something, or is the "br" optional on the 350/360 as these units have a linebreak display problem? If so then like you said using the Quote method is fine for other models?
The <br> is not optional for a linebreak in field 4 of the nuvi 350/360, but a requirement as these units have had a display problem for over a year. Standard linebreaks in field 4 (comment field) will not force a linebreak (don't confuse forced linebreaks with the break at the end of the line due to character overrun). See: http://www.poi-factory.com/node/1486
RT
"Internet: As Yogi Berra would say, "Don't believe 90% of what you read, and verify the other half."
Thanks for the clarification.
The <br> is not optional for a linebreak in field 4 of the nuvi 350/360, but a requirement as these units have had a display problem for over a year. Standard linebreaks in field 4 (comment field) will not force a linebreak (don't confuse forced linebreaks with the break at the end of the line due to character overrun). See: http://www.poi-factory.com/node/1486
RT
Yep, you are right. I went back and looked at a few entries and it ignored the line break. It just looked fine on a few of the ones I tried earlier due to text wrapping.
Okay...so exluding the problematic models are the normal breaks okay, or should I just leave the formatting up to people who use the files?
.
My personal preference is to have the files without the formatting.
Put in the standard linebreaks
Okay...so exluding the problematic models are the normal breaks okay, or should I just leave the formatting up to people who use the files?
I'd suggest including the standard linebreaks. Reason being ... there are programs that can automatically remove them or convert them to <br> (POI Verifier and others); but there are no programs that know exactly where you want them to automatically insert them!
"Internet: As Yogi Berra would say, "Don't believe 90% of what you read, and verify the other half."
Thank you
Thanks to you both for the input.