Geocaching Wish 'Search for Geocaches' 4.28.2
I have a feature request for the 'Search for Geocaches' function.
The current function searches around an ever-widening radius until the requested number of geocaches are downloaded. This can be problematic, since it is not known how many are in an area of interest. If you input too large a number, you get an area MUCH larger than desired. An option to specify a radius would actually be more useful, in my opinion.
I very much prefer the method used by Geocaching4Locus where it just searches within the approximate screen boundary. This is actually my preferred method. It allows me to zoom and position the map display to the park or preserve we are going to visit, and it limits the download to just that area, regardless of the number of geocaches in that area.
I like this idea 
I agree abd generally use Geocaching4Locus because of that. It woukd also be nice to delete just the caches that are on the screen
I agree abd generally use Geocaching4Locus because of that. It woukd also be nice to delete just the caches that are on the screen
And a assosiated request: Within "Search for geocaches" please make the numeric field on the right editable. And better remove the slider instead.
Right now its not very easy (espaecially not during outdoor activities) to adjust small numbers with the slider on the very left of the screen edge.
And a assosiated request: Within "Search for geocaches" please make the numeric field on the right editable. And better remove the slider instead.
Right now its not very easy (espaecially not during outdoor activities) to adjust small numbers with the slider on the very left of the screen edge.
Hello,
in the next app version will be the option to import really only displayed caches on the screen over running live-map. Is it working solution for you?
Hello,
in the next app version will be the option to import really only displayed caches on the screen over running live-map. Is it working solution for you?
@Menion: both are different work-flows, although the request here mixes up both methods ;-)
1) GC Live map: Somebody opens a map and enables "GC Live map" to see if, where, and how much Caches in the map's area are. Optionally additionally import all displayed Caches within the rectangular bounding-box into a Locus folder.
2) Search for Geocaches: Enter a location by coordinates, the name of a town, map-center etc. and download all Caches either a) within a certain circle-radius in Meter/Kilometer or b) a certain number of Caches next to the location
@Menion: both are different work-flows, although the request here mixes up both methods ;-)
1) GC Live map: Somebody opens a map and enables "GC Live map" to see if, where, and how much Caches in the map's area are. Optionally additionally import all displayed Caches within the rectangular bounding-box into a Locus folder.
2) Search for Geocaches: Enter a location by coordinates, the name of a town, map-center etc. and download all Caches either a) within a certain circle-radius in Meter/Kilometer or b) a certain number of Caches next to the location
Oki, understand. In this case, this idea can't be implemented. I'm limited to 500 caches. So if I allow download of 10km radius, it may be satisfied in the mountaines, but not in the big city. Because of this, such option will be confusing and problematic.
Oki, understand. In this case, this idea can't be implemented. I'm limited to 500 caches. So if I allow download of 10km radius, it may be satisfied in the mountaines, but not in the big city. Because of this, such option will be confusing and problematic.
Option 2a) has been succesfully part of GSAK for years now which uses the same API as Locus, and it's not been confusing at all ;-)
In case of 2a) Locus just has to download each Cache within the radius (you could restrict it to 50 km - which is the API-limit regarding GSAK). Plus if the number of Caches would be >500 just download the nearest 500. IMHO this is anyway the method the API delivers Caches which exceed a certain number.
A helpful test: requests Caches of 5 km around Prague centre which are about 1100 ;-) => Gsak downloads just a certain user-defined amount which could be 500 which finally are all Caches within a radius of 2,9 km
Option 2a) has been succesfully part of GSAK for years now which uses the same API as Locus, and it's not been confusing at all ;-)
In case of 2a) Locus just has to download each Cache within the radius (you could restrict it to 50 km - which is the API-limit regarding GSAK). Plus if the number of Caches would be >500 just download the nearest 500. IMHO this is anyway the method the API delivers Caches which exceed a certain number.
A helpful test: requests Caches of 5 km around Prague centre which are about 1100 ;-) => Gsak downloads just a certain user-defined amount which could be 500 which finally are all Caches within a radius of 2,9 km
... and in case of 2a) GSAK interface provides an additional field named "Max. geocaches". This could be filled by default with "500", but could be user-set to a lower value for people who don't want to load hundrets of Caches in a dense area.
... and in case of 2a) GSAK interface provides an additional field named "Max. geocaches". This could be filled by default with "500", but could be user-set to a lower value for people who don't want to load hundrets of Caches in a dense area.
I think the suggestion is all the more important an urban area, or places in rural areas where repetitive caching trails might be narrowed.
The “import displayed” option Menion wrote about seems like it would be a great start but the GSAk style rectangular selection could extend the option. I knew I had seen this before but could not remember that it came from GSAK.
The number of caches seems like it is covered in the slider box but just writing in a number might be easier for some.
I think the suggestion is all the more important an urban area, or places in rural areas where repetitive caching trails might be narrowed.
The “import displayed” option Menion wrote about seems like it would be a great start but the GSAk style rectangular selection could extend the option. I knew I had seen this before but could not remember that it came from GSAK.
The number of caches seems like it is covered in the slider box but just writing in a number might be easier for some.
Replies have been locked on this page!