Additional Waypoints

January 22, 2006

I'm having the same error others mentioned...

If I select "hide everything except for owners and administrators", I can't see the coordinates for the final.

January 22, 2006

The only way to know for sure is open the PQ in Wordpad (or equivalent) to see what is REALLY there.

This has been done, already.

It is not a GSAK problem. (See my post above in this thread.)

-Wlw

2.5k · January 22, 2006

I'm having the same error others mentioned...

If I select "hide everything except for owners and administrators", I can't see the coordinates for the final.

Just click on the Add/Edit near the additional coordinates listing and you can see all the coords that you entered. Jeremy said he did that to avoid the questions about whether everyone can see those.

Edit: deleted comment that didn't come out right.

Edited January 22, 2006 by WeightMan

2.5k · January 22, 2006

When something unusual happens in GSAK when a new function is implemented here, I don't think you should start by assuming it's a problem here. (Even though I am a very happy user of GSAK.)

I thought I made it clear that I didn't know where the problem was. After posting that here, I went to the GSAK forum and read through the thread on the new waypoints and chose not to post anything there. I realize that Clyde is still working on this change and will await his next release. I can wait, no problem.

9.4k · January 22, 2006

I can certainly remove the final coordinates for caches you own from showing up in GPX file downloads. However I felt that as the owner you should be able to get them.

To reduce confusion should I simply remove them entirely?

No one gets them except the owner when downloading them individually from a cache listing. This is just to clarify.

January 22, 2006

I can certainly remove the final coordinates for caches you own from showing up in GPX file downloads. However I felt that as the owner you should be able to get them.

To reduce confusion should I simply remove them entirely?

No one gets them except the owner when downloading them individually from a cache listing. This is just to clarify.

I was concerned about that initially, but upon seeing that I would be the only one getting them, I've added waypoints to my puzzle caches. Still, I think that hidden points should only come from an individual download as rarely will a cache owner need to have the points anyway.

January 22, 2006

I just thought of a good function for this. This would be ideal for downloading temporary event cache waypoints. The points would still have to be manually entered by the GPX inaccessible, but it would be a boon to the rest of us.

Keep up the good work!

January 22, 2006

I can certainly remove the final coordinates for caches you own from showing up in GPX file downloads. However I felt that as the owner you should be able to get them.

To reduce confusion should I simply remove them entirely?

No one gets them except the owner when downloading them individually from a cache listing. This is just to clarify.

IMHO, no! I like the ability to download the coordinates and always have them online. I was keeping the additional coordinates in notes in GSAK, and, as I found out when I went to edit coordinates yesterday on one of my multis - sometimes those notes get accidentally deleted! <_<

I like the ability to add the extra waypoints to my downloads.

1.3k · January 22, 2006

While adding a few to my caches tonight, I thought that it would be a bit more useful to have an 'Add' button beside the Create and Archive ones (at least for multi-cache waypoints but still useful for regular ones that might have more than one 'additional waypoint').

The Create button becomes Make Changes after you've done that first waypoint...it would be a little quicker and more efficient to be able to just add the next stage waypoint right from that edit page, instead of having to go back to the main cache page and Add another one.

I'd like to second this request.

2.8k · January 22, 2006

While adding a few to my caches tonight, I thought that it would be a bit more useful to have an 'Add' button beside the Create and Archive ones (at least for multi-cache waypoints but still useful for regular ones that might have more than one 'additional waypoint').

I just read the thread, and didn't see any response to this request. Did I miss it? Is it going to be implemented?

2.8k · January 22, 2006

Starting to add waypoints to all my multis and puzzle caches. A very useful feature. Now I don't have to have separate files for answers to questions, special info, etc.

Thanks GC!

2.1k · January 22, 2006

Scanning the thread I'm not sure if this has been mentioned yet or not. I'm still seeing that error that was first reported in this thread (the one about the GUID being incorrectly formatted).

I get this when hitting the 'add/edit waypoints' option at the top of the 'edit cache details' page.

Pasting the correct GUID in to the URL works fine.

1.1k · January 23, 2006

I like the new additional coordinates feature. This will be very useful. I also like the way this shows up on the cache pages.

I wonder what the sort order is in the waypoint table at the end of the long description.

I need a waypoint type for coordinates where hikers need to make a turn. I don't envision a lot of these, but more than a typical multi-stage cache. I also envision this to be needed for some multi-stage caches that involve hiking. So using the "Stage" type for this would not be ideal.

I have a cache where I have informational stops as well as stages. I would probably use the previous feature to handle the informational stops, but maybe a type could be created especially to highlight interesting things that we want to show.

3.7k · January 23, 2006

(Jeremy) To reduce confusion should I simply remove them entirely?

No! In fact it would be ideal if all caches had space for more owners' information (miscellaneous waypoints, notes on how the puzzle is solved, photos of relevant items etc.).

I guess that most people hold this stuff on their own system somewhere: although most will (usually) have no trouble re-finding it, there is the danger that it disappears after a couple of years. Or, if there's a query, that you can't access your home PC for a while so can't answer it (e.g. you're away on a week-long caching trip and you get an e-mail from a team complaining that they "looked under a red stone and there was nothing there". It would be nice to have a spoiler pic to send them, and details of how far (for example) the stone is from the fence).

With more sophisticated caches becoming commonplace, it would save embarrassment if we were able to access our notes via the cache page. This won't apply to those with fantastically accurate memories, of course...

HH

January 23, 2006

I downloaded my PQ's this morning to GSAK and the WPT codes for GCM3RB had absolutly no relation to the cache itself. All of the codes were xxMD18.

When I downloaded the gpx file straight from the cache all of the WPT codes were xxM3RB.

Any ideas why this is?

2k · January 23, 2006

I downloaded my PQ's this morning to GSAK and the WPT codes for GCM3RB had absolutly no relation to the cache itself. All of the codes were xxMD18.
When I downloaded the gpx file straight from the cache all of the WPT codes were xxM3RB.

Any ideas why this is?

That would be a GSAK issue.

GSAK Support Forum

I think it's a known issue and Clyde has either a work-around or a fix available, but check the GSAK Forum.

[Edited to correct:]

From the following post it appears that my assumption was incorrect. Sorry. :unsure:

Edited January 23, 2006 by beejay&esskay

January 23, 2006

I downloaded my PQ's this morning to GSAK and the WPT codes for GCM3RB had absolutly no relation to the cache itself. All of the codes were xxMD18.
When I downloaded the gpx file straight from the cache all of the WPT codes were xxM3RB.

Any ideas why this is?

That would be a GSAK issue.

GSAK Support Forum

I think it's a known issue and Clyde has either a work-around or a fix available, but check the GSAK Forum.

At the suggenstion of Clyde I opened up the WPT file. I opened it using Map Source and the WP codes are indeed as I reported earlier, so this in not a GSAK problem as suggested.

January 23, 2006

I downloaded my PQ's this morning to GSAK and the WPT codes for GCM3RB had absolutly no relation to the cache itself. All of the codes were xxMD18.
When I downloaded the gpx file straight from the cache all of the WPT codes were xxM3RB.

Any ideas why this is?

That would be a GSAK issue.

GSAK Support Forum

I think it's a known issue and Clyde has either a work-around or a fix available, but check the GSAK Forum.

At the suggenstion of Clyde I opened up the WPT file. I opened it using Map Source and the WP codes are indeed as I reported earlier, so this in not a GSAK problem as suggested.

I'm having the same problem with a PQ for all caches in Ireland. Only two caches have additional waypoints at this stage, but the code was the same for all waypoints.

January 23, 2006

I just had a weird situation, listed a new offset cache with the final coords marked as viewable by administrators/owner only.

I even labelled it "Admin" and it was flagged as "Final", but the local reviewer just posted:

Log Date: 1/23/2006
Hi, I'm reviewing this cache for posting on geocaching.com, but first I

need to know the coordinates of the other stages of this multicache.

I asked if they were unable to see the final coords in the page when I replied with 'em, but just wanted to note it here (or maybe they don't read the Announcements!?)

If they let me know I'll let you know...

Enjoy,

Randy

January 23, 2006

So, two obvious things. Why does it have a different prefix? Surely it should be GC7E12<something> (My preference is GC7E12-01, but YMMV). That way the cache and the addl wpts sort together.

I second that!

Why wouldn't we add a suffix instead to keep the alphabethical order of the caches and their additional waypoints? That seems to make sense to me, a lot more sense than adding a prefix. I can understand why the prefix was chosen (historical reason: all waypoint codes starts with GC), but I'm not sure this is the best approach.

When I manually enter a waypoint in my GPS, I use -PK (for parking) or -F (for final) or -A, -B, - C for multi and what not. So a parking coordinate for GCR999 would be GCR999-PK.

BTW, this is a great feature, I've been wanting such a feature for years now, but it needs some work in my opinion. And the description of suffix/lookup code needs some better wording. It is very confusing. There has been some talks on our local geocaching forum and people don't understand how to use them and what the rules are, etc.

Suggestion: Why isn't the prefix (or suffix) auto-generated by Groundspeak based on the waypoint type. That way we would have a standard naming convention for parking, trailheads, etc. Otherwise this is going to become a confusing mess. For points that can have multiple, then let the user add a number or digit or something to idetify them uniquely.

Edited January 23, 2006 by Mr. Speedy's parade

9.4k · January 23, 2006

Scanning the thread I'm not sure if this has been mentioned yet or not. I'm still seeing that error that was first reported in this thread (the one about the GUID being incorrectly formatted).
I get this when hitting the 'add/edit waypoints' option at the top of the 'edit cache details' page.

Pasting the correct GUID in to the URL works fine.

Thanks. I've been trying to figure out where that error was. You gave me good directions. I'll try to fix it today.

January 23, 2006

I added the stages to a multi cache I own (GCKQYF), with 6 stages and a hidden final, and then setup a PQ for all caches that I own. When I got the PQ, all the extra waypoints were included in the GPX file, including the hidden final. Was it supposed to do this? did it know that I was the cache owner and therefore include the final point?

9.4k · January 23, 2006

Was it supposed to do this? did it know that I was the cache owner and therefore include the final point?

Yes. That's right. As the owner you have that data available to you.

Because of the confusion I think what I may do is only allow that data downloadable via the Edit waypoints page. That way you'll know that you will get those waypoints there and experience the same thing everyone else does in other places.

Edited January 23, 2006 by Jeremy

January 23, 2006

Possible bug?

This cache: http://www.geocaching.com/seek/cache_detai...3a-1be487c3ff5a shows two additional waypoints on the page. Park 1 at N 41° 43.055 W 088° 04.228 and Park 2 at N 41° 42.701 W 088° 04.804. However, in the PQ I just received, there are three additional waypoints for this cache -- the two listed above (P1T246 and P2T246) plus one more. The third additional waypoint has the code PKT246 with the coords of N41° 43.083 W88° 03.783. There is no mention of this third waypoint on the cache listing. Could this have been a deleted additional waypoint that is somehow being picked up by the PQ?

Those "extra" coords are actually the parking coords for another one of my caches nearby, GCT23E

Are you sure the "extra" coords aren't listed under PKT23E?

I'm positive they weren't listed under PKT23E.

I just re-ran that PQ and I get 6 different waypoints named PKT246, plus an STT246, a PET246, a PWT246, a P1T246 and a P2T246. GCT246 still only shows two additional waypoints. The gpx is:

<?xml version="1.0" encoding="utf-8"?>
<gpx xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" creator="Groundspeak, Inc. All Rights Reserved. http://www.Groundspeak.com" 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>Waypoints for Cache Listings Generated from Geocaching.com</name>
 <desc>This is a list of supporting waypoints for caches generated from Geocaching.com</desc>
 <author>Various users from Geocaching.com</author>
 <email>contact@geocaching.com</email>
 <url>http://www.geocaching.com</url>
 <urlname>Geocaching - High Tech Treasure Hunting</urlname>
 <time>2006-01-23T18:28:23.2809591-08:00</time>
 <keywords>cache, geocache, waypoints</keywords>
 <bounds minlat="41.69275" minlon="-88.14575" maxlat="41.8267166666667" maxlon="-87.1413333333333" />
 <wpt lat="41.7451666666667" lon="-88.05925">
   <time>2006-01-19T16:39:20.8570000-08:00</time>
   <name>PKT246</name>
   <cmt />
   <desc>Boundary Hill Drive Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=80b2187d-0a95-4d92-a6bb-c6632d4b8c71</url>
   <urlname>Boundary Hill Drive Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.69275" lon="-88.02155">
   <time>2006-01-19T16:45:08.2170000-08:00</time>
   <name>PKT246</name>
   <cmt />
   <desc>Suggested Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=125d4bc5-9a1c-43a1-81ae-3cf3bfcf64b0</url>
   <urlname>Suggested Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.71295" lon="-87.9124333333334">
   <time>2006-01-20T09:40:45.5130000-08:00</time>
   <name>PKT246</name>
   <cmt>Parking area for the Forest Preserve in the area.</cmt>
   <desc>Best Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=bf677c2b-57d4-4219-b8d1-6b9e59cc3c41</url>
   <urlname>Best Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.7336" lon="-87.8794166666667">
   <time>2006-01-20T09:50:54.3900000-08:00</time>
   <name>PKT246</name>
   <cmt>I & M Canal Bike Path Parking Lot.</cmt>
   <desc>Best Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=f334a536-7568-4767-8d14-f124358acb7a</url>
   <urlname>Best Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.7332166666667" lon="-87.88015">
   <time>2006-01-20T09:52:27.9670000-08:00</time>
   <name>STT246</name>
   <cmt>Maybe you can get another couple of caches along the way, hint-hint :)</cmt>
   <desc>Suggested starting point</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=13a6478c-5ab4-4cf2-9adf-f0f2a7c1e81d</url>
   <urlname>Suggested starting point</urlname>
   <sym>Trailhead</sym>
   <type>Waypoint|Trailhead</type>
 </wpt>
 <wpt lat="41.7126833333333" lon="-87.1413333333333">
   <time>2006-01-20T09:57:12.3570000-08:00</time>
   <name>PKT246</name>
   <cmt>Knoch Knolls Park parking lot</cmt>
   <desc>Best Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=6d896967-6c69-432b-98ff-3792ce6b0647</url>
   <urlname>Best Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.8184833333333" lon="-88.1132333333333">
   <time>2006-01-20T05:36:35.5000000-08:00</time>
   <name>PET246</name>
   <cmt />
   <desc>Magellan East Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=813f2e74-d77f-4000-93d4-c116864dd6bc</url>
   <urlname>Magellan East Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.8267166666667" lon="-88.14575">
   <time>2006-01-20T05:33:48.9500000-08:00</time>
   <name>PWT246</name>
   <cmt />
   <desc>Magellan West Parking</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=3888e053-efc0-496a-b9f9-fd2154e9d1e7</url>
   <urlname>Magellan West Parking</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.7180555555556" lon="-88.0630555555556">
   <time>2006-01-19T16:35:49.8570000-08:00</time>
   <name>PKT246</name>
   <cmt />
   <desc>Winston Drive Parking Lot</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=483626e5-ec62-4376-b001-bfe7a6e80281</url>
   <urlname>Winston Drive Parking Lot</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.7175833333333" lon="-88.0704666666666">
   <time>2006-01-19T16:27:09.7630000-08:00</time>
   <name>P1T246</name>
   <cmt />
   <desc>Royce Road Trailhead</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=3e381777-4a7e-40a7-a48f-f108b5eb8e48</url>
   <urlname>Royce Road Trailhead</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
 <wpt lat="41.7116833333333" lon="-88.0800666666667">
   <time>2006-01-19T16:28:56.1070000-08:00</time>
   <name>P2T246</name>
   <cmt />
   <desc>Delaware Circle Trail Access</desc>
   <url>http://www.geocaching.com/seek/wpt.aspx?WID=5fb6edd7-85ee-4270-8844-e4205e15e837</url>
   <urlname>Delaware Circle Trail Access</urlname>
   <sym>Parking Area</sym>
   <type>Waypoint|Parking Area</type>
 </wpt>
</gpx>

January 23, 2006

I'd like to see the usual links to mapping services on the additional waypoints detail page.

Thanks.

2k · January 23, 2006

I'd like to see the usual links to mapping services on the additional waypoints detail page.

Thanks.

That's a very good idea.

January 23, 2006

Just a follow-up of my earlier post (from our reviewer):

...reviewers do not have access to the data entered on this screen; please continue to provide additional coordinates with your submissions for multi-stage caches.

fyi,

Randy

January 24, 2006

I really like the feature to add waypoints.

I think it could even be more interesting when one could add pictures for each additional waypoint ?

January 25, 2006

I just found a bug in the add-waypoint feature...

I went to the add new geocache form page. I immediately clicked the add-waypoint.

It seems I got someone else's GUID:

http://www.geocaching.com/hide/wptlist.asp...8a-9fbe91cd7ed9

--The page said:

Managing waypoints for a listing

Waypoint Collection

You do not have access rights to edit waypoint info for this listing but you can view coordinates.

For listing: Callin' All Cachers (Unapproved) (Traditional Cache)

--" Callin' All Cachers (Unapproved) " is a link.

For grins, I tried it again - and got a different unapproved cache.

Please let me know if this post is being seen. This seems like an important issue to fix. If I do not see any reply, I will assume I need to post this information elsewhere to have it get the correct attention.

9.1k · January 25, 2006

Were you trying to add the Additional Waypoint to a cache that had already been submitted, and had a GC waypoint number assigned to it? If not, the database gets confused, because it's looking to associate the Additional Waypoint with its related cache, and it cannot find a cache. So, it chose one at random.

January 26, 2006

This feature is excellent, I used it immediately on an existing cache in Alice Springs, Australia 'Top Red Centre' GCJ703 because it involves climbing a slightly dodgy escarpment and I get people to pass through safe waypoints en route so they don't take a straight GPS line and fall off something. My only problem was with waypoint types, I ended up labelling all three points as 'trailhead' but they aren't really, just points on a route. If we can't use the category'waypoints' can we perhaps add the category 'trailpoints' or better, 'trackpoints'?

Also the little double signpost icon is just fine for 'trackpoints' if we had this category perhaps the 'trailhead' icon could have an icon with just one sign on the post.

Thanks Jeremy.

January 26, 2006

Better yet: replace "Trailhead" by "Trackpoint".

If only one trackpoint is given, people will know to start their walk there.

January 26, 2006

But if they're all trackpoints, where do you start?

9.4k · January 26, 2006

I'd call it a waymark, but that name has been taken

How about just Trail Marker?

8k · January 26, 2006

I'd call it a waymark, but that name has been taken

How about just Trail Marker?

In the other thread I suggested "Trail Junction" or "Route Waypoint"

2.8k · January 26, 2006

I'd call it a waymark, but that name has been taken

How about just Trail Marker?

I like it.

January 27, 2006

Regarding the PQ additional file. Love it :lol: One request regarding the name.

The original files have the name of the PQ

the associated wpt files for any PQ have the same name value

<name>Waypoints for Cache Listings Generated from Geocaching.com</name>

could the name of the waypoint file also include the pq name. for eg the name for the wpt file for my PQ6 example above could be

so auto-renaming a number of waypoint files based on this data does not lead to a naming conflict.

Thanks

Sue

January 29, 2006

Is there nothing in the .GPX file for the waypoint that associates it with a particular cache? Here's the GPX file for one waypoint:

<?xml version="1.0" encoding="utf-8"?>
<gpx xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" creator="Groundspeak, Inc. All Rights Reserved. http://www.Groundspeak.com" 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>Waypoints for Cache Listings Generated from Geocaching.com</name>

<desc>This is a list of supporting waypoints for caches generated from Geocaching.com</desc>

<author>Various users from Geocaching.com</author>

<email>contact@geocaching.com</email>

<url>http://www.geocaching.com</url>

<urlname>Geocaching - High Tech Treasure Hunting</urlname>

<time>2006-01-29T00:21:26.1012501-08:00</time>

<keywords>cache, geocache, waypoints</keywords>

<bounds minlat="32.8648" minlon="-97.2481333333333" maxlat="32.8648" maxlon="-97.2481333333333" />

<wpt lat="32.8648" lon="-97.2481333333333">

<time>2006-01-28T16:13:06.1370000-08:00</time>

<name>CCRYWY</name>

<cmt>trailhead</cmt>

<desc>THTest</desc>

<url>http://www.geocaching.com/seek/wpt.aspx?WID=a48997a1-237c-44e3-ad79-a064aaa46339</url>

<urlname>THTest</urlname>

<sym>Trailhead</sym>

<type>Waypoint|Trailhead</type>

</wpt>

</gpx>

I don't see anything to associate this waypoint with the parent cache. So, when I import this into GSAK, nothing tells me the cache this waypoint is part of. It just shows up as a random waypoint. Can a link to the parent cache be included in the GPX file?

Edited January 29, 2006 by Admin Web-ling

5.2k · January 29, 2006

I don't see anything to associate this waypoint with the parent cache. So, when I import this into GSAK, nothing tells me the cache this waypoint is part of. It just shows up as a random waypoint. Can a link to the parent cache be included in the GPX file?

<name>CCRYWY</name>

It looks to me like this is associated with GCRYWY. If GSAK doesn't know that then its a problem with GSAK, not the website.

3.2k · January 29, 2006

I would like to request that the additional waypoint be marked as MINE when I'm the cache owner.

I made one that is hidden so only myself or reviewers can see it. When I import the cache page into GSAK the "owner" flag isn't set on the file so it isn't marked as belonging to me. It would be great if the new waypoint was flagged as belonging to the cache owner.

January 29, 2006

It would be nice to have some explicit link to the cache, but just repace the first 2 characters of the waypoint with GC and there you have it. Off to alter all my programs now to cater for it. Now why am I not out caching

Sue

January 29, 2006

I don't know if it's just me, but I actually prefer alphabetical order. When I have a series of waypoints all related to the same GCxxxx entry, I like to add a *suffix* to the thing so that they all show up beside each other in the list, both in GSAK and CacheMate.

Is there any consideration of making the 'prefix' into an optional suffix for Pocket Queries? I know that this wouldn't work for those with a GPSr that only handled 6 chars, but so many new ones handle more than that now.

Elsewise, I may have to break down and learn GSAK scripting and write myself a nifty macro to do this.

Thanks!

wsgaskins

I just had to add my vote....Before parking coords were downloadable, I was creating additional waypoints in GSAK with the suffix PK so that they all sorted together with their associated cache. That way, I could easily find and delete the two if a cache was archived. This was nice & simple. I have to be careful now...can't just drag & drop the file into GSAK. I have to screen through the new listings for those extra coords & delete/rename/etc. before adding them to my main GSAK database. There is probably an easier way to do this, but I'm "technically handicapped".

2k · January 29, 2006

Before parking coords were downloadable, I was creating additional waypoints in GSAK with the suffix PK so that they all sorted together with their associated cache.

I think the decision has been made on how to name the addtional waypoints and it is unlikely to change just because it causes problems for some other software.

There is a new version of GSAK available which lets you ignore the additional waypoints, at which point you are no worse off that you were before.

Beyond that, Clyde is working hard at expanding the functionality of GSAK to handle the additional waypoints better.

GSAK support forum

February 1, 2006

I received a PQ today with a new cache that uses the additional waypoints feature. It's great for uploading to my GPSr using EasyGPS, but I also use Mobipocket for viewing cache information on my smartphone. It does not appear that the additional waypoints show up in any way in the .prc file. The waypoint in question is GCT8RD. Is this a bug?

1.6k · February 2, 2006

Since I haven't received a PQ with the additional waypoints in it, I have to ask this....

Do you get two separate files, one with the caches and a second with the additional points, or are they all combined in one file?

Not nearly a code monkey.... or even in the simian family :rolleyes: but to me it would be easier for the end user to have two separate files.

That way you could have two separate databases... one for caches, one for additional waypoints.

Again... haven't seen one yet.... so I'm not sure what applies.

The Blue Quasar

2k · February 2, 2006

You get two files with PQs. (Of course, with single gpx downloads from the cache page, you get one file with the extra waypoints mixed in. :rolleyes: )

6.1k · February 2, 2006

I recently published my first 2 caches, which were both multis. I put in the location for the first stage as a waypoint, and then in the text referenced it as "first go to waypoint STAGE1 below", etc. However I had a mail from a cacher who had printed off the cache page in PDF format and when they got to the area found that the it didn't include the details of the waypoints, so they were a little stuck. For now I've put the co-ords for the first stage in the text as well as in the waypoints to aviod this happening again but this seems a little unneccessary to me.

Is it possible to have the PDF download also include the waypoints descriptions?

Martyn.

2.9k · February 2, 2006

I'd call it a waymark, but that name has been taken

How about just Trail Marker?

Id go for route the word trailhead means absolutely nothing to me i had to guess it meant walk to here etc.

Ive also put the GCcode in every description for my additional waypoints it certainly looked better when i downloaded them last night mine are clearly identifiable to the correct cache.

February 2, 2006

...the word trailhead means absolutely nothing to me ...

Come to think of it - to me neither.

Could it be an American word only?

February 2, 2006

...the word trailhead means absolutely nothing to me ...

Come to think of it - to me neither.

Could it be an American word only?

rail·head Audio pronunciation of "trailhead" ( P ) Pronunciation Key (trlhd)
n.

The place where a trail begins.

You're welcome.

Additional Waypoints

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment