| -
I think this is an artifact from the way the waypoint is entered into
ExpertGPS. You can get MapSource to not "renumber" if you enter the
waypoint name when it is entered into ExpertGPS. Right now, then
<name> tag in the XML is missing in the GPX files for MOGA. I
noticed this when I was playing with the waypoints handed out in the
past years and trying to get it loaded into GSAK. ExpertGPS defaults
the waypoint name to be whatever you put into the <label> tag.
You can see this is you bring up the Edit dialog for a waypoint. The
<< button will put the actual value into the Waypoint field,
which turns into the <name> tag when the GPX file is saved. My guess is that the CO needs the <name> tag to do its thing, and because of the way it was entered in ExpertGPS, the tag is never generated. That tag will always be in the GPX file that comes from GC.com, and will also always be in one generated by MapSource as well. That may be the only problem, although it may not be. I am thinking that the CO is programmed with the assumption that a waypoint is not going to exist without a name, and that is the core of the problem. There may be other similar assumptions being made, but we won't know unless we try. Jim, if you would like to experiment a little, I can edit the waypoints on one of the MOGA files so that they all have a <name> tag, and you can then try to see if that is all that is needed to make it work. If so, then all you need to do is alter the procedure for entering the waypoints into ExpertGPS, and you are done with it. If not, then even using the same procedure for entry, the file can be brought into MapSource and it will not be "renumbered" because the name is already there and doesn't need to be generated, and the file can be saved from there, which should allow it to be loaded into the CO. Let me know if you are interested in experimenting with this. Might not be a bad idea to straighten it out before the issue is forgotten. Michael Griffin wrote: **************************************** For List Info or To make _ANY_ changes, including unsubscribing from this list, click -----> //www.freelists.org/list/geocaching Missouri Caches Scheduled to be Archived http://tinyurl.com/87cqw- Nice of you to volunteer. However, the GPX file that expertGPS creates is not recognized by the Colorado. This is a problem with the Colorado and not the file. GC.com has their own XML they do and it, along with Mapsource, are the only GPX files that it works with. We will need to see if we can get a GPX generated from GC.com on caches that have not been activated yet. If we can't, we will hand you the sheet and you can manually enter them. Either that, or Garmin needs to correct the GPX load to accept "standard" GPX files from any software besides their own and GC.com. The problem we have with using Mapsource is it renumbers all the caches. I have no idea why, it just does. Mike Griffin -----Original Message----- From: geocaching-bounce@xxxxxxxxxxxxx [mailto:geocaching-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Bensman Sent: Monday, April 07, 2008 8:53 PM To: geocaching@xxxxxxxxxxxxx Subject: [GeoStL] Updated maps RE: Re: MOGA caches - It was a great time at MOGA!!!! Thanks to everyone who put it on. http://webpages.charter.net/jbensman/Maps.htm I have updated my maps to include more and better trail data and more POIs. For those without a Garmin and will go latter or will go back, I have a couple of pdfs that have the caches plotted on the map. They are much higher quality than what was given out and they have the trails. You can download them on my maps page. You can also download the source files with the tracks and waypoints I used to create the maps. The cache files that were placed on the Colorados not only did not work right (none of the fancy features worked), they messed things up on the CO so badly I was not able to download tracks or waypoints. Nor could the file on the GPS be opened. Fortunately, I finally figured out a way to access the track file and could get the coordinates of the waypoints on the GPS. So I was able to use my track files to update the trails. The problem is the files were not properly formatted for the CO, so I will volunteer to make sure they are done right next year. The problem was the files, not the CO. I GPSed the Prairie Loop so it is accurate. I GPSed part of the Joanna Trail, RGS GPSed some of it and the rest in the cache area shows up well on GoogleEarth. So the Joanna Trail location is accurate. Not much shows up on GoogleEarth on the West side so I do not have most of the mowed paths on the maps. Lots of stuff shows up on the East side on GoogleEarth. I added what I could see to the map, but beware what you see in googleEarth could be different on the ground. The traced map for the Log Cabin Loop is obviously way off. I took the track RGS gave me and made a good guess where the trail was since he bushwacked a lot. So don't expect that part to be accurate. But overall the maps should now be pretty accurate. I talked to Ranger Al who now has a 60CSX with my maps on it. He said he is now going to start GPSing stuff. I am going to help him figure out how to do it and he will give me the data. For next year, I will volunteer to make sure the trails get GPSed and to make sure there is a good trail map wherever it is. Jim Bensman "Nature Bats Last" Go Obama!-----Original Message----- From: geocaching-bounce@xxxxxxxxxxxxx [mailto:geocaching- bounce@xxxxxxxxxxxxx] On Behalf Of Glenn Nash Sent: Monday, April 07, 2008 7:48 PM To: geocaching@xxxxxxxxxxxxx Subject: [GeoStL] Re: MOGA caches - Well, thats a plus. :-) glenn Michael Rogers wrote: |
