INDUSTRY FIELD GUIDE
Streetcar boarding-change data for AI rider information
Two stops may share a public name and serve opposite directions.
NAICS 485119 · Other Urban Transit Systems
Two stops may share a public name and serve opposite directions. An assistant that repeats a temporary boarding instruction without its direction and valid times could send the wrong rider to it. Census provides the transportation classification, and GTFS service alerts illustrate how service changes can identify affected entities. Census NAICS manual · GTFS service alerts
Sketch a fictional downtown loop. Give two opposite-direction stops the same display name but different IDs. Add an authorized boarding change with a time window. Give the other direction an expired notice. Ask the model to select the valid boarding information for a named trip and explain which record it used. Include an incomplete case where the direction is missing.
Exclude exact security access, staff names, live positions, and customer complaints. Use fictional stops or approved public feed records. Keep live passenger instructions outside the benchmark.
Describe a boarding information sample
Original Fiund exercise
A shared stop name does not erase direction and notice-validity differences
An original abstract streetcar loop uses fictional stops and trips. It contains no live position, staff, access detail or instruction for an actual passenger.
| Record | Source | What it records |
|---|---|---|
| STC1 | Stop map | Display name Central refers to EAST stop E1 and WEST stop W1, distinct IDs. Trip T-E is eastbound; T-W westbound. |
| STC2 | Current notice | Authorized day D, hours 10–12: eastbound E1 boarding changes to temporary E2. Scope names E1 and EAST only. |
| STC3 | Other notices | WEST change W1-to-W2 expired on D-1. Question Q1 asks T-E at 11 on D; Q2 says Central at 11 but omits direction. |
Question for the model
Which notice supports Q1, and can Q2 select the same temporary stop from its display name alone?
Show the reference answer and checks
STC1 and STC2 match T-E's eastbound direction, E1 identity and the day-D 10–12 validity window, supporting E2 within this fictional lookup. Q2 lacks direction, so Central could mean E1 or W1; it cannot inherit the eastbound change. STC3's westbound notice is expired and supplies no current W2 instruction. Preserve affected entity and interval rather than repeat a temporary stop across both directions.
- Applying an eastbound notice to a westbound stop with the same display name.
- Using an expired notice or filling an omitted direction from assumption.
Fields to preserve
- Trip, stop ID and direction
- Defines the affected entity.
- Notice authorization and valid interval
- Selects the source.
- Temporary stop and missing direction
- Limits the response.
Test another case
Ask about T-E at 13 on D. Require the temporary-window claim to expire instead of preserving E2 from the earlier answer.
Use invented stops or separately authorized public records. Exclude live dispatch and customer data; the benchmark supplies no real-time passenger direction.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.