# Block

| Field | Value |
| --- | --- |
| Discipline | — |
| Authorities | — |
| Pages (CoP 4th Edition) | 242 |
| IFC Bindings | 1 |
| Parameters | 4 |
| Source | CORENET X Code of Practice 4th Edition |
| Source link | [View on CORENET X ↗](https://info.corenet.gov.sg/ifc-sg/glossary-of-identified-components?id=e9cc50c3-a9e5-44ad-9f6a-87579e22dd2f) |

## IFC Bindings

| # | IFC Entity | Predefined subtype(s) | Params | Notes |
| --- | --- | --- | --- | --- |
| 1 | `IfcSite` | — | 4 |  |

## Parameters

See `parameters.json` for the machine-readable, binding-grouped data (with resolved `allowed_values` for input-limited fields). Each IFC binding is one classification (entity + SubType): its parameters apply only to model elements of that classification, so a binding with no such element in the model asks nothing. **Mandatory** is what the component's own page note says: Y = must be filled on those elements, N = optional, blank = the page is silent; the note itself is `glossary_mandatory_note`.

| IFC Entity | S/N | Property | Type | Unit | Input limited | Mandatory | Example |
| --- | --- | --- | --- | --- | --- | --- | --- |
| `IfcSite` | 1 | CXBlockID | Integer |  |  | Y | 1; 2; 3 |
| `IfcSite` | 2 | BuildabilityBlock | Text |  |  | N | SUPERSTRUCTURE-2-RNL; BASEMENT-1-OTHERS |
| `IfcSite` | 3 | PurposeGroup | Integer |  | Y | Y | 1; 2; 3; 4; 5; 6; 7; 8 |
| `IfcSite` | 4 | BuildingType | Text |  | Y | Y | Refer to table above |