Description
Description
The 3D model capabilities in MS are currently supporting GLTF in 3D model symbolizers. It is requested to provide also support for IFC 3D models:
- georeferenced if IFC v4 is used
- non-georeferenced for older IFC versions to be used instead of GLTF in model symbolizer
What kind of improvement you want to add? (check one with "x", remove the others)
- Minor changes to existing features
- Code style update (formatting, local variables)
- Refactoring (no functional changes, no api changes)
- Build related changes
- CI related changes
- Other... Please describe:
Other useful information
Proposal based on shared model by @ufficiosit
It is proposed here to create a new type of layer of type model to allow to include:
- Catalog to include an ifc as layer
- Workflow for import and visualize an ifc on map
- Identify workflow
- Panel settings with following options:
- Visibility
- General tab (title and description)
- Custom tab to add possibility to change position of the center of the model
- [Optional] Add adjustment of the center interacting with the map (this need to include a review of the settings panel)
Notes:
We need to include the web-ifc library in MapStore (check license compatibility).
- Style panel will not be available for this type of layer. It is already defined within the model.
- This type of layer should be used for small IFC files. For large files it’s better to convert to 3D Tiles. we should consider to show a message to the user if the IFC file is too big to be rendered in MS (to evaluate during design)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment