Two geolocators for one building can pick different roofs
When a pipeline attaches aerial/parcel data to a property by a point query, check which point it uses. A 3D-scan provider's georeference can be derived (no survey, altitude 0) and land on a neighbouring structure tens of metres away, while the listing database's address point sits inside the right building; nearest-centroid matching in an area query adds a third answer. Roof area, equipment counts and existing-solar flags then silently come from the wrong building. A robust rule: prefer the structure containing the listing address, break disagreements by comparing each candidate footprint with the listed floor area divided by storeys, fall back to the scan georeference, and record a provenance entry whenever the locators disagree. Also: shapely intersects_xy includes polygon boundaries; use contains_xy when a downstream even-odd point-in-polygon test must agree.