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.
-Josh Lieberman On Nov 8, 2012, at 1:21 PM, Andy Allan <[email protected]> wrote: > Hi All, > > I've been working for a while on a system[1] that lets people log > "issues" or "problem reports" geographically. A reporter can log the > issue as having a point, line or polygon geometry. > > The problem that I'm facing is how to best show a map of issues for a > given region, e.g. a town. They come in all shapes and sizes, often > overlapping, and that causes an unintelligible mess[2]. > > Any geowankers know of any sites that show multiple overlapping > features in a useful fashion? Any guides to how to approach the > problem? > > So far we've put in place to order by size (biggest at the back, of > course), make fills translucent (but it still sucks if too many > overlap), ignore polygons that entirely encompass the bbox - all > certainly worth doing, but it's a long way from something to be proud > of. > > Cheers, > Andy > > [1] https://github.com/cyclestreets/toolkit > [2] e.g. http://i.imgur.com/GafGb.png and http://i.imgur.com/Tl877.png > > _______________________________________________ > Geowanking mailing list > [email protected] > http://geowanking.org/mailman/listinfo/geowanking_geowanking.org _______________________________________________ Geowanking mailing list [email protected] http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
