This issue captures a potential enhancement to /location/overlaps for inputs/output features without albers area, but uses the base feature type area (meshblocks) to determine the target feature area value. The assumption is that the base feature type area (meshblocks) will always have the albers area value and that the features that contain it, will always contain those base feature instances.
The enhancement will be for the area of the meshblocks that overlaps with the result, use that sum up constitutent meshblocks to get the respective area values.
Currently /location/overlaps works with a selected number of features where albers areas are available. See http://loci.cat/integration-api.html#locationoverlaps for the list of feature types
This issue captures a potential enhancement to /location/overlaps for inputs/output features without albers area, but uses the base feature type area (meshblocks) to determine the target feature area value. The assumption is that the base feature type area (meshblocks) will always have the albers area value and that the features that contain it, will always contain those base feature instances.
The enhancement will be for the area of the meshblocks that overlaps with the result, use that sum up constitutent meshblocks to get the respective area values.
See #65