Bug #1317

accurately handling donut holes in boundaries when probed

Added by Frank Lenk almost 4 years ago. Updated almost 4 years ago.

Status:ResolvedStart date:06/12/2013
Priority:HighDue date:
Assignee:Andy Dufilie% Done:

0%

Category:-
Target version:-
Complexity: OIC Priority:No
Required by:MARC, Kansas City, MO

Description

I have the city geography displaying on this map. http://70.43.171.194:8080/weave.html?file=basemap.weave

The geography was imported from a Shapefile. There are small cities that are completely surrounded by a Kansas City, Missouri. In other words the larger city has several donut holes in it where it annexed all the land around an existing small city or town. If I look at the map in ArcGIS the two boundaries are clearly distinct. In Weave if you click on the larger city it shows it highlights that city with the holes excluded. However, when you click on the smaller city, say Gladstone, Missouri, it says there are two records, it highlights both cities and lists Kansas City in the tooltip even though that area is supposed to be a hole in its boundaries.

According to an email from Andy, this is due to a limitation if Weave's ability to properly intersect polygons. We would like to have this limitation removed.

History

#1 Updated by Andy Dufilie almost 4 years ago

  • Status changed from Open to Resolved
  • Assignee changed from Frank Lenk to Andy Dufilie

Also available in: Atom PDF