CSV docs

 

Hey I have a crossover that I really love. Has anyone else had trouble with poi files that have several comas in them? I put them in excel and find 3 or 4 comas in one cell. Of course when I put the pois in the Magellan converter program it creates a new cell for each coma and then to go through each poi and remove them would take several hours or more. Any suggestions on how to remove them without going line by line?

Use ASAP Utilities see

Use ASAP Utilities see http://www.asap-utilities.com/download-asap-utilities.php

I also use to replace all the extra end of line characters to spaces before converting to.gpx files. These characters cause the POIEdit program to flag an error.

After install pick ASAP Utilities --> 8. Text --> 14. Advanced Character Replacement and then check the box next to the comma. Then put a space in he replace field.

--
eTrex Touch 35, Nuvi 1350LMT, Nuvi 350, Nuvi 260, Garmin GPS III, Basecamp

Find and Replace

I have not tried this, but you could copy the column of data from excel into word and use a find replace function to get rid of all your commas. You may also be able to find/make a macro to do the same thing in excel.

Daniel

--
Garmin StreetPilot c580 & Nuvi 760 - Member 32160 - Traveling in Kansas

Should be easy....

palsditch wrote:

I put them in excel and find 3 or 4 comas in one cell.

This is because the Magellan loader program does not really conform to the CSV standard. If you look at the CSV with a text editor (Notepad) you should see that the offending field is enclosed by quotes ".....". The loader ignores that.

In Excel, you should be able to select (hi-light)the offending column of cells and do a search and replace. Search for comma, replace with space.

--
Magellan Maestro 4250// MIO C310X

Comas -- CSV

I just found out that, after many failed load attempts, the Garmin Loader doesn't like comas in fields either. Tried to load four Custom POI from the site and got a shut down because they each had a number comas in the address fields.

I removed the offending comas using Excel "replace".

Open the subject file see if it has comas, go the edit menu, select Replace and in the window that opens - put in a coma for the program to find and put in a hash mark for the program to replace. Press "replace all" and the comas are gone.

For those wondering Excel separates the information in each field by using a comma (compatible with CSV ) if you put a coma in the address contained in the address field then the Garmin would want to split that field at the extra coma instead it just fails as an error.

not quite

Blaine Benson wrote:

I just found out that, after many failed load attempts, the Garmin Loader doesn't like comas in fields either. Tried to load four Custom POI from the site and got a shut down because they each had a number comas in the address fields.

I removed the offending comas using Excel "replace".

Not quite. Excel strips quotes from fields that contain embedded special characters. Try looking at the file with a text editor and you'll find the fields having special characters like commas encased by quotes.

--
Illiterate? Write for free help.

names have meaning

Blaine Benson wrote:

I just found out that, after many failed load attempts, .....

I removed the offending comas using Excel "replace".

CSV files are NOT Excel files, they are just text files that Excel happens to be able to read and write. If you knew what CSV stood for then you would (hopefully) understand what the problem was. I expect that a quick Google search would explain it. And using quotes is the preferred fix.