| QUOTE (Image Maker @ September 20, 2013 01:31 pm) |
| I stumbled across this VERY useful macro a few days ago. What assumption is the macro making about the centre point for the PQs? My DB up until now was filled with a series of PQs with vastly differing middle points, which is super for fine tuning but has a problem with unnecessary overlap. Does the macro first calculate the centre of the current points in the DB? If yes, I guess these coords would be useful for writing the PQs so could these coords be included in the output please. Thanks Chris P.S. Wouldn't it also make sense to include the radius for use in the last PQ? Without this won't the last PQ fetch too many caches? |
The Macros doesn't care about centerpoint, or locations. It takes all caches in the current database, sorts them by publish date and creates PQs with a certain amount of caches within them by date range.
The problem is going to come up when it says you need a single PQ from Date1 to Date2 to keep this date range updated, but in you're current setup it can't be covered in one PQ. (Ie. 10 Miles around Seattle and 10 miles around Portland can't be done in one PQ)
Every PQ needs to cover the entire area that's included in that database, but only for a small date range.
I use it on entire states, so the "area" of all the PQ's is well defined and there are no gaps anywhere.
I can't remember if the Macro respects, filters, but if so, you could manually filter on one of your PQ centertpoints, run the Macro, and create one set of PQs (ie. Seattle +10miles). Adjust your centerpoint, apply filter and then create a second set of PQs. (ie. Portland +10miles)
-TWT
