🐛 Bug: Misrepresenting directional rail stops with the same lat/long

[i-am-sijia]

Describe the bug

In the MTC 9-county network, 19th and Macarthur stops on Southbound BART services are skipped. This bug is generated in the network creation step (the original pipeline notebooks). These two stations are different compared to the other BART stations in the input GTFS as they have two separate stop records for south and north bound respectively, although the lat/long of the south and north bound stops are exactly the same. Since the lat/long are the same for the south and north bound stops, only one rail node is generated. But the south bound stop did not get associated with the generated rail node, thus the final itinerary is skipping the south bound stops.

Need to check if this is corrected in Ranch's transit algorithm and if not, fix it.

Progress:

• Sufficient information provided
• Cause identified/found
• Test developed/identified
• Approach determined
• Test passes

To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Failing tests

• No applicable test failed, need to create.
• other...specify

Triggering line of code

Thoughts on resolution

Full stack trace

[i-am-sijia]

@yueshuaing