JvSFS 2008:7 Annex 1, reference [101] defines different terms that appear in JvSFS. The track is divided into main tracks and sidings depending on how you want to monitor and manage traffic activities on the tracks.
Main tracks are tracks intended for secured movement, such as a train running on a signal-regulated line or location of operation.
• Secured movement is a form of movement on main tracks when travelling by train or blockage, which presupposes that the route is prepared and free from traffic activities and obstacles.
• An operating location is an area defined from the line of the runway which can be monitored by signallers in more detail than is required for the line.
• A signaller is a person who supervises and directs the traffic activities on main tracks and specified sidings.
Main tracks are divided into:
• The normal main track: the main track of an operating location leading from the operational site boundary through gears in normal mode. At an unattended operating location, the normal main track is used in secured movement.
• Different main tracks: main track in an operating location other than the normal main track.
Sidings are tracks other than main tracks. A track that is not normally signal-regulated, for example at operational locations.
The data product has stretch distribution and connects to the network with reference from node to node with distance in meters to both the starting and end positions of the route in the direction of the track link.
Related Objects
• Sat @-@ roads, — LÖ @-@ road must be established at the same time as main tracks or that the decision exists to exclude the specific main track from being LÖ @-@ road.
• FOMUL @-@ metering, String, speed exceeding %, Track U/N/E, Line class available only on main tracks.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.