<cmt> </cmt> went and came back

 

I update the Speed Cameras and Red Light Cameras POI's weekly. In the past, after converting the .csv files to .gpx files using EPE 5.93, there was always a blank comment line ("cmt /cmt") between the "name" and "extensions" fields. Until last week, that is. All of a sudden last week, those lines weren't there anymore. They were gone. Consequently every entry was one line shorter because it's cmt line wasn't there. And that was okay.
Today when I went to update those two files, EPE wouldn't start, so instead of issuing the "EPE -reset" command I downloaded the newest version of EPE, 5.96. When I updated the Speed and Red Light POI's after the download, the lines were back. I guess my question isn't so much why are those lines back, but why did they go away in the first place? And if truth be told, I'd just as soon NOT have them in every entry just to save the space.

Phil

--
"No misfortune is so bad that whining about it won't make it worse."

what options are set

What options do you have set in the M-Column Options? I just looked at several of my GPX files and I don't see the empty comment field in the files directly loaded as CSV to which a proximity was added using ALT-R and then saved as GPX.

I have two profiles stored under M-Column, one with just the four CSV fields and one that is expanded to included things such as comments.

--
ɐ‾nsǝɹ Just one click away from the end of the Internet

I can't see why you'd go to

I can't see why you'd go to the trouble of converting the files from CSV to GPX, especially since one of your stated goals is "saving space".

Using only the Speed and RLC files from March 6th, the GPI file created by POI Loader from CSV files is 659 kb and from the GPX files is 690 kb, so no space saved.

--
I never get lost, but I do explore new territory every now and then.

I cannot figure why you convert them

KenSny wrote:

I can't see why you'd go to the trouble of converting the files from CSV to GPX, especially since one of your stated goals is "saving space".

Maybe the OP could explain the reason that he bothers to convert the CSV files to GPX format.

--
Garmin Drive Smart 55 - Samsung Note 10 Smartphone with Google Maps & HERE Apps

simple

KenSny wrote:

I can't see why you'd go to the trouble of converting the files from CSV to GPX, especially since one of your stated goals is "saving space".

Using only the Speed and RLC files from March 6th, the GPI file created by POI Loader from CSV files is 659 kb and from the GPX files is 690 kb, so no space saved.

Converting from CSV to GPX allows both proximity distance and speeds to be assigned as elements of the POI. POI Loader defaults to a quarter mile or 400 meters for distance when one of the keywords is used. Otherwise, you have to assign a distance or a speed to the file every time you load files.

Some files I don't download and update some files I have alerts set for with every update, I have them converted to GPX and an alert distance assigned. I can also use Bluetooth to dial the numbers from my GPS if desired - all things that can't be done with a CSV.

As I don't have to remember what I entered for proximity values every time POI Loader is run, I can use the Auto mode and load all my POI and disconnect my unit within 2 minutes of starting POI Loader.

--
Illiterate? Write for free help.

That's why

Box Car wrote:

Converting from CSV to GPX allows both proximity distance and speeds to be assigned as elements of the POI. POI Loader defaults to a quarter mile or 400 meters for distance when one of the keywords is used. Otherwise, you have to assign a distance or a speed to the file every time you load files...
...As I don't have to remember what I entered for proximity values every time POI Loader is run, I can use the Auto mode and load all my POI and disconnect my unit within 2 minutes of starting POI Loader.

I convert .csv to .gpx for that reason. For those POI's where proximity or speed isn't important, I leave as .csv's.

--
"No misfortune is so bad that whining about it won't make it worse."

Check the EPE setting

"Remove empty comment field in GPX output" under preferences.

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

yes

camerabob wrote:

"Remove empty comment field in GPX output" under preferences.

That would do it as well.

--
ɐ‾nsǝɹ Just one click away from the end of the Internet

That did it.

camerabob wrote:

"Remove empty comment field in GPX output" under preferences.

Thanks, cb, that took care of the empty comment lines.

Phil

--
"No misfortune is so bad that whining about it won't make it worse."