Yes, the macro respects (and restores) filters.
Image Maker - Please see this page (click here) for an explanation of how to set PQ's up using this macro. If your multiple PQ's are roughly contiguous, i.e. look like this example from that website:
![user posted image]()
The PlacedPQ macro will eliminate the overlaps and allow you to get maximum efficiency in covering the entire area.
As TheWinterTrio said, if your PQ's are widely separated, you will have to use filters and run the macro against each filter of caches. With the addition of GPXFile in Version 8.3.1.58 of GSAK (here), you could create the GPXFile custom field, load your existing PQ's to populate that field, then filter on GPXFile. This would make it relatively easy to use PlacedPQ with disparite areas. However, you may find it even easier to keep those caches in separate databases (one for Seattle, and one for Portland, to use TheWinterTrio's example) and just load the respective PQ's into their own DB's.![smile.gif]()
Image Maker - Please see this page (click here) for an explanation of how to set PQ's up using this macro. If your multiple PQ's are roughly contiguous, i.e. look like this example from that website:
The PlacedPQ macro will eliminate the overlaps and allow you to get maximum efficiency in covering the entire area.
As TheWinterTrio said, if your PQ's are widely separated, you will have to use filters and run the macro against each filter of caches. With the addition of GPXFile in Version 8.3.1.58 of GSAK (here), you could create the GPXFile custom field, load your existing PQ's to populate that field, then filter on GPXFile. This would make it relatively easy to use PlacedPQ with disparite areas. However, you may find it even easier to keep those caches in separate databases (one for Seattle, and one for Portland, to use TheWinterTrio's example) and just load the respective PQ's into their own DB's.
