aschuma/vvs_direct_connect

A Docker-based REST service that offers real-time departure information for a dedicated VVS connection of the local public transport system in Stuttgart

vvs_direct_connect's Issues

Update GH Workflows

Transfer Mode Support

The application currently only supports direct connections between two VVS train stations.

The requirement now is to also support connections with transfers. This new behavior should be switchable via a feature flag, thus keeping the existing functionality untouched.

Furthermore, addresses within the VVS area should be supported as origins and destinations. If pedestrian paths are included, they should be filtered out. In the case of necessary transfers, only the first S-Bahn or tram line (referred to as "transportation_number") should be returned in the existing field. In a separate new structure, the intermediate stations and lines will be returned.

Note
The format of addresses such as "Konrad Adenauer Str 32 (Staatsgalerie)" looks like this: "streetID:1500001775:32:8111000:51:Konrad-Adenauer-Straße:Stuttgart:Konrad-Adenauer-Straße::Konrad-Adenauer-Straße:70173:ANY:DIVA_SINGLEHOUSE:3513826:755185:NBWT:VVS:0"
To find a value for an address, enter the origin and destination in the VVS timetable information (https://www3.vvs.de/), submit as search, decode the browser URL and format the deeplink parameter with a JSON formatter.

vvspy readme notice

Hey @aschuma

cooles Projekt!
Hättest du was dagegen, dass ich es auf dem Readme von vvspy erwähne?