Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
The flexibility and capability depend more on the quality of the original data than the form it is encoded in. While gpx is needed if you want to do blue-tooth dialing, and if the data included telephone numbers, I've seen poorly constructed gpx files and well constructed csv files. If not using bluetooth dialing I see no reason to prefer one format over the other.
I have successfully dialed many times with my bluetooth from csv POI files.
-- "As life runs on, the road grows strange with faces new - and near the end. The milestones into headstones change, Neath every one a friend." - James Russell Lowell
Garmin StreetPilot C330, Garmin NUVI 765T, Garmin DriveSmart 60LMT
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
When converted to a gpi file using POI Loader they are reduced in size when loaded onto your device. For example - I have a gpx version of the Starbucks POI database that is 9.7MB. When uploaded to my 1690 as a TourGuide gpi file, it is only 3MB.
attaching unique pictures/sound and/or TourGuide files to individual pois
attaching unique proximity alerts to individual pois
importing pois into Favorites directly
And if you edit the gpx in a spreadsheet, there is easier sorting/deleting on City, State, Zip, etc (assuming the gpx has those individual fields populated).
-- It's about the Line-
If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
The flexibility and capability depend more on the quality of the original data than the form it is encoded in. While gpx is needed if you want to do blue-tooth dialing, and if the data included telephone numbers, I've seen poorly constructed gpx files and well constructed csv files. If not using bluetooth dialing I see no reason to prefer one format over the other.
No, you've got this one wrong. You can't set both speed and proximity alarms using a CSV file but you can with a GPX format file. You can't format the data presentation using a CSV file but you can using GPX. As you mentioned, Bluetooth is another difference. These differences are much more than simple data quality.
What you want the file to do is the important thing.
Frovingslosh wrote:
The flexibility and capability depend more on the quality of the original data than the form it is encoded in. While gpx is needed if you want to do blue-tooth dialing, and if the data included telephone numbers, I've seen poorly constructed gpx files and well constructed csv files. If not using bluetooth dialing I see no reason to prefer one format over the other.
I disagree with this opinion.
It has nothing to do with the quality of the information in the file, but what you want the file to do for you. For example, if all you need is a simple list of locations, such as the red light and speed cameras, then CSV is your ticket, even though GPX can build the speed alerts into the file. If however you want locations that have comments, multi-paragraph descriptions, addresses and other contact information, GPX is your ticket, because from my experience, while it is possible to create a CSV file that has all the information a CSV file can have, it's far easier to make a mistake in creating a large CSV file.
-- "Anyone who is capable of getting themselves made President should on no account be allowed to do the job."
--Douglas Adams
Seems like it just comes down to personal preference. Either one would get the job done for most of us.
If all you're interested in is a location and "one alert fits all" like redlight cameras or railroad crossings then CSV file is the way to go. If you need extra information or both individually settable proximity and speed alerts then GPX if the format you need. Each format has it's own advantages and disadvantages, you need to decide which is best for your uses.
In my area, new red light cameras are being installed every week. For files that are updated weekly like Speed and Red Light Cameras, it pays to use these .csv files just as they come without converting them to .gpx and adding custom alert distances. But POI Loader has to be run in manual to make sure the speed and distance settings are what you want.
Yes.You can use csv or gpx.
Yes.You can use csv or gpx.
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.
I prefer gpx
can gpx poi work on the garmin
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
the data is the important thing
can gpx poi work on the garmin
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
The flexibility and capability depend more on the quality of the original data than the form it is encoded in. While gpx is needed if you want to do blue-tooth dialing, and if the data included telephone numbers, I've seen poorly constructed gpx files and well constructed csv files. If not using bluetooth dialing I see no reason to prefer one format over the other.
Agree
the data is the important thing
You are obviously correct about the data quality.
However, when I have a good quality file, I like to use EPE to convert it into .gpx (if not already in that format)
Then, when I need some flexibility, I am ready.
Only GPX can be used with MapSource
csv files must be converted into gpx files if you want to plan routes in MapSource with the POIs. MapSource only deals with gpx format.
Zumo 550 & Zumo 665 My alarm clock is sunshine on chrome.
I beg to differ
I have successfully dialed many times with my bluetooth from csv POI files.
"As life runs on, the road grows strange with faces new - and near the end. The milestones into headstones change, Neath every one a friend." - James Russell Lowell Garmin StreetPilot C330, Garmin NUVI 765T, Garmin DriveSmart 60LMT
When converted to a gpi. . .
can gpx poi work on the garmin
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
When converted to a gpi file using POI Loader they are reduced in size when loaded onto your device. For example - I have a gpx version of the Starbucks POI database that is 9.7MB. When uploaded to my 1690 as a TourGuide gpi file, it is only 3MB.
JRoz -- DriveSmart 55 & Traffic
More than Dialing
.. If not using bluetooth dialing I see no reason to prefer one format over the other.
In addition to the MapSource & BaseCamp usage already mentioned, there are quite a few more reasons I prefer to use gpx.
And if you edit the gpx in a spreadsheet, there is easier sorting/deleting on City, State, Zip, etc (assuming the gpx has those individual fields populated).
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.
Data Quality?
can gpx poi work on the garmin
Although .gpx files in raw form are larger in size, when loaded to the GPS they take only slightly more space. Given the flexibility and capability they offer, I prefer them.
The flexibility and capability depend more on the quality of the original data than the form it is encoded in. While gpx is needed if you want to do blue-tooth dialing, and if the data included telephone numbers, I've seen poorly constructed gpx files and well constructed csv files. If not using bluetooth dialing I see no reason to prefer one format over the other.
No, you've got this one wrong. You can't set both speed and proximity alarms using a CSV file but you can with a GPX format file. You can't format the data presentation using a CSV file but you can using GPX. As you mentioned, Bluetooth is another difference. These differences are much more than simple data quality.
What you want the file to do is the important thing.
The flexibility and capability depend more on the quality of the original data than the form it is encoded in. While gpx is needed if you want to do blue-tooth dialing, and if the data included telephone numbers, I've seen poorly constructed gpx files and well constructed csv files. If not using bluetooth dialing I see no reason to prefer one format over the other.
I disagree with this opinion.
It has nothing to do with the quality of the information in the file, but what you want the file to do for you. For example, if all you need is a simple list of locations, such as the red light and speed cameras, then CSV is your ticket, even though GPX can build the speed alerts into the file. If however you want locations that have comments, multi-paragraph descriptions, addresses and other contact information, GPX is your ticket, because from my experience, while it is possible to create a CSV file that has all the information a CSV file can have, it's far easier to make a mistake in creating a large CSV file.
"Anyone who is capable of getting themselves made President should on no account be allowed to do the job." --Douglas Adams
preference
Seems like it just comes down to personal preference. Either one would get the job done for most of us.
Good enough for me!
Seems like it just comes down to personal preference. Either one would get the job done for most of us.
If all you're interested in is a location and "one alert fits all" like redlight cameras or railroad crossings then CSV file is the way to go. If you need extra information or both individually settable proximity and speed alerts then GPX if the format you need. Each format has it's own advantages and disadvantages, you need to decide which is best for your uses.
Files updated weekly
In my area, new red light cameras are being installed every week. For files that are updated weekly like Speed and Red Light Cameras, it pays to use these .csv files just as they come without converting them to .gpx and adding custom alert distances. But POI Loader has to be run in manual to make sure the speed and distance settings are what you want.
dobs108