SASA has decided to give the community all the following data under the CC-3.0-BY-SA licence. Feel free to be innovative and creative and try it out!
- Planned data (Zipfile and Webservice)
- Realtime positions (JSON Webservice)
- Realtime stationboard informations (Webservice)
- Latest service related news (XML, Json Webservice)
- Routing engine (XML Webservice)
The zipfile with the planned data is structured in a format called VDV 452. The files themselves are created following the instructions given in VDV 451. Even if there are many files which in 452 do not exist, they are empty and should not have any impact on the other files.
If you want to implement GTFS, then use this opensource tool to create some GTFS for your application.
Some developers might be interested in web services rather then in files and therefore we have decided to put up some webservice to provide the planned data, too. On this site you find some documentation about the webservice and learn how to use the data to build your application. Examples can be found here.
The real-time positions are available under the URL realtime.opensasa.info.
This is only a short documentation - don't think that it is complete:
All the requests return some geojson.
This allows you to query the service for all vehicles on line number 4 and variant 1. "Linenumber" and "variantnumber" can be extracted from the vdv-webservice or the vdv-zip-file (REC_LID).
You can also query a list of lines:
You can query the web service asking for all positions, by using this URL:
Other documentation will be available as soon as possible.
Real-time stationboard informations
The real-time stationboard information is available under the URL:
This webservice has one required parameter, namely ORT_NR. This represents the number of the bus stop, and has to be extracted from the webservice of the planned VDV-data or the VDV-zip-file (REC_ORT).
An example would be:
It shows you all departures from the station number 5324 from now until the end of the day.
There are other optional parameters, which are
The ALL parameter is not compatible with the number of lines to display and will always show you every departures during the whole day.
If the type is set to plaintext (formatted as csv with separator ;) with the following columns:
- Name of this bus stop
- Number of the line
- Arrivaltime at this station
- Departuretime at this station
- Last bus-stop of this trip
- Delay in minutes (if there is 0, it is in time. If there is nothing, no information is known about this trip)
The "json" and the "jsonp" give you a list of objects, with the following parameters:
- station_name: is the name of this station
- lidname: is the name of the line
- last_station: is the name of the last station from the trip
- arrival: is the arrival time at this station
- departure: is the departure from this station
- delay: is the delay in minutes. If the delay is "null", then no information abou this bus is present in the system.
The JSONP type requires the jsonp parameter, otherwise it will return json formatted information.
The file which generates all these informations is available under a GPL v3 Licence on github.
Service related news
The news are available in different formats. The first method to get them is via RSS-feed. Its URL is:
The title specifies, which area is affected by the news. BZ stands for Bolzano, and ME stands for Merano. If any of these two is specified, then the news are affecting both areas.
The second method is to get the news as a json formatted string. In this case, you have a list of news-objects. The objects are composed by a unique id, titel_de, titel_it, nachricht_de, nachricht_it, gebiet (0=both, 1=Meran, 2=Bolzano), linienliste (list of lines interested), lastmod (last modification time).
You can set some parameters such as city (0, 1, 2) or id (to get only one news item).
This Service offers the same possibility for "jsonp" too. You have to add the parameter callback for receiving all information in "jsonp".
The URL herefor is:
An example for "jsonp" could be:
The third and last method is to get the results as a xml-formatted string. The service returns a list of news, every news item has the same tags as the "json"-object.
Also with this method it is possible to put the parameters city (0, 1, 2) and id. If you request a single news item by id, only one news item is returned, and it is not incorporated in a list.
The URL for this service is:
SASA made available their routing engine to the public. The engine's URL is http://xml.opensasa.info/bin/extxml.bin. There are many parameters, which you can find in this documentation. Some examples for xml to query the interface are included, too. SASA has created a little code snippet to show you how to use the routing engine, which can be found here.