Object positioning in the network
The RailTopoModel data structure is centered around the network. The Network is used as the main reference system for positioning of arbitrary information objects. These information objects are modelled as a generic class called “NetEntity”.
This layer allows the user to project objects and entities on the topology, by referencing topology elements. Three types of generic entities, that can be located on the network, were identified:
- Spot entity: Happens at a point (e.g.: signals, buffer stops, ETCS balise, etc.)
- Linear entity: Happens along a path (e.g.: platform, speed limit, ballast renewal, etc.)
- Areal entity: Happens on a sub network (e.g.: catenary cases, track circuits zones, switches, stations, tunnels, bridges, etc.)
One entity can have more than one location.
To define all types of entity, a generic class is defined: NetEntity. This class defines a general relation with a shared location to define the position on the network. The location of each entity on the network is defined using the intrinsic reference of net element. Thus, three types of entity are defined:
Each “NetEntity” instance possesses an unspecified number of “EntityLocation” instances. Each “EntityLocation” instance is specialised either as “AreaLocation”, “LinearLocation” or “SpotLocation”.
Using an “AreaLocation” instance for connecting to network means that the “NetEntity” in question is related to a subset of “NetElement” instances which together resemble an area or a sub-network.
A connection based on a “LinearLocation” instance means that the “NetEntity” in question is related to a linear segment of the “Network”.
A connection based on a “SpotLocation” means that the “NetEntity” in question is related to a “NonLinearElement” building block of the “Network”.
An areal object is a sub graph (a continuous fraction of the network), that is comprehended as an object.
It is defined analogously to spot- and linear entities, by listing the ElementParts member of the location.
The name areal object was chosen because most practical examples resemble an area. In the context of RailTopoModel an “AreaLocation” instance defines a subgraph (a continuous fraction of the network).
It is produced by listing the ElementParts member of the location.
If a nonlinear element is included in a collection, then the whole element is included. If only one track edge is concerned, then the entity should be referenced to the track edge at position 0% (or 100%) to show it happens only on this track edge. It must be checked that the objects included in the areal location form a connected sub graph (no independent parts) and that no object is listed twice.
This type is located by the type of class: AreaLocation. The area location, in this case, is defined by a set of net elements with a pair of positions (beginning and end in intrinsic reference) for all elements.
Many “NetEntity” instances can be seen as paths.
To describe a path location, a start point, an end point and an ordered list of every encompassed element, is needed.
The start and end points are point locations, thus either a nonlinear element or a point along a track edge.
The path should be a topological path, meaning that at each nonlinear element only one exit direction can be taken.
If the start- or end point is a nonlinear element, this element is fully encompassed within the path.
The correct ordering of the list should be checked against the topology definition of the network. This could be the task of a validator. The orientation of the path on each track edge can be deduced from the order of the crossed nonlinear elements.
This type is located by the type of class: LinearLocation. The linear location, in this case, is defined by an ordered set of net elements with a position (in intrinsic reference) for the first and last element.
A spot entity can be either a nonlinear element (happens “in” the element) or an entity along a section of rail/section of line at a certain distance. If it happens in the element, it encompasses the whole nonlinear element. It should be described as track edge X at 0 (or 100%), meaning it happens at the elements centroid, but only on this particular track edge.
If it happens along a track edge at a certain distance, it is necessary to defined whether this entity happens directly on the track edge, or alongside the track edge; and if the entity occurs in both directions or only in one. These types of entities are located on the network by the type of class: SpotLocation. It is possible to have more than one location for a punctual entity:
- Multiple location (on multi-track) on the network for the same level (micro,…).
- Multiple location because the entity is located on different levels.
|What you should have learned|
|Back To||Previous Chapter||Next Chapter|
|RTM Modeling Concepts||Positioning||-|