Explore the reference / 10 notes
Spatial Context and BIM Exchange
Define coordinate, placement, provenance, and information requirements for CAD and BIM handoffs that use geospatial context.
Choose a question
Reference notes
Coordinate Context in CAD and BIM Exchange: Units, Axes, and Transform Chains
State the frames, units, axes, and transforms a recipient needs to interpret position, orientation, and scale in a CAD or BIM handoff.
Georeferencing a BIM Exchange Without False Alignment
Specify how local and project coordinates relate to a CRS, and why a BIM model's visual alignment does not prove georeferencing.
Define an IFC Exchange Scope: Release, Model View, and Purpose
Turn “send an IFC” into a scoped request naming the release, model view, recipient task, and required information.
When Geometry Arrives but BIM Meaning Does Not
Separate visible geometry from the hierarchy, relationships, classifications, and properties a BIM task may require.
Turn BIM Information Needs into Exchange Requirements with IDS
Use IDS to state required BIM objects, classifications, properties, values, and units within a defined IFC exchange scope.
Use a BIM Reference Model Without Confusing It for an Editable Source
Use a BIM reference for coordination without assuming it preserves design history, full semantics, or project acceptance.
Choose a BIM–GIS Integration Pattern: Mapping, Federation, or Linked Objects
Choose how building and geospatial models work together while stating required equivalence, identity, spatial context, and authority.
Preserve Civil Placement: Alignments, Stationing, Offsets, and Design Grids
State the curve- or grid-relative information a civil or infrastructure recipient needs beyond a flattened XYZ position.
Carry Survey and Elevation Provenance into a BIM Handoff
Specify the reference, control, processing, and accuracy records needed to interpret survey, scan, or elevation inputs around a design model.
Interpret Geospatial Reference Data Around a BIM Model: Scans, Rasters, and Tiles
Separate CRS, axes, height, stored coordinates, pixel or tile placement, and model frames when spatial context data accompanies BIM.
A model can look correct and still be wrong in scale, orientation, location, containment, or structured meaning. The recipient needs enough context to interpret a CAD or BIM handoff and to state what the exchange should preserve.
Choose the decision you need to make
Start with the task, then open the article that answers it. These articles are related reference points, not a required linear course.
- Coordinate Context in CAD and BIM Exchange: Units, Axes, and Transform Chains — declare local, project, and world frames, units, axes, and placement relationships.
- Georeferencing a BIM Exchange Without False Alignment — describe the relationship to a CRS and the operation context needed to reproduce it.
- Define an IFC Exchange Scope: Release, Model View, and Purpose — name the IFC release, view, recipient task, and information scope, including civil-placement dependencies.
- When Geometry Arrives but BIM Meaning Does Not — separate visible geometry from hierarchy, relationships, classifications, properties, and placements.
- Turn BIM Information Needs into Exchange Requirements with IDS — express selected object, classification, property, value, and unit requirements.
- Use a BIM Reference Model Without Confusing It for an Editable Source — set source-of-truth, update, reference, and issue-view boundaries.
- Choose a BIM–GIS Integration Pattern: Mapping, Federation, or Linked Objects — choose a conceptual integration pattern and declare equivalence, identity, authority, and loss.
- Preserve Civil Placement: Alignments, Stationing, Offsets, and Design Grids — state when a curve or grid relationship matters beyond displayed XYZ.
- Carry Survey and Elevation Provenance into a BIM Handoff — inventory spatial reference, source, control, checkpoint, and processing context.
- Interpret Geospatial Reference Data Around a BIM Model: Scans, Rasters, and Tiles — declare how external point-cloud, raster, vector, service, and tiled inputs encode location.
Keep the boundaries clear
A schema can represent a relationship without proving a product route preserves it. An integration brief is not an executable mapping or an acceptance result. Coordinate systems, vertical references, civil station conventions, source authority, and project tolerances must come from the responsible project or jurisdiction.
Shape and mesh fidelity, product structure, reusable engineering meaning, encoding mechanics, named product routes, transfer failures, and formal acceptance belong to their respective portal categories. Use this category to define the spatial and BIM information a recipient needs; use those companion categories for representation, route, failure, or acceptance decisions.