Feed status · checked 2026-07-19
Pasažieru vilciens (Vivi)
Based on the feed this agency publishes
Service mode Rail
unchanged since 2026-07-18
Catalogued in Latvia.
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
141 of 141 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
393 of 393 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.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 feed_info.txt with feed_start_date and feed_end_date to your export. · 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 146 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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 5 kinds of issue across 66 instances (0 error, 66 warning, 0 informational).
Service data covers the next 146 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% 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 ("Bieriņi/Bērnu slimnīca").
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.
Fares are applied to trips.
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.
- Rīga - Aizkraukle (pink)
- Rīga - Carnikava (yellow)
- Rīga - Cēsis (gray)
- Rīga - Daugavpils (pink)
- Rīga - Dubulti (teal)
- Rīga - Ķemeri (teal)
- Rīga - Gulbene (pink)
- Rīga - Lielvārde (pink)
- Rīga - Liepāja (orange)
- Rīga - Indra (pink)
- Rīga - Madona (pink)
- Rīga - Ogre (pink)
- Rīga - Jelgava (orange)
- Rīga - Sloka (teal)
- Rīga - Tukums II (teal)
- Rīga - Saulkrasti (yellow)
- Rīga - Skulte (yellow)
- Rīga - Sigulda (gray)
- Rīga - Valmiera (gray)
- Rīga - Zilupe (pink)
- Rīga - Valga (gray)
- Aizkraukle - Rīga (pink)
- Carnikava - Rīga (yellow)
- Cēsis - Rīga (gray)
- Daugavpils - Rīga (pink)
- Dubulti - Rīga (teal)
- Ķemeri - Rīga (teal)
- Gulbene - Rīga (pink)
- Lielvārde - Rīga (pink)
- Liepāja - Rīga (orange)
- Indra - Rīga (pink)
- Madona - Rīga (pink)
- Ogre - Rīga (pink)
- Jelgava - Rīga (orange)
- Sloka - Rīga (teal)
- Tukums I - Rīga (teal)
- Tukums II - Rīga (teal)
- Saulkrasti - Rīga (yellow)
- Skulte - Rīga (yellow)
- Sigulda - Rīga (gray)
- Valmiera - Rīga (gray)
- Zilupe - Rīga (pink)
- Valga - Rīga (gray)
| Route | Type | Line color |
|---|---|---|
| Rīga - Aizkraukle | Rail | pink |
| Rīga - Carnikava | Rail | yellow |
| Rīga - Cēsis | Rail | gray |
| Rīga - Daugavpils | Rail | pink |
| Rīga - Dubulti | Rail | teal |
| Rīga - Krāslava | Rail | pink (no shape in feed) |
| Rīga - Ķemeri | Rail | teal |
| Rīga - Gulbene | Rail | pink |
| Rīga - Lielvārde | Rail | pink |
| Rīga - Liepāja | Rail | orange |
| Rīga - Ludza | Rail | pink (no shape in feed) |
| Rīga - Indra | Rail | pink |
| Rīga - Madona | Rail | pink |
| Rīga - Ogre | Rail | pink |
| Rīga - Jelgava | Rail | orange |
| Rīga - Sloka | Rail | teal |
| Rīga - Tukums II | Rail | teal |
| Rīga - Saulkrasti | Rail | yellow |
| Rīga - Skulte | Rail | yellow |
| Rīga - Sigulda | Rail | gray |
| Rīga - Valmiera | Rail | gray |
| Rīga - Zilupe | Rail | pink |
| Rīga - Valga | Rail | gray |
| Aizkraukle - Rīga | Rail | pink |
| Carnikava - Rīga | Rail | yellow |
| Cēsis - Rīga | Rail | gray |
| Daugavpils - Rīga | Rail | pink |
| Dubulti - Rīga | Rail | teal |
| Krāslava - Rīga | Rail | pink (no shape in feed) |
| Ķemeri - Rīga | Rail | teal |
| Gulbene - Rīga | Rail | pink |
| Lielvārde - Rīga | Rail | pink |
| Liepāja - Rīga | Rail | orange |
| Ludza - Rīga | Rail | pink (no shape in feed) |
| Indra - Rīga | Rail | pink |
| Madona - Rīga | Rail | pink |
| Ogre - Rīga | Rail | pink |
| Jelgava - Rīga | Rail | orange |
| Sloka - Rīga | Rail | teal |
| Tukums I - Rīga | Rail | teal |
| Tukums II - Rīga | Rail | teal |
| Saulkrasti - Rīga | Rail | yellow |
| Skulte - Rīga | Rail | yellow |
| Sigulda - Rīga | Rail | gray |
| Valmiera - Rīga | Rail | gray |
| Zilupe - Rīga | Rail | pink |
| Valga - Rīga | Rail | gray |
This feed has 141 stops.
List every stop
- Rīga
- Aglona
- Aizkraukle
- Alotene
- Āraiši
- Asari
- Atašiene
- Atgāzene
- Babīte
- Baloži
- Biksti
- Brasa
- Briģi
- Bulduri
- Carnikava
- Cena
- Cēsis
- Cesvaine
- Ciemupe
- Cirma
- Cukurfabrika
- Čiekurkalns
- Dalbe
- Dārziņi
- Daugavpils
- Daugmale
- Depo
- Dobele
- Dole
- Dubulti
- Dzintari
- Egļupe
- Kalngale
- Kalsnava
- Koknese
- Krāslava
- Krievupe
- Krustpils
- Gaisma
- Kūdra
- Garciems
- Kūkas
- Garupe
- Gauja
- Ķegums
- Ķemeri
- Ķīšupe
- Gulbene
- Lielupe
- Ieriķi
- Lielvārde
- Ikšķile
- Liepāja
- Līgatne
- Līksna
- Imanta
- Lilaste
- Inčukalns
- Līvāni
- Lode
- Inčupe
- Ludza
- Lugaži
- Indra
- Madona
- Majori
- Istalsna
- Mārciena
- Melluži
- Jāņamuiža
- Melturi
- Mežāre
- Milzkalne
- Muldakmens
- Jāņavārti
- Nerza
- Nīcgale
- Jaundubulti
- Jaungulbene
- Ogre
- Olaine
- Jaunkalsnava
- Ozolnieki
- Jaunogre
- Jaunolaine
- Jelgava
- Pabaži
- Pārogre
- Pļaviņas
- Priedaine
- Pumpuri
- Jersika
- Jugla
- Jumprava
- Kaibala
- Rēzekne II
- Garkalne
- Rumbula
- Sakstagals
- Salaspils
- Saldus
- Sarkandaugava
- Saulkalne
- Mangaļi
- Torņakalns
- BA Turība
- Tīraine
- Zasulauks
- Zolitūde
- Vaivari
- Sloka
- Smārde
- Tukums I
- Tukums II
- Saulkrasti
- Skulte
- Zemitāni
- Sigulda
- Skrīveri
- Skrunda
- Stirniene
- Strenči
- Šķirotava
- Taudejāņi
- Trepe
- Vabole
- Valmiera
- Vangaži
- Varakļāni
- Viļāni
- Zilupe
- Vecdaugava
- Vagonu parks
- Vecāķi
- Ziemeļblāzma
- Zvejniekciems
- Valga
- Bieriņi/Bērnu slimnīca
- Dauderi
- Medemciems
- Šmerlis
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 70.9 | first check |
| 2026-07-19 | 70.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning393 instances
393 of 393 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning141 instances
141 of 141 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)
- Warning47 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning11 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Validator rule: scorecard_missing_feed_info_dates · 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 0% 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 146 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 3 of 141 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 146 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 76 / 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 85 / 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/pasazieru-vilciens-vivi/2026-07-19.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-19. 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.