The TriMet instance of OTP won't use E-scooters on more than one leg. Need to figure out what in our config is limiting scooter legs
This trip on the IBI Instance usually has 2 scooter legs with a MAX leg in the middle.
This same trip on the TriMet Instance results in just 1 scooter leg with a MAX leg in the middle, and a walking leg to finish the trip.
Why are we seeing this behavior? It's making E-scooter trips not as effective on the TriMet instance. (Adding insult to injury, sometimes the transit leg is a short 1-stop leg, followed by a 2 mile walk).
This was due to the 'name' attribute in the portland boundary geojson data. Removed that, restarted OTP, and viola... (per @evansiroky debugging work & suggestion)
The TriMet instance of OTP won't use E-scooters on more than one leg. Need to figure out what in our config is limiting scooter legs
This trip on the IBI Instance usually has 2 scooter legs with a MAX leg in the middle.
This same trip on the TriMet Instance results in just 1 scooter leg with a MAX leg in the middle, and a walking leg to finish the trip.
Why are we seeing this behavior? It's making E-scooter trips not as effective on the TriMet instance. (Adding insult to injury, sometimes the transit leg is a short 1-stop leg, followed by a 2 mile walk).
Note: the configs, data and Graph.obj + otp.jar are all located here: https://maps.trimet.org/m/