This object is in archive! 

Child Waypoints not correct recognized from one Geocache

Wolfgang shared this problem 7 years ago
Solved

Hi,

I have added Child Waypoints in GSAK and exported this Geocache. When I now import this Cache into Locus I get separated waypoints.

Usually this works pretty fine. Guess there is something different and Locus does not understand it.

GPX file is attached.

Thanks Wolfgang

Files: Tour.gpx

Replies (3)

photo
1

Good day Wolfgang,

as I see ... to correctly attach child waypoints to a parent cache, it is needed that these waypoints name contains ID of cache. So in this case, you cache has ID GC5GAAY, this means that all names of child waypoints have to end with xxx5GAAY code.

This is anyway not a case of your file, where all points are simply numbered since number one. Are you using any special macro for export? Because this is not a expect standard format.

photo
1

Hi Wolfgang,


for me it looks like some of the child waypoints of GC5GAAY are wrong saved / named in the gpx-file as Menion already mentioned.


Instead of


<name>01</name>

and so on

the child waypoints 01 - 25 should be saved / named as


<name>015GAAY</name>

and so on in the gpx file.

There is a comment


<cmt>Grabbed from: "D:\Temp\test.csv"</cmt>

that you are importing this cache from a csv-file. Maybe this csv-file contains already wrong information of the name-tag of waypoits 01 trough 25? Just a guess ...

Funny, but some child waypoints seems to be named correct. Like


<name>R15GAAY</name>
....
<name>R25GAAY</name>
....


c.s.g.

photo
1

Hi,

thanks for your replies. Then I guess the problem is related to GSAK. It's possible to add Child Waypoints manually or to grab them from e.g. the Clipboard. That's what happened here.

I didn't know that a child waypoint is defined with it's name to the Geocache. Thought this has to do with (sub-)fields inside the GPX file.

Thanks Wolfgang

Replies have been locked on this page!