The requirements for the structure of the RailTopoModel® are a direct consequence of the basic use cases.
- The ability to describe a network using a classical representation with nodes and edges.
- The ability to describe a network using an optimised representation for fast computations in operational environments along the lines of connexity.
- The ability to mix different description levels for an optimal representation of the network in question to fulfill the computational requirements most efficiently. This means especially to describe the operational hotspots in the most detailed level necessary whereas surrounding areas can be described at a higher level of aggregation using the minimum number of elements.
The structure of a network is defined using three core concepts:
The two concepts “NetElement” and “Relation” are essential for the topological structure whereas the two concepts “NetElement” and “ElementPartCollection” are used to describe the hierarchical structure between “NetElement” instances belonging to different description levels.
So, if the network is modelled as a graph, it has to be expressed that NetElements are related to other NetElements (as most of the objects in this model, this Relation object has an identifier and a validity range).
Topological structure (network)
- →Main Article: Topological structure (network)
Hierarchical structure (levels)
- →Main Article: Hierarchical structure (levels)
|What you should have learned|
|Please, enter a summary!|
|Chapter||RailTopoModel® Quick Start||RailTopoModel® modelling concepts||RailTopoModel® External References|
|Section||Levels of detail||Structure||Positioning|
|Subection||Topological structure (network)|