Revit cannot assign psets to site without having a topography object
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
It is not possible to implement the IFC2X3 georeferencing guide by buildingSMART in Revit - i.e. to assign a Pset_MapConversion and Pset_ProjectedCRS to the IfcSite element, without first creating a topography object to be exported as IfcSite. Generally, MEP files do _not_ have a topography, so this workaround leads to unnecessary geometry in their files, and requires the files to be additionally patched afterwards.
Contributor guide
Research direction
Start by reproducing the issue in Revit with an MEP file that has no topography, then inspect the IFC export path for IfcSite georeferencing data. Done means Pset_MapConversion and Pset_ProjectedCRS can be assigned to IfcSite without creating or exporting unnecessary topography geometry, while following the IFC2X3 buildingSMART guide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100