Create a configuration variable in the Caching Process, that allows the user to determine the size of the supertile to render. In this way the user could determine the largest item and create the supertile based on the size of this item.
My organization tried to use a cached mapservice which included parcels, but there were 100s if not 1000s of duplicate labels. It seems like this could have been prevented, if the supertile could have been enlarged to encompass the largest parcel in this layer (or at least signicantly larger than the existing supertile to drastically reduce the duplicate labeling).
The workaround to this is the creation of annotation which would change when the parcels change, so it would need to be updated on a weekly basis. It seems a configurable supertile size would solve this problem.
