Linz Public Transport

Use this skill to interact with Linz Linien EFA endpoints:

• - INLINECODE0
• INLINECODE1

Read endpoint details in {baseDir}/references/endpoints.md before implementation.
Use {baseDir}/scripts/linz_transport.py as the default execution path.

Workflow

1. 1. Resolve the API base URL.
2. Run the script subcommand that matches the task.
3. Return a compact, user-facing summary.

Primary Tooling

• - Script path: INLINECODE4
• Runtime: Python 3, standard library only.
• Base URL input:

Preferred commands:

• - Search stops:

• - Fetch departures by stop ID:

• - Resolve stop and fetch departures in one call:

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

CODEBLOCK0

CODEBLOCK1