Make patterns using parent stations, not stops

[mattwigway]

We're currently using the stops in a trip to make patterns, but we should really use the parent stations. In most feeds this won't make any difference, but in a few critical ones it will have a major effect. For instance, in the Netherlands, each platform is coded as a separate stop, meaning many lines have a whole bunch of patterns. For instance, trips from Den Haag Centraal to Amersfoort, at Utrecht Centraal:

[ansoncfit]

See also #108

[abyrd]

Before we invest any large amount of time in making select-by-name more efficient, we should also consider that the real demand (at least from discussions I’ve had with users) is geographic select. People want to just click on or drag select a place and take actions on all trips that pass through it.

They also generally think it makes more sense to select the trips /before/ acting upon them. Our UI bears te marks of the underlying software - which was intentional for simplicity at first but we need to consider having user interactions depart more radically from the internal data model.

[abyrd]

Discussed again today: the two main motivating factors here are 1. pattern selection when editing and 2. display performance. We don't necessarily want to merge all the patterns because it often matters that a transfer is from one end of a station to the other - collapsing all the patterns would allow some unrealistic transfers. And as noted above, the real demand is for geometric selection rather than name simplification. As for display performance, we're moving toward vector tiles which require some preprocessing, and stops can be merged into their parent stations when creating those vector tiles without simplifying the internal model.