2026-02-17
10:17 AM
- last edited on
2026-02-19
03:05 AM
by
Laszlo Nagy
I'm struggeling with georeferencing my current project.
My client want IFC4, georeferenced whith the information embedded in the IFC-file, like this
I believe this is where I have to fill in the data to make this work:
I have filled in all the information requered, (I believe), supplied by EPSG.IO:
I have also made sure that the IFC-exporter is correct:
Still, when I export to IFC, this is the only instance of IFCMAPCONVERSION in the file when opened in notepad...
What am I doing wrong??
.Kamelite
Operating system used: Windows 10
Solved! Go to Solution.
2026-02-18 11:17 AM
I discovered, like you are pointing out, that everything is done correct.
I just had to take the IFC into solibri to confirm that everything was in place!
.Thank you for answering
.Kamelite
2026-02-17 07:19 PM
I think you’re doing everything right. There should be only one IfcMapConversion entity, because the different properties (egenskaper) are just different attributes of that one entity. As you can see, the easting is the third attribute, the northing is the fourth, and the elevation is the fifth in the IFC file.
You can find the official definition in the IFC4 specification here: https://standards.buildingsmart.org/IFC/RELEASE/IFC4/ADD2_TC1/HTML/schema/ifcrepresentationresource/...
For EPSG codes, https://epsg.org is a very useful reference. For example, the details of your code (5110 – ETRS89 / NOR EUREF89 NTM zone 10) can be found here: https://epsg.org/crs_5110/ETRS89-NOR-EUREF89-NTM-zone-10.html
Or is there some other issue you’re having with the location?
2026-02-18 11:17 AM
I discovered, like you are pointing out, that everything is done correct.
I just had to take the IFC into solibri to confirm that everything was in place!
.Thank you for answering
.Kamelite