Transitive Overlay rendering is inaccurate without intermediate stops about otp-ui

[fpurcell]

See #42 and #36

[randolphjones]

To clarify, I am seeing this issue with both core-utils and transitive-overlay on v 0.0.12

[evansiroky]

This bug report is what I deserve for not testing with data that actually came from OTP.

[evansiroky]

FYI, the otp-react-redux application will always make requests for the intermediate stops as they are used in the ItineraryBody component to show how many stops a user has to ride. These stops are also displayed when a user clicks the DefaultTransitLegSummary component to toggle the view of stops. In otp-react-redux these intermediate stops are also rendered as a schematic element within the transit line display.

The design of otp-react-redux attempts to make the line/stops display in the itinerary body consistent with what is shown on the map in the transitive overlay. I'm not sure if this current design really needs those intermediate stops showing up in the line display so thought I'd bring this up since this functionality might be more suited for just the otp-react-redux implementation.

[randolphjones]

Thanks. That all makes sense. I'm ok with us always making the request with intermediate stops as well. @fpurcell may have a strong preference here when it comes to how he wants the app we're building to function. At a glance it looks like we want it to operate the same way as OTP-RR.