Feed status · checked 2026-07-18
Waltti (Joensuu)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Pohjois-Karjala, 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.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
1603 of 1613 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 +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
3315 of 3315 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 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
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.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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 85 days.
- Published accessibility data
- Accessibility information is stated for 0.6% of stops and 0% 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 7 kinds of issue across 50481 instances (0 error, 50456 warning, 25 informational).
Service data covers the next 85 days.
1% of stops state wheelchair accessibility (0% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
1% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Kuhmonkatu/ koulut").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (green)
- 101 (green)
- 102 (green)
- 103 (green)
- 104 (green)
- 11 (green)
- 112 (green)
- 2 (green)
- 201 (green)
- 202 (green)
- 203 (green)
- 204 (green)
- 3 (green)
- 4 (green)
- 6 (green)
- 9 (green)
- 114 (green)
- 12 (green)
- 122 (green)
- 124 (green)
- 127 (green)
- 131 (green)
- 206 (green)
- 207 (green)
- 211 (green)
- 212 (green)
- 214 (green)
- 215 (green)
- 400 (green)
- 401 (green)
- 420 (green)
- 425 (green)
- 440 (green)
- 460 (green)
- 465 (green)
- 480 (green)
- 490 (green)
- 500 (green)
- 540 (green)
- 540 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Utra/Koillispuisto- Keskusta - Karhunmäki - Reijola | Bus | green |
| 101 Niittylahti-Joensuu-Ylämylly | Bus | green |
| 102 Joensuu-Honkalampi-Liperi | Bus | green |
| 103 Joensuu-Reijola-Hammaslahti | Bus | green |
| 104 Joensuu-Reijola-Suhmura-Hammaslahti | Bus | green |
| 11 Urheilupuisto - Keskusta - Utra | Bus | green |
| 112 Joensuu-Reijola-Kumpu-Särkivaara-Joensuu | Bus | green |
| 2 Utra/Kupluskylä - Keskusta - Marjala | Bus | green |
| 201 Hukanhauta-Joensuu-Lehmola-Kylmäoja | Bus | green |
| 202 Joensuu-Lehmola-Kontiolahti | Bus | green |
| 203 Joensuu-Kontiolahti-Kontioniemi | Bus | green |
| 204 Joensuu-Lehmo-Paihola | Bus | green |
| 3 Petäikkölä - Vehkalahti - Keskusta - Raatekangas | Bus | green |
| 4 Kulho - Keskusta - Onttola | Bus | green |
| 6 Joensuu - Lentoasema / Airport | Bus | green |
| 9 Otsola - Keskusta - Iiksenvaara | Bus | green |
| 114 Joensuu-Niittylahden koulu-Niittylahti | Bus | green |
| 12 Marjala - Keskusta - Utra | Bus | green |
| 122 Liperi-Mattisenlahti-Jyrinkylä | Bus | green |
| 124 Jyrinkylä - Ylämylly - Liperi | Bus | green |
| 127 Ylämylly-Viinijärvi | Bus | green |
| 131 Ylämylly - Vaivio | Bus | green |
| 206 Joensuu-Alavi-Mönni-Jakokoski-Kontiolahti | Bus | green |
| 207 Joensuu-Kulho-Kuurna-Kontiolahti | Bus | green |
| 211 Joensuu-Onttola-Kunnasniemi-Kontiolahti | Bus | green |
| 212 Joensuu-Lehmola-Kontiolahti | Bus | green |
| 214 Kuurna-Paihola-Kontioniemi-Kontiolahti | Bus | green |
| 215 Onttola-Kontiolahti | Bus | green |
| 400 Joensuu-Outokumpu | Bus | green |
| 401 Joensuu - Outokumpu | Bus | green |
| 420 Joensuu-Polvijärvi | Bus | green |
| 425 Joensuu-Käsämä-Polvijärvi | Bus | green |
| 440 Joensuu-Juuka-Nurmes | Bus | green |
| 460 Joensuu-Lieksa | Bus | green |
| 465 Joensuu-Eno Uimaharju | Bus | green |
| 480 Joensuu-Ilomantsi | Bus | green |
| 490 Joensuu-Kiihtelysvaara | Bus | green |
| 500 Joensuu-Tohmajärvi-Kitee | Bus | green |
| 540 Joensuu - Rääkkylä | Bus | green |
| 540 Joensuu - Rääkkylä | Bus | green |
This feed has 1613 stops.
List every stop
- Kanervala P
- Lentoasemantie L
- Reijola E
- Reijola P
- Reijolan koulu P
- Siirtolantie E
- Siirtolantie P
- Tempontie P
- Tempontie E
- Haapajoki P
- Haapajoki E
- Kukkola P
- Kukkola E
- Varpaniemi E
- Varpaniemi P
- Karhunmäki E
- Kotilahti P
- Kotilahti E
- Nepenmäki E
- Erkinpellontie I
- Ojalankaarto I
- Yliopisto P
- Yliopisto E
- Kanervala E
- Tuohitie L
- Petäikkölänkatu P
- Laiduntie P
- Paimenpojantie P
- Lonikintie L
- Yrittäjäntie E
- Sompatie E
- Pielisensuu P
- Pielisensuu E
- Kuntohovi E
- Kannelpuisto L
- Kannelpuisto I
- Suvikuja L
- Konepaja E
- Pyhäselänkatu L
- Kuhasalontie E
- Meijeri L
- Meijeri I
- Kimmel E
- Kimmel P
- Itäranta E
- Pappilantie L
- Sariolankatu L
- Oksoja L
- Iiksenportti L
- Iiksenportti I
- Kissamäentie L
- Kissamäentie I
- Pyörretie P
- Pyörretie E
- Nyyrikinkatu I
- Nyyrikinkatu L
- Sommelo L
- Sommelo I
- Lepikkoaho L
- Ketunpesät L
- Kupluskylä E
- Törö P
- Törö E
- Mustosenkatu I
- Mustosenkatu P
- Vesisahantie P
- Vesisahantie E
- Hiekkalantie L
- Hiekkalantie I
- Talastie L
- Koillisväylä P
- Koillisväylä E
- Koillisportti L
- Repsikankatu L
- Upokaskuja I
- Utrantori P
- Lasinpuhaltajantie I
- Lasinpuhaltajantie L
- Miilunpolttajantie I
- Miilunpolttajantie L
- Laivurintie L
- Laivurintie I
- Utrantie I
- Utrantie L
- Verkkotie E
- Pilkkitie E
- Kuohutie I
- Harustie I
- Ruuhitie I
- Latolankatu I
- Latolankatu L
- Pataluoto L
- Uikunkatu L
- Pursitie P
- Ruoritie P
- Rantakylä I
- Rantakylä L
- Riippapuisto P
- Lauttatie E
- Juhanintie E
- Ollilanpuisto P
- Toukolankatu E
- Varikko I
- Varikko L
- Raivaajantie I
- Kartoittajantie P
- Kartoittajantie E
- Lattamiehentie P
- Lattamiehentie E
- Kurjenkatu I
- Kurjenkatu L
- Mutalan koulu I
- Mutalan koulu L
- Siihtala I
- Siihtala L
- Rauhanpuisto I
- Rauhanpuisto E
- Penttilänkatu E
- Aurinkokatu L
- Aurinkokatu P
- Lintuaidantie E
- Kuuselantori P
- Kuuselantori E
- Erkinpellontie L
- Vilniuksenkatu P
- Roskildenkatu P
- Mujusenpiha P
- Lehtokangas L
- Kaislaranta L
- Lähdesuo P
- Lähdesuo E
- Lykynnurmi P
- Lykynnurmi E
- Siilaisentori E
- Louhosaukio L
- Louhosaukio I
- Siilaisentie L
- Siilaisentie I
- Siilaisen terveysasema P
- Siilaisen terveysasema E
- Kuusamatie P
- Kuusamatie E
- Tiedepuisto L
- Tiedepuisto I
- Ravirata I
- Lyseo L
- Siepontie P
- Siepontie E
- Vanamokatu E
- Petrankatu E
- Länsikatu E
- Pt-talo E
- Kanavaranta L
- Kanavaranta I
- Yläsatamakatu L
- Yläsatamakatu I
- Virastotalo P
- Virastotalo E
- Lepikkoaho I
- Itäranta P
- Suvikuja I
- Raivaajantie L
- Jukolanportti P
- Koskikatu P
- Keskuspuisto P
- Koskikatu I
- Koskikatu I
- Koskikatu L
- Kauppatori I
- Pappilantie I
- Sariolankatu I
- Oksoja I
- Laulupuuntie I
- Karjamäentie E
- Hukanhaudantie P
- Ylämylly I
- Mansikkatie E
- Mansikkatie P
- Huvimäentie P
- Hirvolantie P
- Hirvolantie E
- Mulontie P
- Mulontie E
- Tehtaantie P
- Lampitie L
- Sompalampi L
- Honkamonttu I
- Honkamonttu L
- Honkapuisto L
- Honkapuisto I
- Katajakuja L
- Hopri E
- Jyrinlenkki
- Louhelantie P
- Louhelantie E
- Enon koulut
- Eno
- Oravanmarjantie I
- Teppola P
- Teppola E
- Kesätuulentie I
- Kesätuulentie L
- Onkamo th P
- Onkamonsuora P
- Onkamonsuora E
- Valtamaa E
- Valtamaa P
- Tikkalan koulu (vt6) E
- Tikkalan koulu (vt6) P
- Tikkala (vt6) E
- Tikkala (vt6) P
- Hernevaara (Tohmajärvi) E
- Hernevaara (Tohmajärvi) P
- Haukioja E
- Haukioja P
- Suurkangas E
- Suurkangas P
- Rauansalontie E
- Rauansalontie P
- Elinmyllyntie E
- Elinmyllyntie P
- Karhuntaival E
- Karhuntaival P
- Honkavaara (Joensuu) E
- Honkavaara (Joensuu) P
- Kiihtelystie th E
- Kiihtelystie th P
- Hammasjärvi E
- Hammasjärvi P
- Pykäliköntie E
- Pykäliköntie P
- Mökinpelto E
- Mökinpelto P
- Haavanpää (vt6) E
- Karjalanmäki E
- Karjalanmäki P
- Tikunseläntie E
- Tikunseläntie P
- Kukkuraitti E
- Kukkuraitti P
- Ruunavaara th E
- Ruunavaara th P
- Savikko (Joensuu) E
- Savikko (Joensuu) P
- Pitkämäki (Joensuu) E
- Mähölä E
- Metsäpelto E
- Metsäpelto P
- Kumpu th E
- Kumpu th P
- and 1363 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
12 findings, ordered by severity.
Show every finding
- Warning50451 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.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3315 instances
3315 of 3315 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1603 instances
1603 of 1613 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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
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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
1 of 3315 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info10 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unknown_file · 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: 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
This feed is close to the conformance mark. States wheelchair access on 1% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 85 days.
- Accessible Not yet
- States wheelchair access on 1% of stops and 0% 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 85 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 74 / 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 38 / 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-joensuu/2026-07-18.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-07-18. 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.