IFC Georeferencing: Coordinate Systems, EPSG Codes and Real-World BIM Alignment

Coordinate problems are among the most difficult interoperability issues in large BIM projects. An architectural model may be created close to the origin for numerical stability, while a survey or GIS dataset uses projected coordinates that represent a real geographic location.

If these coordinate systems are not defined and interpreted consistently, models can appear hundreds of kilometres away from their intended position, rotate incorrectly or become misaligned with terrain and infrastructure data.

IFC provides mechanisms for describing the relationship between engineering model coordinates and projected map coordinates. Understanding these mechanisms is essential for reliable OpenBIM and GIS integration.

1. Local BIM Coordinates vs. Real-World Coordinates

Most 3D modeling applications work with a local Cartesian coordinate system. A building may be modeled near (0, 0, 0), with the X and Y axes aligned to the project grid and Z representing elevation.

Surveying and GIS workflows often use projected coordinate systems. These systems express positions using coordinates such as Easting, Northing and elevation. The values may be large because they refer to a location within a national or regional grid.

These two coordinate systems serve different purposes:

• Local engineering coordinates: Convenient for modeling, design and numerical operations.
• Projected map coordinates: Suitable for locating buildings and infrastructure in a geographic context.
• Vertical reference: Defines how elevations relate to a specified height datum.

A correct transformation must account for translation, rotation, scale where applicable, and the coordinate reference system used by the target application.

2. What Is an EPSG Code?

An EPSG code identifies a coordinate reference system or related geodetic definition in a widely used registry. It helps different applications agree on how coordinate values should be interpreted.

A projected coordinate system may define its projection method, underlying geographic datum, units, axes and area of use. Two datasets with similar-looking coordinate values are not necessarily compatible if they use different reference systems.

Selecting the correct EPSG identifier is therefore more important than simply copying Easting and Northing values. The project team should obtain the authoritative coordinate reference information from the survey or project specification.

An EPSG identifier should not be guessed from a country's name. Multiple projected systems, zones and vertical reference systems may be relevant within the same country or project region.

3. IFC Georeferencing Entities

IFC supports georeferencing through entities that describe the projected coordinate reference system and the transformation from engineering coordinates to map coordinates.

IfcProjectedCRS

IfcProjectedCRS represents the projected coordinate reference system used to interpret map coordinates. Its information can include the name of the system, its geographic datum, vertical datum, map projection and map unit, depending on the IFC schema and available data.

IfcMapConversion

IfcMapConversion defines the transformation between the local engineering coordinate system and the map coordinate system. It provides the map translation, orientation and scale information needed to place model geometry in the projected coordinate reference system.

These entities work together: the coordinate reference system describes what the map coordinates mean, while the map conversion describes how local model coordinates are transformed into those coordinates.

4. Understanding the Map Conversion Parameters

A simplified horizontal transformation can be expressed as:

In this simplified model:

• X and Y: Local engineering coordinates.
• E₀ and N₀: Map coordinate offsets.
• s: Scale factor.
• θ: Rotation angle between the local and map axes.
• a and b: Rotation components.

The precise interpretation of IFC attributes, axis conventions and transformation parameters must follow the applicable IFC schema and implementation. The simplified equations above illustrate the underlying 2D similarity transformation, not every possible coordinate operation used by GIS software.

Vertical coordinates require additional attention. A horizontal map conversion alone does not guarantee that elevations are referenced to the correct vertical datum. Height offsets and vertical coordinate transformations must be handled according to the project specification and software capabilities.

5. Rotation and Axis Convention Problems

A frequent source of errors is assuming that every application uses the same axis orientation. One application may define project north differently from true north, while another may interpret the local X and Y axes using a different convention.

A rotation sign error can cause a model to appear correctly translated but incorrectly oriented. The problem may be subtle in a small building model and become obvious when the model is overlaid on roads, property boundaries or survey points.

Always verify the transformation using at least two or three known control points. A single point can confirm translation at one location but cannot independently validate rotation and scale.

6. A Practical IFC Georeferencing Workflow

A reliable workflow begins with the coordinate specification, not with trial-and-error adjustments inside the modeling application.

1. Obtain survey information. Confirm the horizontal coordinate reference system, EPSG identifier, units, vertical datum and control points.
2. Define the local model origin. Decide how the engineering model coordinates relate to the project grid and building reference points.
3. Configure the transformation. Set the map offsets, rotation and scale using verified project information.
4. Export the IFC model. Ensure the export process preserves the intended georeferencing information.
5. Inspect the IFC data. Check the projected CRS and map conversion entities in a suitable IFC inspection workflow.
6. Validate in a second application. Import or overlay the model in a GIS or coordination environment using the same coordinate reference system.

This independent validation step is critical. A model can appear correct in the software that created it because the application remembers project settings that were not fully written into the exported IFC file.

7. Common IFC Georeferencing Errors

Incorrect EPSG identifier

A wrong coordinate reference system can shift or distort the model when interpreted by GIS software. Confirm the identifier from the project survey documentation rather than relying on approximate location.

Double transformation

Some workflows apply a coordinate shift during export and then apply another shift during import. This can result in large positional errors. Determine which application is responsible for each transformation.

Large coordinate values in the modeling environment

Moving detailed geometry directly to very large global coordinate values may create precision or display problems in some modeling and rendering systems. A local engineering origin combined with explicit georeferencing can be a more robust strategy.

Ignoring vertical datum differences

Two datasets can align horizontally while showing inconsistent elevations. Verify whether heights are ellipsoidal, orthometric or referenced to another project-specific vertical datum.

Assuming the IFC export preserved all settings

Export settings and software implementations differ. Inspect the resulting IFC data and validate the model in an independent application rather than assuming that the source project's coordinate configuration was preserved perfectly.

8. Why Georeferencing Matters for BIM and GIS

Correct georeferencing makes it possible to coordinate building models with terrain, roads, utilities, cadastral information and other spatial datasets. It is particularly important for infrastructure projects, campus-scale developments, urban planning and digital twin systems.

When IFC models are positioned consistently, downstream applications can perform spatial queries, visualize building assets in their geographic context and combine information from different engineering disciplines.

Georeferencing is therefore not merely an export setting. It is part of the information quality of an OpenBIM deliverable.

Frequently Asked Questions

What is IFC georeferencing?

IFC georeferencing describes how a building or infrastructure model's local engineering coordinates relate to a real-world projected coordinate reference system.

What is the purpose of IfcMapConversion?

IfcMapConversion defines transformation information that maps local engineering coordinates into map coordinates, including translation, orientation and scale parameters.

What is IfcProjectedCRS?

IfcProjectedCRS describes the projected coordinate reference system used to interpret the map coordinates associated with the IFC model.

Does an EPSG code define the building's local origin?

No. An EPSG code identifies a coordinate reference system. The relationship between the local model origin and map coordinates is defined separately through georeferencing transformation information.

Why does an IFC model appear in the wrong location in GIS?

Common causes include incorrect CRS information, missing map conversion data, axis orientation errors, unit mismatches or applying a coordinate transformation more than once.