Table: transport_network_component
Description (EN): This table represents transport network components. In the database's inheritance architecture, it acts as a direct sub-type of the component table. It does not store redundant descriptive columns; instead, it uses a shared primary key to inherit all high-level attributes (such as name, location, management type, and geometry) from its parent component record.
Column Structure
| Column | Data type | Definition | Example value | Constraint? | Geometry? | Comments |
|---|---|---|---|---|---|---|
id |
BIGINT | Unique identifier for the transport network component | 42 |
PK, FK | No | Primary key that also acts as a Foreign Key referencing component.id |
is_private |
BOOLEAN | [...] | [...] | - | No | - |
lanes_number |
BIGINT | [...] | [...] | - | No | - |
subtype |
VARCHAR | [...] | [...] | - | No | Possible values: PRIMARY_ROAD, PROVINCIAL, COUNTRY_SIDE |
Relationships
- Inherits from (Sub-type of):
component. Thetransport_network_componenttable is a specialized extension of thecomponenttable. - Belongs to:
enterprise(A component sub-type is linked to one enterprise) - Has many:
damage(A component sub-type can be affected by multiple damage over time)
!!! tip "Where is the rest of the data?"
To find the name, geographical location (geometry, town, country), or ownership details of a transport network component, you must join this table with the component record that shares the exact same id.
Example Query
Retrieve a list of all transport network components, including their names, towns, and spatial coordinates, by joining the table with its parent component entity:
tnc2.id,
c.name,
c.town,
ST_AsText(c.geometry) as coordinates
FROM
transport_network_component tnc2
JOIN
component c ON tnc2.id = c.id