Jump to content
GeoKen

GPX Export File has no Attributes

Recommended Posts

Brand new to Cachly but long time Geosphere user.  I have an offline database that contains 6 caches that I each contain a log not and a cache note in Cachly.  I uploaded these to GC.com without any issues.  After the upload I wanted to export the file information for these into GSAK.  I did the export GPX command and got a zip file.  When I loaded this into GSAK I get the "File has no attributes" error.  Does the upload (post logs to GC.com) clear the attributes that GSAK needs when receiving a GPX file?

Part 2.  What is the best way to get the Cachly Cache notes into the GSAK user note?

Thanks

Share this post


Link to post
Share on other sites

GPX exports do include attributes. GSAK for some reason always shows that warning. Did you make sure that the attributes really didn’t get imported?

Can you email me the file using the email support option?

Exporting a GPX will also send personal notes. 

Share this post


Link to post
Share on other sites

Nic: If the file is indeed in the correct format, consider the following difference between a GC GPX file and a Cachly GPX file that causes the GSAK alert:

Cachly:

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"

GC:

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/1 http://www.groundspeak.com/cache/1/0/1/cache.xsd"

In a quick test, modifying a Cachly GPX export to match what GC outputs for the 2nd line in the GPX eliminates the alert on GSAK import. 

Share this post


Link to post
Share on other sites

Those headers appear to show that Cachly uses GPX v1.0 and GC.com v1.0 

GSAK and GC.COM both support v1.0.1 extensions (set in on your preferences)   v1.0 does not include attributes, but 1.0.1 does...

see https://forums.geocaching.com/GC/index.php?/topic/240499-differences-in-gpx-10-101-and-11/

 

Even if Cachly includes the attributes in the GPX file, without the proper version indicated in the header, GSAK (and potentially GPSRs that support 1.0.1) may not load them, thinking it's a v1.0 file.

-TWT

Share this post


Link to post
Share on other sites
32 minutes ago, TheWinterTrio said:

Those headers appear to show that Cachly uses GPX v1.0 and GC.com v1.0 

 

The headers are different and Cachly shows 1.0 while GC shows 1.0.1 . I updated the Cachly reference to match GC's reference and GSAK imported without the alert dialog.

In the generated GPX files the differences I outlined above are (which would be obvious if the forum didn't auto hyperlink):

http://www.groundspeak.com/cache/1/0 vs http://www.groundspeak.com/cache/1/0/1

and

http://www.groundspeak.com/cache/1/0/cache.xsd vs http://www.groundspeak.com/cache/1/0/1/cache.xsd"

both have Cachly outputting /1/0 while GC.com outputs /1/0/1

Share this post


Link to post
Share on other sites
2 hours ago, Team DEMP said:

The headers are different and Cachly shows 1.0 while GC shows 1.0.1 . I updated the Cachly reference to match GC's reference and GSAK imported without the alert dialog.

In the generated GPX files the differences I outlined above are (which would be obvious if the forum didn't auto hyperlink):

http://www.groundspeak.com/cache/1/0 vs http://www.groundspeak.com/cache/1/0/1

and

http://www.groundspeak.com/cache/1/0/cache.xsd vs http://www.groundspeak.com/cache/1/0/1/cache.xsd"

both have Cachly outputting /1/0 while GC.com outputs /1/0/1

Thanks, will get this fixed.

Share this post


Link to post
Share on other sites

Nic-

Here is a GPX file that I exported OUT of Cachly and tried to load into a new database in GSAK.  I get the the error from GSAK that the file has no attributes.

I am using Cachly version 3.0.3(14). This is how I exported the file out of Cachly.

1. I load an offline database created from a GSAK GPX file into Cachly.

2. I selected one cache in this data base and created a cache note for it.  Note is "Under a tree."

3. I also made a log for this cache as "Found while testing Cachly."  I then saved the log entery.  This resulted in a red circle with the number 1 showing up by the more menu in the lower righthand portion of the screen.

4. I then selected "Offline" from the selections on the bottom of the screen.

5. I set a filter to show only Found caches and selected "List".  This showed only the single cache I marked found.

6.  Pressing the ... on the top right of the screen I selected "Export GPX" from the list items that are shown from this action.

7. I selected the  "Export GPX" list item the filtered caches list item.

8. I gave it an Export Title of Cachly Export Test", made sure the Included logs, The included GSAK Extensions & Include Private Data sliders where all to the right and indicating green.  I selected "Export" and Save to Drop Box.  Then pressed "Save".  This successfully exported the file.

9. Now I try to import the gpx file in a clean data base in GSAK and I get errors and the cache information does not show up.  I tried to attach the zip file that Cachly created on the export but can't seem to get the insert attachment to work.

Share this post


Link to post
Share on other sites
11 hours ago, Team DEMP said:

The headers are different and Cachly shows 1.0 while GC shows 1.0.1 . I updated the Cachly reference to match GC's reference and GSAK imported without the alert dialog.

In the generated GPX files the differences I outlined above are (which would be obvious if the forum didn't auto hyperlink):

http://www.groundspeak.com/cache/1/0 vs http://www.groundspeak.com/cache/1/0/1

and

http://www.groundspeak.com/cache/1/0/cache.xsd vs http://www.groundspeak.com/cache/1/0/1/cache.xsd"

both have Cachly outputting /1/0 while GC.com outputs /1/0/1

Sorry, I didn't really complete the thought...   Each file has two version numbers.  A GPX version and the Groundspeak Extention Version.. 

What I meant was that the Cachly shows GPX1.0 and GS1.0     Where the GC.COM shows GPX1.0 and GS1.0.1. 

Share this post


Link to post
Share on other sites
5 hours ago, GeoKen said:

Is there a way I can test this for you to see if it solves the problem?

Yes, I can add you as a beta tester if you would like. The beta version with this fix should be out later this week.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×