Road — Notes

Provenance

• Source: CORENET X Code of Practice v3.1, Section 4 (BIM Data Representation — IFC+SG), pages 91–92.
• Source link: CORENET X — IFC-SG Glossary of Identified Components ↗
• Discipline: ARC · Authorities: URA, LTA
• 6 IFC binding(s), 19 parameter(s), 1 declarative-only binding(s).

IFC binding breakdown

• IfcCivilElement — subtypes: DRIVEWAY — 5 param(s), table format 6col.
• IfcBuildingElementProxy — subtypes: HUMP — 0 param(s), table format 6col. [no IFC+SG properties required]
• IfcCivilElement — subtypes: CARRIAGEWAY — 4 param(s), table format 6col.
• IfcSpace — subtypes: PARKINGACCESSWAY, FIREENGINEACCESSROAD, FIREENGINEACCESSWAY, VEHICULARSERVICEROAD — 2 param(s), table format 6col.
• IfcBuildingElementProxy — subtypes: ACCESSPOINT — 4 param(s), table format 6col.
• IfcCivilElement — subtypes: ROADKERB — 4 param(s), table format 6col.

Other input-limited parameters

These accept values from a defined list in the COP source table (not part of the global structural enums); see examples in parameters.json:

• Egress, Ingress, LoadingCapacity, Vehicular