Railway data - Traffic management systems

Open data API in a single place

Provided by Lantmäteriet

Get early access to Railway data - Traffic management systems API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.11.12 00:00
Created
2012.10.31
Available languages
English
Keywords
trafikslag: järnväg, område: transport
Quality scoring

Dataset description

Traffic management system means the technical or manual safety solution used to monitor and control a runway. There are several different systems. system H Based on the presence of complete signal switchgear at the operating sites and line blockage on the line. The operating sites are either guarded or closed. system M Based on the line being monitored by two signallers without the use of line blocking or radio blocking. The operating sites can be monitored by manual methods with the support of simple signal switchgear, but can also have complete signal switchgear. It may happen that operational sites are unattended, guarded or closed. system S is based on the line being monitored by manual means by only one signaller. There are no operating sites, but there are line locations without main tracks. The boundaries of these lines are marked with boards. Inside these boards, all tracks are sidings. The line otherwise has main tracks, also past other line locations. No train journeys can be made in system S, but all movements on the line shall take place as a blockage. system R Based on the line and operating locations being monitored by radio-blocking. The operating sites are either guarded or closed. system F Based on the line and operating locations being monitored by manual means by only one signaller. On the operating sites there are only sidings, and all movements there take the form of visibility movement. The operating sites are guarded. system E1 Based on the monitoring of the line and the operational sites using level 1 of the European Control-Command System ERTMS. The operating sites are guarded. system E2 Based on the line and operational locations being monitored using level 2 of the European Control-Command System ERTMS. The operating sites are guarded. system E3 Based on the European Control-Command System ERTMS level 3 monitoring of the line and operational sites. The operating sites are guarded.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks