Roosevelt Island Operating Corporation Tramway (RIOC Tramway)

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

1. Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Estimated effort: Varies.

2. Add feed_contact_email or feed_contact_url to feed_info.txt.

   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.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Estimated effort: One field, set once in export settings.

3. Add feed_contact_email to feed_info.txt.

   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.

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

   Estimated effort: One field.