Motivation and Context

This PR adds functions to test for point-region membership and point collection-region membership with a weighting factor, to account for possibly nested regions. If a point is only found in a single region, its weighting in that region is 1.

Otherwise, each region is assigned a weighting that is inversely proportional to the area of a particular region containing the point. The weighting is calculated like so :
`

     1 - (region_area/total_region_area)

whereregion_area` is the area of a specific region the point is found in and total_region_area is the total area of all regions that point is found in.

For collections of points that are assumed to belong to the same construct, the region membership check has been modified to give a weighting value only to the innermost (i.e. smallest area) region in nested regions. In other words, in the case of nested regions, a point is only considered found in the innermost region. the same weighting value to all regions containing a particular point. In the case of nested regions, this may result in an object being fully contained within the containing region, while only partially contained within the nested internal region.

How Has This Been Tested

Locally c and python tests. Python test modified to verify that with non-nested regions it returns the same result as the non-weighted versions

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have completed my CLA (see CONTRIBUTING)
• I have added tests to cover my changes.
• All new and existing tests passed.