Fuzzy trip matching, validate trip_id really exists

[Vinceveve]

Is your feature request related to a problem? Please describe.

When I receive a realtime feed, it can have a trip_id or not.
If it has a trip_id, OTP assumes the trip_id is ok.
Many times it is not. (random int or uuid, without any link with static feed)

Goal / high level use-case
Facilitate realtime feeds integration.

Describe the solution you'd like
When FuzzyTripMatching is activated, I need to validate that the provided trip_id really exists in the static feed.
If not, act like there is no trip_id set and try to match using route, date and time.

Describe alternatives you've considered
Proxy between RT feed and OTP to remove trip_id dynamically.

[leonardehrenfried]

I am taking a look at this today and I noticed that the direction is also required by the current fuzzy matcher. Do you have that in your data?

[Vinceveve]

Yes direction Boolean was there too