Formatting
Tue, 10/21/2008 - 6:47pm
15 years
|
I have created simple, multi-lined poi files using just my basic text editor. I have had no problems.
The other day I placed one of my poi files that I was having trouble with into my spreadsheet program to see if I could find my error.
When I saved my work and later re-opened the file in my text-editor all of my cords went from ##.###### to ##.##. I have tried going back into my spreadsheet and changing the format, but can't figure out where my data went!
Did you save
Did you save the POI file from the spreadsheet application as a .csv file ?????????
MrKenFL- "Money can't buy you happiness .. But it does bring you a more pleasant form of misery." NUVI 260, Nuvi 1490LMT & Nuvi 2595LMT all with 2014.4 maps !
Excel
I believe what's happening is that Excel is converting your coordinates into scientific format or rounding it off to 2 decimal places. You can put a single quote at the begining of the coordinate, so that excel will treat it as text rather than as numbers. '74.012345678
nuvi 2460LMT
Previous Discussion
See http://www.poi-factory.com/node/11495
Nuvi 660 -- and not upgrading it or maps until Garmin fixes long-standing bugs/problems, and get maps to where they are much more current, AND corrected on a more timely basis when advised of mistakes.
I'll Try It!
Thanks for the input!
I do use openoffice and I was saving it as a ".csv" so it must be something with automatically switching to two decimals.
Now, I will begin to gather all that data ALL over again!
Thanks for the input!
Aaron Grames
Check the raw file
Have you looked at the resulting csv file in something like Notepad? It may be that openoffice is only "displaying" 2 decimal places, but the underlying data is still there. Excel does the same thing for decimal data.
.
Have you looked at the resulting csv file in something like Notepad? It may be that openoffice is only "displaying" 2 decimal places, but the underlying data is still there. Excel does the same thing for decimal data.
I'm guessing that you didn't read the above-referenced thread. When saving as a csv file, it does NOT save the underlying data. The fix is to change the global display preference for number of decimal places.
Nuvi 660 -- and not upgrading it or maps until Garmin fixes long-standing bugs/problems, and get maps to where they are much more current, AND corrected on a more timely basis when advised of mistakes.