buildingSMART / buildingSMART/IFC4.x-development
Incorrect coordinate order
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
The coordinate order of the geographic reference position in the example for IfcRigidOperation [E.7.2 - Geographic Referencing Rigid Operation](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/annex_e/placements-and-gis-referencing/geographic-referencing-rigid-operation.html) is incorrect. Accoring to [EPSG:4258](https://epsg.io/4258) the coordinate order is latitude, longitude.
Current coordinate order:
`#302=IFCRIGIDOPERATION(#21, #301, IFCPLANEANGLEMEASURE(14.0902217), IFCPLANEANGLEMEASURE(46.3623297), 475.);`
Corrected version:
`#302=IFCRIGIDOPERATION(#21, #301, IFCPLANEANGLEMEASURE(46.3623297)46.3623297, IFCPLANEANGLEMEASURE(14.0902217), 475.);`
Contributor guide
Research direction
Open the linked E.7.2 Geographic Referencing Rigid Operation example and compare its coordinate order with EPSG:4258. Verify the intended latitude and longitude values, then correct the displayed IFC rigid-operation example and check the rendered specification for the corrected order.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100