buildingSMART / buildingSMART/IFC4.x-development

WorldCoordinateSystem talks about a project base point and survey point

Open
#743 0 comments 0 reactions 0 assignees View on GitHub
allocated allocated-gis ifc-update-out
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

From the docs of IfcGeometricRepresentationContext: https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcGeometricRepresentationContext.htm

> If an geographic placement is provided using [IfcMapConversion](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcMapConversion.htm) then the WorldCoordinateSystem atttibute is used to define the offset between the zero point of the local engineering coordinate system and the geographic reference point to which the [IfcMapConversion](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcMapConversion.htm) offset relates. **In preferred practise both points (also called "project base point" and "survey point") should be coincidental**. However it is possible to offset the geographic reference point from the local zero point.

This sounds like Revit specific language and doesn't make sense to me. Other software don't have a "project base point" and "survey point". In real life your model has a 0,0,0 point (which IfcMapConversion handles any conversion to map coordinates) and that's it. There isn't a single special "survey point".

Proposal: remove this language and deprecate WorldCoordinateSystem

Ping @pjanck

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked IfcGeometricRepresentationContext and IfcMapConversion documentation, focusing on the WorldCoordinateSystem wording and its relationship to the geographic reference point. Determine the agreed replacement wording and whether deprecating WorldCoordinateSystem is in scope; done requires an accepted specification decision and corresponding documentation update.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.