API: GetHistoricalTrack


#1

GetHistoricalTrack takes an input of “ident@departureTime”. Now I’m not sure why, but I have a database that has a bunch of departure times I’m interested in, but they’re off just a bit from what you guys have - maybe 2 to 6 seconds in some cases. Anyway, it looks like I don’t get a hit in GetHistoricalTrack unless it’s exact. Would you consider an option to the API to add “roundToMinute” or “ignoreSeconds” or something that, if set, would change your underlying query from ‘equals’ to ‘like’ so that I’d get a return even if the time didn’t 100% line up?