Tabussen Trip Planner

Plan public transport journeys in Västerbotten, Sweden - including Umeå local traffic (Ultra) and regional routes (Länstrafiken Västerbotten).

Overview

This skill uses the ResRobot API (Trafiklab) to provide journey planning for Tabussen/Ultra. ResRobot is Sweden's national public transport API covering all operators including Länstrafiken Västerbotten.

Coverage:

• - Ultra (Umeå local bus traffic)
• Länstrafiken Västerbotten (regional buses)
• Connections to/from other Swedish regions
• Train connections where applicable

Commands

1. Search Location

Search for stops, stations, or points of interest.

CODEBLOCK0

Argument	Description
INLINECODE0	Location name to search for (append ? for fuzzy search)
INLINECODE2

Number of results to show (default: 5, max: 10) |

Output includes:

• - ID - The stop identifier (use this in journey search)
• INLINECODE4 - Official name of the stop
• INLINECODE5 - Latitude, longitude
• INLINECODE6 - Traffic volume indicator (higher = more traffic)

Search tips:

• - Use ? suffix for fuzzy/partial matching: INLINECODE8
• Exact search without ?: INLINECODE10
• Include municipality for precision: INLINECODE11

2. Journey Search

Plan a journey between two locations using their IDs.

CODEBLOCK1

Argument	Description
INLINECODE12	Origin stop ID (from search)
INLINECODE13

Destination stop ID |
| datetime | Optional: "18:30", "tomorrow 09:00", "2026-01-28 14:00" |
| mode | Optional: "depart" (default) or "arrive" |

Coordinate-based search:

./journey.sh "63.825#20.263" <to-id> [datetime] [mode]

Use lat#lon format for coordinates (WGS84 decimal degrees).

---

Understanding User Time Intent

Before searching, understand what the user wants:

Intent Types

User Says	Intent	How to Query
"now", "next bus", "how do I get to"	Travel Now	No datetime parameter
"in 30 minutes", "in 1 hour"

Depart Later | Calculate time, use depart mode | | "around 15:00", "sometime afternoon" | Around Time | Query with offset (see below) | | "arrive by 18:00", "need to be there at 9" | Arrive By | Use arrive mode | | "tomorrow morning", "on Friday at 10" | Future Time | Use specific datetime |

Handling "Around Time" Queries

When user wants options "around" a time, query 15-30 minutes earlier to show options before and after:

CODEBLOCK3

Relative Time Calculations

Convert relative times to absolute:

User Says	Current: 14:00	Query Time
"in 30m"	->	"14:30"
"in 1h"

-> | "15:00" |
| "in 2 hours" | -> | "16:00" |

---

LLM Response Formatting

When presenting journey results to users, use these emojis and formatting guidelines.

Emoji Reference

Emoji	Use For
INLINECODE24	Bus (Tabussen/Ultra)
INLINECODE25

Train | | walk | Walking segment | | clock | Time/duration | | clock1 | Departure time | | goal | Arrival time | | pin | Stop/station | | house | Origin (home/start) | | target | Destination | | warning | Delay or disruption | | check | On time | | arrows_counterclockwise | Transfer/change |

Response Structure

Always include these key elements from the tool output:

1. 1. When to leave - The actual time user needs to start (including walking)
2. Walking segments - Distance and time for any walking
3. Transport departure - When the bus actually leaves
4. Arrival time - When user reaches destination
5. Line number and direction - Which bus to take

Example Response Format

For a simple direct journey:
CODEBLOCK4

For a journey with transfer:
CODEBLOCK5

Walking Segment Details

Always show walking details:

• - Distance in meters
• Include walking in the "leave time" calculation
• Walk time estimate: ~100m per minute (normal walking speed)

Presenting Multiple Options

When showing journey options, make timing crystal clear:

CODEBLOCK6

---

LLM Workflow: How to Plan a Trip

Follow this workflow when a user asks for a trip:

Step 1: Understand Time Intent

Parse what the user wants:

• - "How do I get to..." -> Travel now
• "I need to be there at 18:00" -> Arrive mode
• "Sometime around 3pm" -> Query 14:30, show range
• "In about an hour" -> Calculate from current time

Step 2: Search for Both Locations

Search for origin and destination separately:

CODEBLOCK7

Step 3: Validate Search Results

Check each result carefully:

1. 1. Exact or close match? - If the name matches what the user asked for, proceed.

1. 2. Multiple results returned? - The script shows up to 10 matches. If the first result isn't clearly correct, ask the user to confirm.

1. 3. Name significantly different? - If user asked for "university" and result shows "Umeå Universitet", confirm with user.

1. 4. No results found? - Try alternative strategies (see below).

Step 4: Handle Ambiguous or Failed Searches

When results don't match or are ambiguous, ask clarifying questions:

CODEBLOCK8

When no results are found, try these strategies:

1. 1. Try with city name:

CODEBLOCK9

1. 2. Try common variations:

CODEBLOCK10

1. 3. Use fuzzy search (add ?):

CODEBLOCK11

Step 5: Execute Journey Search

Once you have confirmed IDs for both locations:

CODEBLOCK12

Step 6: Format Response

Use the formatting guide above to present results clearly. Always use actual numbers from the tool output - never estimate or speculate.

---

Query Formatting Rules

The search API is sensitive to formatting. Follow these rules:

Common Stop Names in Umeå

User Says	Search For
"Vasaplan", "centrum"	INLINECODE36
"Universitetet", "uni"

"Umeå universitet?" | | "NUS", "sjukhuset" | "Norrlands universitetssjukhus?" | | "Ikea" | "IKEA Umeå?" | | "Flygplatsen" | "Umeå Airport?" | | "Järnvägsstationen", "tåget" | "Umeå centralstation?" |

Regional Destinations

Destination	Search For
Skellefteå	INLINECODE42
Lycksele

"Lycksele busstation?" | | Vindeln | "Vindeln station?" | | Robertsfors | "Robertsfors centrum?" | | Holmsund | "Holmsund centrum?" |

Street Addresses

Include city name for better accuracy:

./search-location.sh "Storgatan 25, Umeå?"
./search-location.sh "Kungsgatan 10, Skellefteå?"

---

Examples

Example 1: Travel Now (Umeå Local)

User: "How do I get from Vasaplan to NUS?"

CODEBLOCK14

Response:
CODEBLOCK15

Example 2: Regional Journey

User: "I need to get to Skellefteå from Umeå tomorrow at 8"

CODEBLOCK16

Response:
CODEBLOCK17

Example 3: Arrive By Time

User: "I need to be at NUS by 08:00 tomorrow"

CODEBLOCK18

Response:
CODEBLOCK19

Example 4: From Address/Coordinates

User: "I'm at Storgatan 50 in Umeå, how do I get to IKEA?"

CODEBLOCK20

---

DateTime Formats

All times are Swedish local time (CET/CEST).

Format	Example	Meaning
(empty)		Travel now
INLINECODE47

"08:30" | Today at 08:30 |
| tomorrow HH:MM | "tomorrow 09:00" | Tomorrow at 09:00 |
| YYYY-MM-DD HH:MM | "2026-01-28 14:00" | Specific date |

---

Output Format

Journey Option (Raw Tool Output)

CODEBLOCK21

Transport Types

Type	Description
INLINECODE53	Tabussen/Ultra/Länstrafik bus
INLINECODE54

Regional bus (Länstrafik) | | JRE | Regional train | | WALK | Walking segment |

Operators in Västerbotten

Operator	Description
Länstrafiken Västerbotten	Regional and local buses
Ultra

Umeå local traffic (part of Länstrafiken) | | SJ | Long-distance trains | | Norrtåg | Regional trains |

---

Error Handling

"No locations found"

The search returned no results.

Strategies:

1. 1. Check spelling (Swedish: å, ä, ö)
2. Try with city name suffix
3. Use fuzzy search (add ?)
4. Try common alternative names
5. Ask user for clarification

"No journeys found"

No routes available.

Strategies:

1. 1. Check if service operates at that hour (late night limited)
2. Try different departure time
3. Suggest alternative nearby stops
4. Note that some regional routes have limited frequency

Common Issues

Issue	Solution
"Vasaplan" returns multiple	Use "Umeå Vasaplan"
Stop not found

Try fuzzy search with ? | | No late-night routes | Ultra has limited night service | | Long wait times | Regional routes may be hourly |

---

Quick Reference

Popular Umeå Stops (Ultra)

Stop	ID	Notes
Vasaplan	740020116	Central hub
Universitetssjukhuset (NUS)

740023840 | Hospital | | Universum | 740026881 | University area | | Umeå Busstation | - | Regional bus departures | | Västerslätt Centrum | 740045407 | Western suburb |

Key Regional Stops

Stop	ID	Notes
Skellefteå busstation	740000053	Regional hub
Lycksele busstation

- | Inland hub | | Vindeln station | - | Train connection | | Robertsfors centrum | - | Coastal route |

---

API Details (For Script Development)

This skill uses ResRobot API v2.1 from Trafiklab.

Base URL: INLINECODE57

Endpoints:

• - Stop lookup: INLINECODE58
• Journey planner: INLINECODE59

Key Parameters:

• - accessId - API key (required)
• INLINECODE61 - json or xml
• INLINECODE62 / destId - Stop IDs
• INLINECODE64 / time - Travel date/time
• INLINECODE66 - 1 for arrive-by searches

Get API Key: Register at https://developer.trafiklab.se

---

Notes on Västerbotten Traffic

Ultra (Umeå Local)

• - Frequent service in central Umeå
• Lines 1-9 are most common
• Night buses (N-lines) on weekends
• Real-time info available in app

Länstrafiken (Regional)

• - Line 100: Umeå - Skellefteå (frequent)
• Line 12/20: Coastal routes
• Lines 30-49: Inland routes
• Frequency varies by route

Tips for Users

• - Vasaplan is the main hub for both Ultra and regional
• Many regional buses depart from Vasaplan, not train station
• Train station (Umeå C) is separate from bus station
• IKEA and Avion have good bus connections

---

When to Ask Clarifying Questions

Always ask when:

1. 1. Search returns no results:

- "I couldn't find [location]. Could you provide more details?"

1. 2. Multiple plausible matches:

- "I found several stops matching '[query]': [list]. Which one?"

1. 3. Result name very different from query:

- "You asked for '[user query]' but I found '[result name]'. Is this correct?"

1. 4. User request is vague:

- "From where in Umeå? Vasaplan (central), or another location?"

1. 5. Time is unclear:

- "When do you want to travel? Now, or at a specific time?"