This is a preemptive issue w.r.t the shared "package" that I am building for use across iOSPointMapper and AVIV ScoutRoute.
MappingGeometry is currently used in two places of the AccessibilityFeature that can end up being different from each other.
- AccessibilityFeature -> AccessibilityFeatureClass -> AccessibilityFeatureKind -> MappingGeometry
- AccessibilityFeature -> AccessibilityFeatureClass -> OSWPolicy -> OSWElementClass -> Metadata -> MappingGeometry
We need to ensure that the MappingGeometry used in both places is the same and consistent.
Or we need to remove this potential inconsistency probably by removing Metadata from OSWElementClass since OSWPolicy is part of an extension outside the framework and should not have MappingGeometry in it. But it logically makes sense for the OSWElementClass to have geometry data.
This is a preemptive issue w.r.t the shared "package" that I am building for use across iOSPointMapper and AVIV ScoutRoute.
MappingGeometry is currently used in two places of the AccessibilityFeature that can end up being different from each other.
We need to ensure that the MappingGeometry used in both places is the same and consistent.
Or we need to remove this potential inconsistency probably by removing Metadata from OSWElementClass since OSWPolicy is part of an extension outside the framework and should not have MappingGeometry in it. But it logically makes sense for the OSWElementClass to have geometry data.