Clean up trip_headsigns

[samvermette]

On the CARTA website it does seem like they label headsigns as Inbound and Outbound.

Your GTFS feed generally follows that convention but has inconsistent headsigns. Some headsigns contain the route name + direction, and others not. I would just label them as inbound/outbound (fullname instead of abbreviation).

As @jden pointed out on Twitter this seems to be deeper problem since these strings are used on real-life vehicle headsigns, but figured I'd open an issue anyway.

[junosuarez]

Thanks for opening this issue. Is this a blocker for your use of the data? As you note, we're continuing to improve the data in the upstream systems which are used to generate the GTFS dataset.

[samvermette]

Not a blocker at all, we have a bunch of tools that take care of cleaning headsigns and other strings, but ideally we don't need to get those involved :)

[samvermette]

Quick follow-up: we just ended up renaming everything to Inbound or Outbound using the following method (Objective-C):

- (NSDictionary *)cleanedUpTripDictionary:(NSMutableDictionary *)dict {
    if([dict.tripHeadsign containsOneOfWords:@[@"OB", @"B"]]) {
        dict.tripHeadsign = @"Outbound";
        dict.rtTripHeadsign = @"OUT"; // to match Clever Devices API
    }
    else if([dict.tripHeadsign containsOneOfWords:@[@"IB", @"IBMKT", @"IB12TH+MKT"]]) {
        dict.tripHeadsign = @"Inbound";
        dict.rtTripHeadsign = @"IN"; // to match Clever Devices API
    }
    else {
        NSLog(@"Unexpected trip_headsign that neither IB or OB: %@", dict.tripHeadsign);
    }

    dict.rtRouteID = dict.routeID;
    return dict;
}

So beyond the inconsistencies there are 3 other "totally off" headsigns: B, IBMKT and IB12TH+MKT. Hope this helps.

[samvermette]

This is very related to #19, but any reason why you guys ended up removing the inbound/outbound connotation from the trip headsigns? We need those to be able to match the API predictions to the GTFS schedules...