Linz Public Transport

Step 1: Resolve Base URL

• Use user-provided base URL first.
• Otherwise use LINZ_TRANSPORT_API_BASE_URL if available.
• If neither exists, use http://www.linzag.at/linz2.

Step 2: Present Output

• Sort by countdownInMinutes ascending if needed.
• Show the next 5-10 departures unless user asks for more.
• Include both relative (countdownInMinutes) and absolute (time) times.
• Keep field names stable when returning JSON.

Error Handling

• If stop search returns empty list, suggest nearby spellings and retry with a shorter query token.
• If multiple stop matches are returned, rerun with explicit --stop-id or use next ... --pick-first only when ambiguity is acceptable.
• If departures response is empty, state that no upcoming departures are currently available.
• If HTTP request fails, report status code, endpoint, and retry guidance.
• If EFA response includes a message code, include that code in diagnostics.

Minimal Examples

python {baseDir}/scripts/linz_transport.py stops "taubenmarkt"
python {baseDir}/scripts/linz_transport.py departures --stop-id 60501160 --limit 10
python {baseDir}/scripts/linz_transport.py next "taubenmarkt" --limit 10 --pick-first

python "{baseDir}/scripts/linz_transport.py" stops "taubenmarkt"
python "{baseDir}/scripts/linz_transport.py" departures --stop-id 60501160 --limit 10
python "{baseDir}/scripts/linz_transport.py" next "taubenmarkt" --limit 10 --pick-first