← Back to the full scorecard

Call-prep brief · checked 2026-10-21

OASA Athens rail transport (metro, electric railway, tram)

Grade F · 49.7 / 100

Unchanged since 2026-10-20.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Top three things to fix

  1. Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.

    Service data ended 51 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: Usually one export setting; export on a schedule so it never lapses again.

  2. Add feed_info.txt with feed_start_date and feed_end_date to your export.

    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.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: Two fields, set once in export settings.

  3. 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.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: A small file for most flat-fare systems.

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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
Service data ended 51 day(s) ago.
Next action
Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
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

Ready to send to the agency

Hi OASA Athens rail transport (metro, electric railway, tram) team, Service data ended 51 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/oasa-athens-rail/

Copy this note from the full scorecard.

Key facts

Feed URL
https://data.gov.gr/dataset/4e897a75-975a-4ce7-af65-f32ea01f93b9/resource/5e3858ee-d9ba-48c2-9015-744ea160976d/download/stasy_gtfs.zip
Last checked
2026-10-21
Service window
Feed has expired. Last service date 2026-08-31.
Location
Attikí, Greece

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.