[FEATURE] StoreyViewsPlugin sort on IfcBuildingStorey elevation #1710
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the way
StoreyMaps
are ordered inStoreyViewsPlugin.storeysList
.Ordinarily we sort each
StoreyMap
by the lowest point of the 3D boundary of its IfcBuildingStorey.This is a problem when the IfcBuildingStorey contains an element, such as a stairwell or drainpipe, that overlaps with the boundaries of other IfcBuildingStoreys. In this case, the correct spatial ordering is unclear.
This PR makes sorting more robust by sorting the Storeys on the IfcBuildingStorey
elevation
attribute, if provided in the data.If not provided, then sorting will fall back on using the boundaries as just described.
Usage example here, with an XKT file that contains metadata that has the elevation attributes on the IfcBuildingStoreys: https://github.com/xeokit/xeokit-sdk/blob/master/examples/navigation/StoreyViewsPlugin_Minimap_Duplex.html