Problem with Caches Along a Route queries

[+Ringo67]

My Caches Along a Route queries, two of them that I run on a weekly basis, won't work with my Garmin software and an Web-based iPhone app I've been using.

 

I don't know what is wrong. They look the same as before when I open them using a text editor. However, after working for weeks, all of a sudden they can no longer be opened using my Garmin software and won't upload using the iPhone app.

 

Anyone else having these problems?

 

Thanks,

- Paul

aka Ringo67

[Ruslt]

Im having the same problem. I think it must be a bug right now. Im leaving to go out of town in the morning and can't get the darn file to be recognized by mapsource. It keeps saying not a valid GPX file. HELP!!!!

[+EraSeek]

Yup, same here. I thought it was my old EasyGPS version, so I upgraded, but still the same. Errors out as not valid GPX file.

[+Ringo67]

Yup, same here. I thought it was my old EasyGPS version, so I upgraded, but still the same. Errors out as not valid GPX file.

 

Well, at least now I know it's not just me.

 

Hopefully, the Groundspeak Web gurus can identify the bug and fix it.

 

- Paul

[+Team DEMP]

I never tried a route GPX but I did it to see if I could identify why it might be an issue. First, GSAK opened it fine. Then I tried with EasyGPS and it didn't open it saying that there was no gpx found. I looked and the file starts with <Gpx with a capital G. I changed it to <gpx and it went all the way until the end. I then changed </Gpx to </gpx at the end and EasyGPS as well as MapSource opened it fine.

 

So until geocaching.com makes the change, you can manually edit the file and change Gpx to gpx on the 2nd line and last line of the received GPX.

 

Hopefully GC.com won't say "it shouldn't matter" since 2 programs many use can't read the files and they can change quicker then the other 2 programs.

[+EraSeek]

How do you get to that point to change it?

[+Team DEMP]

The GPX file is just a text file. Save it to your desktop and open it in any text editor including notepad. Change Gpx to gpx at the start (2nd line) and end (last line) and save the file. Then use that file.

[+EraSeek]

Thanks : )

[+Ringo67]

Thanks : )

 

Yeah, Thanks!

[+koikeeper]

Wow, you're the man! Thanks alot. How did you figure it out?

[+Team DEMP]

How did you figure it out?

 

The error message I got when loading into EasyGPS was "... Could not find <gpx> at the beginning of the file." so I opened it in a text editor and compared it to a regular PQ GPX and the difference was Gpx vs gpx. The closing gpx tag at the end of the file also was Gpx and not gpx so I changed that too.

 

I saved the modified GPX and it loaded fine into EasyGPS and also into MapSource. Now if we use a page like http://www.topografix.com/gpx/1/1/#element_gpx as the source of what the schema (the structure of the GPX file should be, it should be lower case. I don't see anything in that documentation which indicates the schema should be treated case insensitive. So I downloaded the large recommended validation program (it's part of a larger distribution) and ran it with the following output:

 

D:\xerces-c_2_8_0-x86-windows-vc_8_0\bin>SaxCount.exe -v=always -n -s -f 1816433.gpx

 

Error at file D:\xerces-c_2_8_0-x86-windows-vc_8_0\bin/1816433.gpx, line 2, char 377

Message: Unknown element 'Gpx'

 

Error at file D:\xerces-c_2_8_0-x86-windows-vc_8_0\bin/1816433.gpx, line 2, char 377

Message: Attribute 'version' is not declared for element 'Gpx'

 

Error at file D:\xerces-c_2_8_0-x86-windows-vc_8_0\bin/1816433.gpx, line 2, char 377

Message: Attribute 'creator' is not declared for element 'Gpx'

So as you can see, it's an apparent error on the creation of the file by the GC.com site. More info then you probably wanted to know, but that should answer your question

[Ruslt]

Now that my day trip is over and I missed out on caching along my route, I was able to get mapsource and cachemagnet to recognize the file with the helpful post by Team Demp! This is an issue that really needs addressed by Groundspeak. I don't pay 30.00 a year to have to change files to get them to work. I pay 30 bucks to cache along a route and I didn't get to do that. Thanks again Team DEMP!

[+TexasGringo]

***Change Gpx to gpx at the start (2nd line) and end (last line) and save the file. Then use that file***

 

Yep, that worked...."Gpx" should all be lower case "gpx".

[+benh57]

This should be fixed... Nate?

[+Team DEMP]

This should be fixed... Nate?

I just downloaded the same route GPX and it is NOT fixed as of 7am ET on Monday morning.

[+Dustydew]

This should be fixed... Nate?

 

The gpx file generated from a query is not working in Vantage Point (for the Triton GPS) this morning either. I tried it twice and it says "invalid file type". Hope this gets fixed soon.

[+koikeeper]

Once again a big THANK YOU to TEAM DEMP!! We're going to SC in a couple of weeks and I started working on our route. I was very disheartened when I couldn't open the file. Didn't have time to figure it out and knew that I hadn't changed anything since the last time I ran a route. I'm surprised more people aren't complaining about this.

[+EraSeek]

"G"px still capitalized.

[+benh57]

This should be fixed... Nate?

I just downloaded the same route GPX and it is NOT fixed as of 7am ET on Monday morning.

 

By 'this should be fixed' i meant, 'Groundspeak should fix this ASAP... OpinoNate, where are you, please confirm!'

 

Odd that we have had no word from GS on this issue, as it's pretty critical.

[+EraSeek]

I just did a pocket query. Looks like it is a lower case G now but it is erroring out anyway. Looks like something else isn't right now.

[majormajor42]

I was also having problems loading .gpx files into mapsource from PQs. Since I only wanted the coords and titles (GCXXXX) I made my PQs .loc files instead. It was a simple solution. I use WAP on my cell phone if I need hints and stuff about a cache I am trying to find.

[+Team DEMP]

I just did a pocket query. Looks like it is a lower case G now but it is erroring out anyway. Looks like something else isn't right now.

I just told it to send me a new GPX of a route just before 7am ET and it's still a capital G in the file.

 

For all those with an issue, it's a quick edit on your end to open the file in any text editor, edit the 2nd and last line to be gpx instead of Gpx and save the file.

 

If you save the GPX to your desktop and you are using Windows, do the following:

1. Click Start / Run and in the run box type notepad and press enter. That should open the notepad application up.

2. Size notepad and move it so you can see the GPX file on the desktop and the notepad application at the same time.

3. Drag/drop the GPX file from your desktop into the notepad window and it should (after a few seconds if it is large), open the GPX file in notepad.

4. Make the change from GPX to gpx on the 2nd and last lines of the file

5. Click File / Save to save the changes back to the GPX file on your desktop.

6. Click File / Exit to close notepad

7. Use the GPX file in EasyGPS or Mapsource, etc.

[+EraSeek]

I wonder if standard pocket queries are doing something different than routes. Unless I messed up, when I tried to edit the errored-out query the G was small case. The routes queries I did I was able to edit.

[KoenigDickBauch]

It is only one character worng in the file! G and not g

 

<Gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" creator="Groundspeak Pocket Query" xsi:schemalocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.Groundspeak.com/cache/1/0 http://www.Groundspeak.com/cache/1/0/cache.xsd" xmlns="http://www.topografix.com/GPX/1/0">
 <name>Troisdorf nach Morschreuth</name> </Gpx>

 

it has to be (XML is case sensitiv)

 

<gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" creator="Groundspeak" pocket="" que=""></gpx>

 

You can change it by your self with an UTF-8 editor or use MakeGoogleMap.

 

Regards

Thomas

[+Team DEMP]

It is only one character worng in the file! G and not g

 

As noted in previous posts, it's Gpx to gpx in 2 locations - the 2nd line and the last line.

 

and it's wrong, not worng but that is nitpicking

[KoenigDickBauch]

It is only one character worng in the file! G and not g

 

As noted in previous posts, it's Gpx to gpx in 2 locations - the 2nd line and the last line.

who cares for the last to line? There it is all read.

 

Yes i read it your post, but open a GPX with an normal editor and there are Äs and Ös inside. You get other problems, if you has no UTF-8 editor.

 

Thomas

[+Team DEMP]

It is only one character worng in the file! G and not g

 

As noted in previous posts, it's Gpx to gpx in 2 locations - the 2nd line and the last line.

who cares for the last to line? There it is all read.

 

Because it still fails with a </Gpx> which needs to be changed to </gpx>. I guess that is why it matters.

[+ncparolelady]

I'm having trouble getting google earth to recognize the .gpx files. I've tried changing the uppercase G to a lowercase g...still no luck. Won't even open in Google Earth.

[+LightHouseSeekers]

Had same problem today. Went on road trip said @#$% is the cache along a route PQ caches I loaded before I left the house. Compared that file and another PQ. Like others have said change Gpx to gpx and it works. Used notepad to make the correction.

 

May have had the same problem 2 weeks ago with a regular PQ,

but didn't read that file just reverted to the prior copy and waited for

the next PQ run to reload again.

 

I guess someone at gc.com needs to figure out why this is happening.

[+ncparolelady]

I've tried changing the uppercase "G" to a lowercase "g" in both locations of the text file using notepad. Doesn't make any difference....gpx file still isn't recognized by google earth. Couldn't get Microsoft Streets and Trips to work either using the info. GSAK seems to read the info just fine. I'm pretty comfortable with computer "stuff" and have tried everything I can think of to fix this. No luck. Anybody else having problems running pocket queries and then trying to open in Google Earth or is it really just me?

[+Team DEMP]

I've tried changing the uppercase "G" to a lowercase "g" in both locations of the text file using notepad. Doesn't make any difference....gpx file still isn't recognized by google earth. Couldn't get Microsoft Streets and Trips to work either using the info. GSAK seems to read the info just fine. I'm pretty comfortable with computer "stuff" and have tried everything I can think of to fix this. No luck. Anybody else having problems running pocket queries and then trying to open in Google Earth or is it really just me?

I fired up Google Earth (v 4.3.7191.6508) and loaded in a route GPX which even uses Gpx vs the correct gpx and I had no issue opening it.

 

Maybe there's some specific cache that is causing it? Try the following. Go to a specific cache page like http://www.geocaching.com/seek/cache_detai...1d-59f1248d9988 and click the GPX button and download the single cache GPX to your desktop. Can you load GCEAE7.gpx using File /Open in Google Earth? If not, I think it is something with your Google Earth and you ought to try downloading the latest release and updating your copy.