Basecamp - geocaches need to be locked

Former Member over 14 years ago

Hi

I plan my geocache trips using the route feature within Basecamp. I first add all the caches to the route and then I stretch the route over the public footpaths using the 'insert' waypoint tool. I add a waypoint just before the next cache, so that the gps beeps on approach, in case I am enjoying the countryside too much. I can then switch to the cache and GO there, so that I can read notes / logs / clue and log the cache when complete, as this cannot be done from the route folllow. Once complete, I switch back to the route and follow to next cache.

When planning in Basecamp, I have found that the caches can be moved using the move tool - THIS IS A REAL PROBLEM. If I want to adjust the route and add another cache, or take a different path to take in some scenery, when I select what I think is the nearby waypoint, Basecamp thinks I have selected the cache and when I drag, it moves the cache. Due to the prob with indexing on the 62s, I then have to exit basecamp, delete gpx files and route from gps ( because it holds any caches that are in the route and these do not index properly - and these are the ones I am going to visit!! ), unplug gps, reboot gps, reload new gpx files again, unplug gps, reboot gps to allow gpx indexing, reconect gps, load basecamp...... what a carry on!!

If Geocaches were LOCKED ( why would anyone want to move them? - even for puzzle caches you wouldnt move them like this because you cannot get the accuracy with the coords ) this would prevent the above happening.

Please, please lock all geocaches, or at least add a user switchable option to lock them - just like in Memory Map.

Thanks

Steve

0 Former Member over 14 years ago

The problem seems to be two-fold for you:

when I select what I think is the nearby waypoint, Basecamp thinks I have selected the cache and when I drag,

There is an easier way to select route waypoints more accurately. Select the route you want to edit; then select its properties tab to see the list of route waypoints. Now, as you select each route waypoint, BaseCamp will show you exactly what you've selected on the map. If you double-click on the route waypoint on the list in the properties tab, BaseCamp will even pan and zoom so you can see it very clearly. Now you can edit/move this waypoint and BaseCamp should have no reason to think you've selected some other cache.

Due to the prob with indexing on the 62s, I then have to exit basecamp, delete gpx files and route from gps

I don't know exactly what the indexing problem is.

0 Former Member over 14 years ago

Any feedback from a Desktop App Developer????
I still think that Geocaches need 'locking' on the map - no need for them to be moveable.

Thanks GRMNGURU for your reply. I was aware of what you describe, but I find it easier to work with the map to move waypoints onto public footpaths. As my waypoints are approx 150ft before a cache it means that I dont walk past and get chance to swap from route to geocache follow in order to be able to read notes/hints and be able to log the cache - something which you cannot do from the route follow.

The indexing prob is well documented on the geocaching forums. Basically with my Garmin 62s, if I have 2 gpx files on there and want to add say 1000 caches in a different location ( 2 more gpx files ), I cannot simply just add the 2 new gpx files - as the GPS will only load these 2 new ones when it next boots up - ALL gpx files incl routes that contain ref to any geocaches, have to be deleted from the 62s and then the 4 gpx files loaded, unpluigged from pc, and then gps rebooted for all the 4 gpx files to be 'read' - or 'indexed'. Feedback from Garmin ( well documented replies on the GC.com forums ) suggests its a GC problem with the gpx files, but GC say its a Garmin problem - neither will agree its their problem, hence us paying Cust ( bought a Garmin, pay GC prem subscription ) just have to live with it - which I dont agree with.

0 Former Member over 14 years ago

I agree, I don't see any reason to support moving a geocache. I'll add a case to address this issue in a future release .

0 Former Member over 14 years ago

I agree, I don't see any reason to support moving a geocache. I'll add a case to address this issue in a future release .

Many thanks for taking this on board.
Steve

0 V10TDI over 14 years ago

For what it's worth, I think the user needs to have control over moving a geocache.

For example, here is one good reason why I might want to move a geocache:
http://www.geocaching.com/seek/cache_details.aspx?guid=68da0e69-9a48-4916-9fd0-2546cf89f77e

In this case, the owner of the geocache hasn't updated the actual coordinates to their geocache. I'd like to move it in Basecamp, but I cannot.