Class Ifc4::IfcGeographicElementType

Nested Relationships

This class is a nested type of Struct Ifc4.

Inheritance Relationships

Base Type

Class Documentation

class Ifc4::IfcGeographicElementType : public Ifc4::IfcElementType

Definition from IAI: An IfcGeographicElementType is used to define an element specification of a geographic element (i.e. the specific product information, that is common to all occurrences of that product type).Geographic element types include for different types of element that may be used to represent information within a geographical landscape external to a building. Within the world of geographic information they are referred to generally as ‘features’. Geographic element types includes for many possibilities:

linear elements such as sections of a roadway (including carriageway/pavement, verge, median, marker line, kerb etc.), path, river, stream

connections and junctions including traffic roundabouts, T junctions, 4 way junctions

point features such as street lighting, seating, bus shelters, signage, trees

linear features such as layby’s

area features such as ponds, lakes, woods and forests

The specification of the specific types are given by the inherited attribute IfcElementType.ElementType given as an IfcLabel.

NOTE This is due to the range of choices of element type thyat are available and their expression in different languages. It is not considered possible to create a reasonably full list of types within an enumeration. It is suggested that selection of the relevant type be drawn from an available ‘feature catalog’.

HISTORY New entity in Release IFC2x Edition 4.

Feature Catalog Use Definition

Geographic element types are frequently identified in feature catalogs that are produced for particular purposes.The IfcGeographicElementType entity enables the continued use of existing feature catalogs through capture of their identity and attributes.

Information from feature catalogs might be captured in various ways:

via property sets, some of which will be specifically defined within the IFC property set catalog whilst others will be created for local use; this is the form of capture that is expected to be most widely used

through use of the IFC classification model whereby features might be identified through a classification notation and additional description; in which case, any further attributes required would still need to be captured in property sets.

Public Functions

::Ifc4::IfcGeographicElementTypeEnum::Value PredefinedType() const

Predefined types to define the particular type of the geographic element. There may be property set definitions available for each predefined type.

void setPredefinedType(::Ifc4::IfcGeographicElementTypeEnum::Value v)
const IfcParse::entity &declaration() const
IfcGeographicElementType(IfcEntityInstanceData *e)
IfcGeographicElementType(std::string v1_GlobalId, ::Ifc4::IfcOwnerHistory *v2_OwnerHistory, boost::optional<std::string> v3_Name, boost::optional<std::string> v4_Description, boost::optional<std::string> v5_ApplicableOccurrence, boost::optional<IfcTemplatedEntityList<::Ifc4::IfcPropertySetDefinition>::ptr> v6_HasPropertySets, boost::optional<IfcTemplatedEntityList<::Ifc4::IfcRepresentationMap>::ptr> v7_RepresentationMaps, boost::optional<std::string> v8_Tag, boost::optional<std::string> v9_ElementType, ::Ifc4::IfcGeographicElementTypeEnum::Value v10_PredefinedType)

Public Static Functions

const IfcParse::entity &Class()