MNR tripIDs in GTFS-rt don't match static GTFS ones

[Juan]

Hi MTA folks,

The tripIds of the GTFS-rt Trip Updates for the MNR don't match those of the static GTFS.

URL: https://api-endpoint.mta.info/Dataservice/mtagtfsfeeds/mnr%2Fgtfs-mnr

URL of the GTFS: http://web.mta.info/developers/data/mnr/google_transit.zip

Should we be using another GTFS dataset or this is the right one that should match?

If not, could you take a look at this?

Thanks in advance.

Best.

[Sunny]

This is a known structural limitation of the Metro-North data that is caused by the two being generated out of separate systems. The trip_id's in the GTFS-RT should match with trip_short_name in the static GTFS.

We are exploring ways to resolve this in the long term.

[Juan]

Hi Sunny,

Thanks for your answer.

I can't find any reference to the tripIds in the GTFS-rt in the static GTFS at this moment.

Ex, tripIds 7175455, 7175120 are in the GTFS-rt now but I can't find them in the static GTFS in any field.

Would the two sources be out of sync?

Best

[Sunny]

My apologies.

entity.id and vehicle.trip.trip_id are the trip_short_name. Ex. this is train 1365.

entity {
  id: "1365"
  trip_update {
    trip {
      trip_id: "7176961"
      start_time: "1433"
      start_date: "09062023"
      route_id: "3"
    }
    stop_time_update {
      arrival {
        time: 1694025180
      }
      departure {
        time: 1694025180
      }
      stop_id: "124"
      [transit_realtime.mta_railroad_stop_time_update] {
        track: "5"
        trainStatus: "On-Time"
      }
    }

...
  }
  vehicle {
    trip {
      trip_id: "1365"
    }
    timestamp: 1694009939
    vehicle {
      id: "1365"
      label: "1365"
    }
  }
}

[Juan]

Ok, thanks for the clarification.