A site-context handoff needs units, a shared origin, orientation, elevation basis, coordinate reference information and source revisions. An address or aerial image helps identify a place; it does not establish the dimensional and coordinate basis required to align design models.
Misalignment often appears as a visual problem: the building floats, rotates away from the street or lands beside the parcel. The underlying problem is usually a missing relationship between coordinate systems or source files. Moving the model until the picture looks right can conceal the error until the next update.
Separate identification, context and survey information
An address identifies the intended location. Aerial imagery explains surrounding patterns. A survey or other commissioned site dataset supplies its stated measured information. Keep those sources distinct, with dates and responsibility attached.
Use a context boundary appropriate to the decision. An entrance review needs the adjacent street and neighboring frontages. An aerial composition may need a larger block. A distant skyline can be useful visual context without being treated as a measured obstruction model.
Write the coordinate contract before import
Ask the source owner for a short coordinate note. Keep it with the files rather than inside a message that disappears when the project changes hands.
| Field | Required clarification | Acceptance check |
|---|---|---|
| Units | Source and working model units | A known distance agrees |
| Origin | Local reference point and its meaning | Control point lands in the expected place |
| Orientation | True north, project north and rotation relationship | Known direction agrees |
| Elevation | Vertical reference and units | Known level agrees |
| Coordinate reference | Named system and transformation information where supplied | Recipient can reproduce alignment |
| Source revision | Author, file version and survey/context date | Correct issue is being used |
buildingSMART’s IFC map-conversion documentation describes the relationship between local engineering coordinates and a map coordinate system, including translation and rotation information.[1] That relationship needs to survive the handoff. It is not equivalent to entering a project address.
Test alignment with independent references
Choose control information before import. Check a known point, a known direction and a known distance; also check elevation where relevant. A single point can coincide even when scale or rotation is wrong. Record the expected values and the observed values in the recipient’s application.
If the check fails, identify which transformation was applied. Was the file exported in different units? Was project north mistaken for true north? Was the vertical reference dropped? Resolve the source relationship instead of adding an undocumented corrective move.
For a lightweight visualization scene, it can be useful to work near a local origin while retaining the mapping back to site coordinates. Record the transform and verify it after export. The buildingSMART georeferencing guide provides a detailed framework for documenting these relationships in IFC workflows.[2]
Label context by reliability and purpose
Distinguish surveyed features, modeled design, approximate surroundings and photographic background. Record where heights or distances are assumptions. If a neighbor’s height is unknown, do not give its placeholder the appearance of a measured value in a comparison report.
Use one base context revision across massing options. Otherwise the team might interpret a changed neighboring building or terrain surface as an effect of the proposed design. Context changes should be reviewed like design changes because they can alter what a view appears to demonstrate.
This matters especially for sun and shadow questions. Coordinate and orientation records are inputs to the analysis, not labels to add after a favorable image has been produced.
Handoff the source and the acceptance record
Include source files, coordinate note, control checks, context classification and unresolved questions. Keep the original files and their revisions unchanged. Link any derived visualization mesh to that source issue.
The Rendora architecture tool can retain site reference files and their hashes alongside the scenario input. Those stored references are not automatically parsed into a surveyed site model. Use the site-context checklist to document the alignment work performed in the source and visualization applications.
Coordinate questions
Is latitude and longitude enough for a BIM handoff?
It can locate the project broadly, but model coordination also needs the local origin, orientation, units, elevation basis and the relevant mapping information. Ask the source author for the complete relationship used in the project.
Can an aerial photograph be used as a background?
Yes, when its permitted use and role are clear. Match the camera and record its source. Do not treat an unverified background image as a substitute for surveyed dimensions or a measured terrain model.
References
[1] buildingSMART IFC documentation, IfcMapConversion.
[2] buildingSMART, User guide for georeferencing in IFC. Use the project's agreed exchange requirements when applying the guidance.
About the author
Rendora Journal covers configurable assets, production checks and traceable delivery workflows.