I understand the saturation guidelines, and I've cached enough to know that the map wouldn't be able to include all stages, points, exclusions, areas of sensitivity and the like. I still think this would be an excellent tool for a hider because let's face it, it's annoying to have to compute distances over and over again from all the surrounding caches. Example:A new monument is erected that would be a great spot for a cache, but there's already a few hides nearby. I could A. find a distance calculator and plug in all the coordinate pairs of every cache and the digits I got in the field, then have to head out to the field and take a new set at a guessed location if my original recordings were no good. -OR- B. Glance at a map. The map would tell you, quickly and easily, what areas near your intended cache location were available for a hide. If there were 11 rocky outcroppings near where I wanted to place my cache, what would be easier? Taking readings at each and comparing every single measurement to known caches, or glancing at a map and seeing 'These 7 won't work, but these 4 are outside the circles and are ok.' The answer is obvious.
As for not hiding a cache every .1 of a mile, while that is all good and wonderful in the text, it's a bit ignorant of the fact that sometimes high cache density is a good thing, especially in areas where accessible locations are limited. I live near Penn State Main Campus, and it's just a fact that the vast majority of students living here do not have access to vehicles to take them far from campus. Are the student cachers just supposed to be content finding the 2 dozen or so caches that exist already nearby, since they cannot easily travel outside the area? I don't think so. Exacerbating this problem is a distinct lack of caches with terrain 1 in my area. Little kids cache, people have disabilities that prevent them from climbing hills and traversing rocky terrain, etc., so being able to scout location easily for Dx/T1 urban caches can be nothing but a boon.