We are testing the screening widget to allow members of the public to assess which Local Plan policies are in force in a user defined area. There is clearly some geoprocessing going on in the background which calculated the area of intersection of each layer with the area of interest. This works very well for the most part. However, we are having problems when there is a donut polygon involved (in our case Green Belt). If the area of interest straddles an area where there is a hole in the donut polygon, the reported area of intersection is the whole area of the polygon. For example, the area of interest was 0.4km2 yet the intersection was 166km2.
Can you let me know how we can get round this, or if there is any way to supress this intersection calculation altogether as I think it will be very confusing to customers.