GA and HTA file: Is it planned to publish this data on the basis of the municipalities?
No, we cannot publish this data at the community level, as we do not know the allocation to the community. We made this list based on the customer’s address and he does not indicate his municipality there.
However, you can do this in the same way as SRF:
The information on the interactive map and the values in the article are taken from the Direct Transport Switzerland data set (opentransportdata.swiss) for the distribution of GA and Half-Fare travelcard between 2012 and 20116. In a first step, the assignment to the data of the permanent resident population valid at that time was based on the postal code (31.12.2015). The GWR correspondence table published by the FSO (as at 01.01.2017) was used for the subsequent comparison between postal code and municipality. This made it possible to establish a direct link to the generalised municipal boundaries published by the FSO as of 1.1.2017 and to the spatial structure of Switzerland. Due to averaging data for postal codes with less than 20 subscriptions, the map may be slightly distorted, especially in small communities.
Details on this https://srfdata.github.io/2017-09-sbb-ga-halbtax/#sbb__bfs_raumgliederungen
lante track is 4, but the current track is now 3 due to changes. We recommend that you only map at the level of the stops.
How does the data from the sensor reach the open data platform öV Schweiz at the transport company?
We cannot go into detail here, as this also differs depending on the TRANSPORT COMPANY. The big pictransport companyre below shows the rough overall contexts from the data sources to the publication of the information/data:
The complexity and variability of the transport companies (TRANSPORT COMPANY) is not shown on the Big Pictransport companyre. However, there are many solutions and different characteristics, so one TRANSPORT COMPANY uses one Excel, while another TRANSPORT COMPANY uses a fully integrated system for all layers.
Basically, however, a distinction can be made between three shifts in the transport companies:
1st stops: form the foundation of public transport and are therefore identified and managed throughout Switzerland by the national DiDok system.
2nd Timetable system: Each transport company creates the timetables that are to be communicated to the customer. On the one hand, the TRANSPORT COMPANY itself will publish the timetables (e.g. as a poster at the stop), on the other hand, the timetable data must be included in a larger pool.
The (operational) control system is used for ad hoc planning, i.e. changes to the original planning are either recorded (e.g. delays) or actively made (e.g. detours). This layer also contains very simple systems (e.g. a mobile phone), which only records the current position and calculates the forecast.
The fact is that there are numerous systems at the numerous transport companies that can behave differently in the processing as well as in the provision of data. This heterogeneity is relativized and standardized in intermediate steps.
Before the data is published, it is collected. In a first step, the data is combined in a regional data collector or a regional data hub. Here, too, the big pictransport companyre has been simplified, as the regional systems can include fully integrated systems (e.g. interconnected systems), systems from a nationally operating company (e.g. Postbus) or a hub that collects data nationwide (e.g. Bernmobil). Here, too, there is more than one system per shift (exception: stops), but not as many as with the source systems.
Sooner or later, however, the data will land in the three national systems DiDok (stops), INFO+ (timetable) or CUS (real-time). Currently, only DiDok and INFO+ can be assumed to have received the corresponding data from all Swiss universities of technology. At CUS, only a selection of the TRANSPORT COMPANY currently provide real-time data. There are two reasons for this:
- not every TRANSPORT COMPANY has an (operating) control system.
2.not every TRANSPORT COMPANY, which has an (operating) control system or not every data hub, provides data in the desired format.
The aim, however, is that, over time, as many Swiss universities as possible will deliver real-time data.
The data are transferred from the national collection systems into two publication systems:
1st cube: cube prepares the data so that they can be neatly published on fahrplanentwurf.ch (the annual timetable to check before it is valid) and on fahrplanfelder.ch (the valid annual timetable).
2nd Open Data Platform: There is also an upstream system (similar to Kubus) that prepares and merges the data, but it is fully integrated so that all data can be published on opentransportdata.swiss in a consolidated form. The platform also brings together data from the different layers of national systems so that output is integrated accordingly.
Where can I find the formation of the trains?
Unfortunately, the formation is not currently available “open”. The release of this data is currently not planned. If this should change, you as a registered platform user will be the first to know by e-mail. Another way to stay up to date is to subscribe to our Twitterfeed.
You can find the SBB formation here: data.sbb.ch
Why doesn’t the platform deliver the shapes.txt file?
This is about the (changed) route of the replacement trains. Route progressions can be exported to the file shapes.txt (https://developers.google.com/transit/gtfs/reference/#shapestxt).
BUT: We use OpenStreetMap as GIS. We are not allowed to upload this data to Google due to copyright restrictions, therefore the export of the file is deactivated. Since the data is also used by Google, an activation is unfortunately not possible.