New Compatable GPX Format - Testers required

[CraigRat]

G'Day,

We've bitten the bullet after a lot of soul searching and we've decided to offer up GPX files that are compatable with other geocaching websites.

The primary drivers for this are:
* More people are using Mobile apps WITHOUT going thru programs like GSAK, and most of these apps only handle one GPX format
* Garmin's Opencaching Site and the actual Opencaching network have decided to use formats that have Groundspeaks namespacing in them
* Less confusing for noobs
* Reduces development effort for EVERYONE.

We need some people to test this new 1.0.1 format.

If you are willing to help, go to http://geocaching.com.au/my/settings and set your GPX type to 1.0.1 and download some GPX files from cache/state/query pages and load them straight to your devices/apps/programs and let us know of the results.

After testing we will be making this the 'default' format for anyone who is currently set to 1.0 in their settings (99% fo users) for the sake of operability.

Your help in testing all this is appreciated.

[hgl]

Hi CraigRat,

I tried this out with Geocaching with Geosphere 2.4.2 on iPhone4 and unfortunately the app crashes as soon as it tries to process the GPX file. I tried loading it into an existing Group or a new Group.

I have a few macro's setup to load GCA queries into the app, setting it back to 1.0 works fine.

Let me know if there is any further info I can provide to problem solve.

Cheers
Craig (hgl)

[CraigRat]

There's been a change in the last half hour or so.
Seems some apps are REAL fussy about their GPX schemas
If anyone has any issues try loading a new GPX file and see how you go.

[CraigRat]

Hi CraigRat,

I tried this out with Geocaching with Geosphere 2.4.2 on iPhone4 and unfortunately the app crashes as soon as it tries to process the GPX file. I tried loading it into an existing Group or a new Group.

I have a few macro's setup to load GCA queries into the app, setting it back to 1.0 works fine.

Let me know if there is any further info I can provide to problem solve.

Cheers
Craig (hgl)

This is now confirmed as fixed. Thanks hgl for your help!

[hgl]

There's been a change in the last half hour or so.
Seems some apps are REAL fussy about their GPX schemas
If anyone has any issues try loading a new GPX file and see how you go.

Working well, 2 v1.0.1 queries loading into Geosphere. Well done

[Black Bunny]

CraigRat

What is the difference between 1.0.1 & 1.1 GPX formats?

Black Bunny

[CraigRat]

1.1 was a hack that kind of worked in Garmin devices (but not a lot else).

1.0.1 is eerily similar to Groundspeak's and would be the preffered format if you want to use the GPX file in any devices or apps

[Black Bunny]

OK. I have switched formats and will see how it goes on the iphone Geosphere app & Garmin 300.

[Black Bunny]

Just tried with the Garmin and had success with a query loaded in and showing as caches and not waypoints (as happened in the 1.0 format).

Loaded the same query direct from the Geosphere app and had no problems.

Thanks for the effort CraigRat

You have made Just a Cacher very happy.

[CraigRat]

Just tried with the Garmin and had success with a query loaded in and showing as caches and not waypoints (as happened in the 1.0 format).

I just realised it wasn't showing the any cache types in the GPS, I'm just testing it, should be fixed shortly

[EDIT: FIXED]

[Black Bunny]

That only happened when caches were loaded in via a query. When loaded individually, the caches came up fine.

[CraigRat]

That only happened when caches were loaded in via a query. When loaded individually, the caches came up fine.

If you do your query it should all be ok (so should any log types)

[kennythe1st]

load them straight to your devices/apps/programs and let us know of the results.
.

Tested using 2 Windows softwares that I use regularly and successfully with GPX files including those from GCA.

GPS UTILITY v4.99 successful apart from cosmetic issue

Used GPX from Route Goldfields Track: Daylesford - Castlemaine (Dry Diggings Track) which contains 3 caches. Warning '3 symbols not recognised' but file loaded and displayed fine. I presume the SS2eTrex symbol set that I have selected is not fully compatible with GC's symbol set or whatever you are using so don't regard the warning as an issue.

MEMORY MAP v5.4.4 Build 1113 unsuccessful

Import unsuccessful. Got "The parameter is incorrect". In my experience MM will not provide anything remotely useful in tracking this issue down. Given there are a few or more MM users, I can try variations of the file that you want to suggest. And/or I could send you a MM GPX export file so you can check it for obvious inconsistencies with your XML file content.

OZIEXPLORER v3.95.4k successful

I haven't tried GCA GPX import previously. This one worked fine.

Regards, Ken

[hgl]

I'm not sure how this relates, today I updated GSAK with all my e-mail delivered queries (including ones from GCA).

My find count went up by about 40, which I realised came from duplicate logs on some GCA caches; so I deleted all the GCA finds and re-imported my GCA "My FInds" query. Now my find count was down by about 40 .. hmm something odd was going on.

Finally I remembered the GPX format testing and set it back to 1.1. Re-loaded the GCA "My Finds" query and everything was back to normal.

I am not sure what was going on in GSAK, or how to test the problem - but it seems there may be an issue .. especially if the wyapoints already existed from the old format?

Let me know if you want me to try anything?

Cheers
Craig

[Black Bunny]

Just tried it myself and noticed the same thing. Had a look at the GPX file under 1.0.1 and noticed that the logs for my finds were not there (hence the low count). It appears to have only pulled the last week or so on the cache logs.

Set back to 1.0 and all was well again.