I think `$geoIntersects` more closely meets user expectations. The [docs for `$geoWithin`](http://docs.mongodb.org/manual/reference/operator/query/geoWithin/#op._S_geoWithin) say: 

> The $geoWithin operator is a geospatial query operator that queries for a defined point, line or shape that exists entirely within another defined shape.

That means if the shape is even slightly imprecisely drawn and misses, for example, a corner lot, it won't be included in the stats. I feel that erring on the side of including more will be more forgiving and provide better results. 

Too bad there's not a `$geoMostlyWithin`.