buildingSMART / buildingSMART/IFC4.x-development
Standardised psets for storing data about surveyed points (IfcAnnotation)
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
IFC4X3 introduces Pset_AnnotationSurveyArea which is great (seems to be missing the applicable type restriction to `ASBUILTAREA`?).
Notably missing is properties related to individual survey points. Proposal to add Pset_AnnotationSurveyPoint. The following properties are useful for points:
- Easting
- Northing
- Elevation
- Scale
- Latitude
- Longitude
(attributes Name and Description can cover the point's number / description / code as necessary)
Maybe the infra team has already thought about this but it would be good to standardise how this type of data is stored for survey points. Maybe eastings / northings / el is already stored by nature of the object placement XYZ, but it doesn't answer how to store scale per point, as well as whether or not it is worthwhile to store lat / longs or if we rely on the reading software to having reprojection capabilities.
Contributor guide
Assessment
This issue has not been assessed yet.