Without using the recently banned Macros, there is no way to keep your own database up to date.
It is necessary to recognize archived caches, but there is no possibility, to include these in PQs. Therefore my first request is to create a possibility to include them in the PQs (This could be a PM-feature).
Furthermore I would appreciate a complete redesign of the PQ-feauture. For example: for building a local DB for a larger area around your home coordinates, you have to use some tricks to get this working. There are several workarounds for this (e.g. split the PQs with the "placed between" data, or creating several PQs around different locations), but it is not easy to do this. I am really looking forward for a user-friendly way to create a local DB that can be held up-to-date.
I have a few suggestions:
- No more limitation to 500 caches for one desired PQ-search. If more than 500 caches are included in one search, then this search is splitted up AUTOMATICALLY into several PQs for this search. These single PQs could be counted in the same way as today. (Or instead there is a maximum number of caches, whose data can be used in personal PQs per week).
Lots of redundant data (PQs within intersecting radius around different locations) could be avoided.
- Possibility to create a PQ for a user defined polygon, in the same way how this can be used for GSAK.
With these polygons the user can also limit the data more.
For example no need to create a big radius, only because one single area at the edge of this is needed.
I know these points mean a lot of work for you, but maybe some of these ideas can be useful for you.
