buildingSMART / buildingSMART/IFC4.x-development

IfcExternalSpatialElementTypeEnum

Open
#857 0 comments 0 reactions 0 assignees View on GitHub
after-NWI iso-compatibility iso-Te proposal
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

## Proposal

Type | Definition
---|---
EXTERNAL_FIRE | Space occupied by external fire safety zone (?)
EXTERNAL_ADJACENT | Space occupied by a neighboring ~~building~~ construction work
LAND_PARCEL | Space occupied by building plot or land parcel for example as documented by cadastral registries

Allow relationship of Pset_LandRegistration to IfcExternalSpatialElement.LAND_PARCEL

## Background

Pretty sure the description on EXTERNAL_FIRE is wrong:

> **EXTERNAL_FIRE**
>
> Space occupied by a neighboring ~~building~~ construction work.

We should probably add that though as EXTERNAL_ADJACENT (Specifically not naming it ADJACENT_BUILDING to be a bit domain agnostic).

I don't know what the definition of EXTERNAL_FIRE should be, is that some sort of safety zone?

There has been some form of consensus to not add geometry directly to IfcSite. ~In that line of thinking I'm inclined to say that this entity should be the designated entity to represent a building plot or lot~.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.