On 9 November 2012 14:29, Joshua Lieberman <[email protected]> wrote: > It really depends on the goal of showing those features. If the intent of the > map is to present a summary or overview, then it makes sense to do an > intersect or create a raster and sum up the issues for each resulting feature > / cell. If the intent is to browse the individual issues, then it might be > less cluttered to do something like a map of centroids where rolling over > each point brings up the associated full geometry and attributes.
I intend it to be an exploratory interface, so it has popups attached to the geometries already. I think that for most users it will be driven by the geography, so people are asking themselves "which issues are affecting <my house|my school|my workplace>?" rather than "where does these issue affect?" It's not designed as a statistical overview or for drawing summary conclusions from the data. The former question relies on the geometries being displayed, somehow - if the polygons are only displayed as centroids then the users will have to whack-a-mole to find out which ones affect their house or school. Cheers, Andy _______________________________________________ Geowanking mailing list [email protected] http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
