Hello nice project.

I have a suggestion is it possible to add another docker compose file with a nginx container as cache so that the setup is easier? Or just add the nginx to the default compose file.

Kind regards, Finn

Hi,

thanks for your tool. It looks amazing and should be exactly what I need.

I just wanted to try it out, but can't get it to run. I built the Docker Image and started the Container with Port Forwarding of the Port 3000. Unfortunately nothing is served on the / endpoint.

So my questions are:

• Do I have to set configuration variables? (I saw the deployments/conf.example.env. Can you explain the different entries in there?)
• On which endpoint is the frontend application served?

Thanks already in advance! ~ Moritz

Example: https://tespace.traines.eu/tstp?from=8011160&to=8000096&vias=8010101&vias=8000244&vias=0&vias=0&vias=0&vias=0&vias=0&vias=0&vias=0&vias=0&datetime=2022-11-07T23%3A48

It shows many lines but no connection that ever arrives at the destination station. Btw: The Vias where added by the app. I just searched for Berlin - Stuttgart.

Currently just showing "Error 502: Failed requesting timetable data.".

HTTP 502 Connection not found (too far in the past) e.g. /journeys?departure=2022-09-19T08%3A00%3A00.000%2B02%3A00&from=692415&to=895914

{
	"isHafasError": true,
	"request": "{\"lang\":\"en\",\"svcReqL\":[{\"cfg\":{\"polyEnc\":\"GPA\",\"rtMode\":\"HYBRID\"},\"meth\":\"TripSearch\",\"req\":{\"getPasslist\":false,\"maxChg\":-1,\"minChgTime\":0,\"depLocL\":[{\"type\":\"S\",\"lid\":\"A=1@L=692415@\"}],\"viaLocL\":[],\"arrLocL\":[{\"type\":\"S\",\"lid\":\"A=1@L=895914@\"}],\"jnyFltrL\":[{\"type\":\"PROD\",\"mode\":\"INC\",\"value\":\"1023\"},{\"type\":\"META\",\"mode\":\"INC\",\"meta\":\"notBarrierfree\"}],\"gisFltrL\":[],\"getTariff\":false,\"ushrp\":true,\"getPT\":true,\"getIV\":false,\"getPolyline\":false,\"outDate\":\"20220919\",\"outTime\":\"080000\",\"outFrwd\":true,\"trfReq\":{\"jnyCl\":2,\"tvlrProf\":[{\"type\":\"E\",\"redtnCard\":null}],\"cType\":\"PK\"}}}],\"client\":{\"type\":\"AND\",\"id\":\"DB\",\"v\":21120000,\"name\":\"DB Navigator\"},\"ext\":\"DB.R21.12.a\",\"ver\":\"1.34\",\"auth\":{\"type\":\"AID\",\"aid\":\"n91dB8Z77MLdoR0K\"}}",
	"url": "https://reiseauskunft.bahn.de/bin/mgate.exe?checksum=3cfb0da25d0e81e49aa943346f120265",
	"statusCode": 404,
	"isClient": true,
	"code": "NOT_FOUND",
	"message": "journeys search unsuccessful",
	"hafasErrorCode": "H890",
	"hafasErrorMessage": "HAFAS Kernel: No connection found",
	"error": true,
	"msg": "HAFAS error: journeys search unsuccessful"
}

HTTP 502 Date outside timetable period e.g. /journeys?departure=2022-12-17T06%3A30%3A00.000%2B01%3A00&from=8000244&to=8702383

{
	"isHafasError": true,
	"request": "{\"lang\":\"en\",\"svcReqL\":[{\"cfg\":{\"polyEnc\":\"GPA\",\"rtMode\":\"HYBRID\"},\"meth\":\"TripSearch\",\"req\":{\"getPasslist\":false,\"maxChg\":-1,\"minChgTime\":0,\"depLocL\":[{\"type\":\"S\",\"lid\":\"A=1@L=8000244@\"}],\"viaLocL\":[],\"arrLocL\":[{\"type\":\"S\",\"lid\":\"A=1@L=8702383@\"}],\"jnyFltrL\":[{\"type\":\"PROD\",\"mode\":\"INC\",\"value\":\"1023\"},{\"type\":\"META\",\"mode\":\"INC\",\"meta\":\"notBarrierfree\"}],\"gisFltrL\":[],\"getTariff\":false,\"ushrp\":true,\"getPT\":true,\"getIV\":false,\"getPolyline\":false,\"outDate\":\"20221217\",\"outTime\":\"063000\",\"outFrwd\":true,\"trfReq\":{\"jnyCl\":2,\"tvlrProf\":[{\"type\":\"E\",\"redtnCard\":null}],\"cType\":\"PK\"}}}],\"client\":{\"type\":\"AND\",\"id\":\"DB\",\"v\":21120000,\"name\":\"DB Navigator\"},\"ext\":\"DB.R21.12.a\",\"ver\":\"1.34\",\"auth\":{\"type\":\"AID\",\"aid\":\"n91dB8Z77MLdoR0K\"}}",
	"url": "https://reiseauskunft.bahn.de/bin/mgate.exe?checksum=8186ee987934e7f8a2f9cd5d207c97ae",
	"statusCode": 400,
	"isClient": true,
	"code": "INVALID_REQUEST",
	"message": "journeys search: invalid date/time",
	"hafasErrorCode": "H9360",
	"hafasErrorMessage": "HAFAS Kernel: Date outside of the timetable period.",
	"error": true,
	"msg": "HAFAS error: journeys search: invalid date/time"
}

Currently, some interchange stations are retrieved from HAFAS journeys, the rest is up to the user. Interchange stations should be collected from additional sources, e.g.

• Intermediate stops from journeys
• Geographically relevant stations
• Stations where different lines and modes call
• Precalculation on offline timetable from GTFS download with negative transfer time Dijkstras etc to find relevant stations?

• Show warning if HAFAS finds journey not found by TSTP
• Display HAFAS-recommended journeys only when selecting them (just as TSTP-recommended journeys). Currently, it's difficult to tell, which red line belongs to which journey.

To save bandwidth and processing at HAFAS. Idea: Only request local transport (buses, trams...) if there are other nearby stations selected. More intelligent time window, especially for longer journeys.

Some connections that might be reachable are marked as redundant. Some that are superfluous are not marked as redundant. Also relevant for foot connections, which are not shown at all, if deemed redundant (for performance reasons).

Idea: Calculate Dijkstra for different transfer times (-15, -5, 0, 5, 15, etc)