Feed status · checked 2026-09-05
Waltti (Kajaani)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Kainuu, Finland.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 3 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid url (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
851 of 910 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +23 points in its category
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Invalid url (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 851 of 910 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 273 days.
- Published accessibility data
- Accessibility information is stated for 6.5% of stops and 83.3% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 9 kinds of issue across 1536 instances (740 error, 770 warning, 26 informational).
Service data covers the next 273 days.
6% of stops state wheelchair accessibility (2% marked accessible, 5% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
6% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Paakki ap, Paakki ip, Juurikkalahti ap, Juurikkalahti ip, Sipinen ap, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Vesikkotie/Nurmestie th.", "Torvelantie/Häikiönmäentie E", "Torvelantie/Häikiönmäentie P", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 910 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (green)
- 11 (green)
- 12 (green)
- 13 (green)
- 14 (green)
- 16 (green)
- 16K (green)
- 2 (green)
- 3 (green)
- 4 (green)
- Paakki ap (green)
- Paakki ip (green)
- Pohjavaara ap (yellow)
- Pohjavaara ip (orange)
- Juurikkalahti ap (green)
- Juurikkalahti ip (green)
- Sipinen ap (green)
- Sipinen ip (green)
- Ontojoki ap (orange)
- Ontojoki ip (green)
- SotKatti (teal)
- 6 (green)
- 6K (green)
- 7 (green)
- Pali (red)
| Route | Type | Line color |
|---|---|---|
| 1 Linja 1 | Bus | green |
| 11 Linja 11 | Bus | green |
| 12 Linja 12 | Bus | green |
| 13 Linja 13 | Bus | green |
| 14 Linja 14 | Bus | green |
| 16 Linja 16 | Bus | green |
| 16K Linja 16K | Bus | green |
| 2 Linja 2 | Bus | green |
| 3 Linja 3 | Bus | green |
| 4 Linja 4 | Bus | green |
| Paakki ap Paakki - Sotkamo | Bus | green |
| Paakki ip Sotkamo - Paakki | Bus | green |
| Pohjavaara ap Rimpilänniemi - Pohjavaara - Tenetti - Sotkamo | Bus | yellow |
| Pohjavaara ip Sotkamo - Tenetti - Pohjavaara - Rimpilänniemi | Bus | orange |
| Juurikkalahti ap Eevala - Juurikkalahti - Sotkamo | Bus | green |
| Juurikkalahti ip Sotkamo - Juurikkalahti - Eevala | Bus | green |
| Sipinen ap Sipinen - Sotkamo - Tenetti | Bus | green |
| Sipinen ip Tenetti - Sotkamo - Sipinen | Bus | green |
| Ontojoki ap Ontojoki - Sotkamo - Tenetti | Bus | orange |
| Ontojoki ip Tenetti - Sotkamo - Ontojoki | Bus | green |
| SotKatti Paikallisbussi SotKatti | Bus | teal |
| 6 Linja 6 | Bus | green |
| 6K Linja 6 | Bus | green |
| 7 Linja 7 | Bus | green |
| Pali Palveluliikenne | Bus | red |
List every stop
- Vuottolahti P
- Hietalahti E
- Hietalahti P
- Raittisentie P
- Raittisentie E
- Vuottolehden koulu E
- Vuottolahden koulu P
- Saloranta E
- Saloranta P
- Kotikangas E
- Kotikangas P
- Valtalanniemi E
- Valtalanniemi P
- Kuru E
- Kuru P
- Juurikkaranta E
- Juurikkaranta P
- Suonpää E
- Suonpää P
- Saarela E
- Saarela P
- Ruohoniementie E
- Ruohoniementie P
- Kuusiranta th E
- Kuusiranta th P
- Alanko E
- Alanko P
- Oikotie P
- Oikotie E
- Ouluntie E
- Ouluntie P
- Pentinpuro E
- Pentinpuro P
- Rauhaniemi E
- Rauhaniemi P
- Siirtola E
- Siirtola P
- Pussila E
- Pussila P
- Käkilahti E
- Käkilahti P
- Erkkilä P
- Erkkilä E
- Käkisaari E
- Käkisaari P
- Partala E
- Partala P
- Rauharanta E
- Rauharanta P
- Hina E
- Hina P
- Ojanperä E
- Ojanperä P
- Kota E
- Kota P
- Ojanperä salmenrannan th
- Ojanperä (Vaala)
- Sipinen Malmilan th P
- Sipinen Malmilan th E
- Koukopuro P
- Koukopuro E
- Sipinen P
- Sipinen E
- Matalalehto P
- Matalalehto E
- Lepikko P
- Lepikko E
- Pirttisuo P
- Pirttisuo E
- Lemetinvaara P
- Lemetinvaara E
- Haarala P
- Haarala E
- Kärnälä P
- Kärnälä E
- Miinoanjärvi P
- Miinoanjärvi E
- Petäjävaara P
- Petäjävaara E
- Mutkala P
- Mutkala E
- Onnenaho E
- Kuohuvaara E
- Kuohuvaara P
- Onnenaho P
- Poromäki th P
- Poromäki th E
- Mustikkamäki P
- Mustikkamäki E
- Kaitainsalmi E
- Kaitainsalmi P
- Pelkolanvaara P
- Pelkolanvaara E
- Timola P
- Timola E
- Jataniemi th P
- Makkosenmäki E
- Tuottajantie E
- Oikokatu th P
- Oikokatu th E
- Sotkamon kirkko P
- Jormua E
- Levälahti L
- Jormuantie L
- Naapurinvaara th L
- Naapurinvaara th I
- Tikkalansalmi P
- Tikkalansalmi E
- Kohvero P
- Ruunalampi P
- Ruunalampi E
- Vuokatti ras th L
- Vuokatti ras th I
- Hakala L
- Hakala I
- Tenetti Pohjavaarantie L
- Tenetti Pohjavaarantie I
- Särkisen tupa E
- Särkisen tupa P
- Laukkala pohjoinen th P
- Laukkala pohjoinen th E
- Kuolasalmi th P
- Kuolasalmi th E
- Ohravaara th P
- Rekivaara th E
- Juurikkalahti P
- Juurikkalahti E
- Kiantaperä th P
- Kiantaperä th E
- Sotkamo linja-autoasema
- Kiekkotien th P
- Kirkkotien th E
- Rusala E
- Rusala P
- Saaresmäki 3 P
- Saaresmäki P
- Työmiehentie E
- Työmiehentie P
- Muramaantie E
- Muramaantie P
- Honkakalliot E
- Tapanila E
- Tapanila P
- Lentokentäntie E
- Lentokentäntie P
- Päivärinteentien th E
- Päivärinteentien th P
- Paltaniemen hautausmaa E
- Paltaniemen hautausmaa P
- Kirkkoahon koulu E
- Kirkkoahon koulu P
- Naulala E
- Naulala P
- Hepomäki E
- Hepomäki P
- Kärrytie E
- Kärrytie P
- Mäkipelto E
- Mäkipelto P
- Miettula I
- Miettula L
- Mustikkamäentien th I
- Mustikkamäentien th L
- Heikkilä I
- Heikkilä L
- Kurjentien th I
- kurjentien th L
- Notkolantien th E
- Notkolantien th P
- Lehtomäki P
- Lehtomäki E
- Pärsänsuo th E
- Pärsänsuo th P
- Kirkkoaho P
- Kirkkoaho E
- Tuovila P
- Tuovila E
- Seppälä P
- Seppälä E
- Heinimäentie P
- Heinimäentie E
- Aittaharjuntie L
- Aittaharjuntie I
- Suopursu L
- Suopursu I
- Pärsänsuo L
- Pärsänsuo I
- Naurisaho L
- Naurisaho I
- Tuomaala L
- Tuomaala I
- Niemeläntie L
- Niemeläntie I
- Kuluntalahti L
- Vuokatin koulu E
- Vihtamo th L
- Vihtamo th I
- Suoniemi L
- Tyvelä E
- Tyvelä P
- Naapurinvaaran koulu E
- Naapurinvaaran koulu P
- Tolpanvaara E
- Tolpanvaara P
- Toivola E
- Toivola P
- Akonmäki E
- Akonmäki P
- Karhula E
- Karhula P
- Kyllölä E
- Kyllölä P
- Jokela E
- Jokela P
- Tuulimäki E
- Tuulimäki P
- Joutsenus E
- Joutsenus P
- Sipolankylä E
- Sipolankylä P
- Konappa E
- Konappa P
- Rasilantie E
- Rasilantie P
- Paakinsuo E
- Paakinsuo P
- Vilmiläntie E
- Vilmiläntie P
- Paakki P
- Paakki E
- Itäranta E
- Itäranta P
- Vaahtera E
- Vaahtera P
- Koski E
- Koski P
- Kylmäpuro E
- Kylmäpuro P
- Kouluniemi E
- Kouluniemi P
- Halola E
- Halola P
- Yppälä E
- Yppälä P
- Näretie E
- Näretie P
- Kotakangas E
- Kotakangas P
- Uimaniemi E
- Uimaniemi P
- and 660 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error740 instances
Invalid url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning851 instances
851 of 910 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning762 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning43 instances
43 of 257 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning4 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
1 of 257 trips have no headsign, the text that tells riders where the bus is going.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info15 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 6% of stops and 83% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 273 days.
- Accessible Not yet
- States wheelchair access on 6% of stops and 83% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 273 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 740 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 50 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/waltti-kajaani/2026-09-05.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-09-05. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.