add attribute 'height_valid', which can have the values ['true', 'obsolete', 'missing']
true – height is valid\
obsolete – height is invalid because the building is newer than the PC\
outlier/extreme/invalid – height value is unreasonable eg less than the lowest point in the NL, or roof height is less than ground height\
missing – height value couln't be assigned, possible causes:
one reason that the BAG contains "buildings" for bridges/ below bridges in which case th PC doesn't contain points classified as "building" (in case of AHN3). because in case of AHN3, only the "building" points are used for computing the roof-height of a building
the other reason is that the pointcloud is misclassified (also in case of AHN3)
there can be missing ground points if the building is completely sourrounded by other buildings in which case there are no "ground" points in the AHN
add attribute 'height_valid', which can have the values ['true', 'obsolete', 'missing']
true – height is valid\ obsolete – height is invalid because the building is newer than the PC\ outlier/extreme/invalid – height value is unreasonable eg less than the lowest point in the NL, or roof height is less than ground height\ missing – height value couln't be assigned, possible causes:
one reason that the BAG contains "buildings" for bridges/ below bridges in which case th PC doesn't contain points classified as "building" (in case of AHN3). because in case of AHN3, only the "building" points are used for computing the roof-height of a building
the other reason is that the pointcloud is misclassified (also in case of AHN3)
there can be missing ground points if the building is completely sourrounded by other buildings in which case there are no "ground" points in the AHN
missing roof heights might mean new building