Which File Format, please?

I didn't have a 350, but they did some funny formatting and would display csv files incorrectly (if I remember correctly). I think they were the first nuvis out. So folks made a special formatted csv just for those units. A regular csv or gpx will work fine. The line breaks are nice as they will show in the description area properly.

daniel

All four formats will work in the nuvi 350; the difference is if the POI contain linebreaks.

The nuvi350/360 do not display standard linebreaks correctly. Linebreaks in field 4 require <br> instead of the standard linebreaks. This was the original reason for creating POI Verifier.

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

RT

RT - is there a post where you don't promote your software! I'm just messing with you. From the reviews on this site it appears your software has a ton of useful features.

However, the OP stated he has a 650, not a 350.

Speed3 - you can use all four formats, but GPX or Garmin CSV should work best on your 650.

Other nuvis have the linebreak problem. I tried to make a list of which ones do (created by user input), but not enough contributed to make the list complete. I know some nuvi 2xx models have the problem; but until someone says the other nuvis don't, I'm assuming they do.

If you call it 'promoting' when I gave the above link to a page where I posted a procedure on "how to use Excel to accomplish this conversion without using POI Verifier", what are we going to call it when I really do promote it?

RT

OK, and thank you all for your input.

I have been using the CSV format and they seem to work well, so I will stick with that format.

I was surprised to double click on one and have it open in Excel.

It would seem that you could create your own POI using excel if you followed this format, no? I guess I'd use Google to get the actual geographical coordinates, no?

Thanks again,
Speed3

Yes. You can also open CSV files in Notepad (or any text editor).

Yes you can use excel to make your custom pois and along with Google or Gpsvisualizer to get the coordinates.

Welcome to the POI Factory, Speed3!

I use all except the 350/360 format with our 680 or 650. My preference is GPX (phone numbers work with Bluetooth) then Garmin CSV- regular line breaks (if available), then Garmin CSV - no line breaks

The regular line breaks format will display multi-line address fields properly on a nuvi 6xx. The Nuvi 350/360 format uses <br> for line breaks which doesn't display properly on nuvi 6xx units.

Thank you.

Let's give it another try. Would anybody be interested in having a list of which nuvis require standard linebreaks and which require <br>?

If so, download a POI with <br> linebreaks in the 'Comment' field (field 4) and email the results to me via my contact link; or you can just post it here. I'll try to keep the list current. One such csv POI that contains <br> linebreaks is at:
http://www.poi-factory.com/node/19698

Using a POI that contains standard linebreaks isn't conclusive as what one might think is a linebreak is actually word wrap.

Which linebreaks are required:
nuvi 255--<br>
nuvi 2xx--not complete, but appears most all require <br>
nuvi 350--<br>
nuvi 360--<br>
nuvi 6xx--Standard

Thanks.

RT

RT,
Why don't you create a single test file with 3 locations having Titles of "Standard", "350", and "None". If the same long detailed info was formatted in 3 different ways, owners could tell you which format(s) display correctly on each unit. Otherwise, somebody is going to look at a location with a single-word description and report that that format displays correctly on the xxx model.

I may have to do that, but I'm hoping that when one uses that file and their GPS requires standard, it will display some extra characters like br. Want to make it as simple as possible. I see you have a 660. Could you try that and report what you see? Sure would appreciate it.

Thanks.
RT

PS That's what I did last time;
http://www.poi-factory.com/node/17422
but it may have gotten too complicated and time-consuming to download and try multiple files. Also, they may have been hesitant to download from a strange website ... this way it comes from POI-Factory.

nuvi 250 (newer hardware, multiple vias, micro-SD card slot, version 4.2 firmware)

Did the test with one file with both types of long lines in it. Lines with "BR" in them display as if they are multiple lines (the desired result). A quoted string with multiple real line brakes in it loads properly, but only line 1 displays.

BR is required for my 250. Tried putting the string in angle brackets here, but that confuses this website! Not sure how you others are doing it, does lower case slip it through or is it a different trick?

Is there a stated limit to the number of lines contained in a CSV file? I thought that I had read somewhere that it was a 3 line limit, but my 250 is displaying 4 lines of information just fine. If there is a different limit to number of lines for different models this would be handy information to collect also.

I see you have a 660. Could you try that and report what you see? Sure would appreciate it.

& l t ; b r & g t ; without the spaces between.

Thank you.

So, to test:
Try the file above. If you get <br> displayed, you're in luck and can use standard linebreaks. If it IS NOT displayed, then you require the <br> linebreaks.

Thanks ... so the nuvi 250 also require the <br>

Thanks all.

RT

Just copy and paste the following:
&lt;br&gt;

Now, to display this code here as text is another matter.

You may be interested in the link:
http://www.poi-factory.com/node/7347

RT

The updated list and the procedure for checking your nuvi linebreak requirement has been moved to:
http://www.poi-factory.com/node/19757

This was done so the list can easily be updated.

Thanks.

RT