You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling or disabling transit modes in an analysis, all routes added by scenarios are treated as trams.
There is no UI element to set the mode of a newly added route, but when an AddTrips object is initialized, its mode = Route.BUS. Applying this modification to the network does not copy the mode info into the new instance of com.conveyal.r5.transit.RouteInfo, which is where the router looks for it. So the field com.conveyal.r5.transit.RouteInfo#route_type remains uninitialized at 0, which in GTFS means "tram".
The text was updated successfully, but these errors were encountered:
The mode of travel for added trips (routes) still can't be set in the UI, but this change at least copies over the default value (bus) from the AddTrips modification class.
This has been confirmed to work - when bus is deselected in the UI, added routes are not considered.
It should suffice to include a mode property in the modification JSON.
When enabling or disabling transit modes in an analysis, all routes added by scenarios are treated as trams.
There is no UI element to set the mode of a newly added route, but when an AddTrips object is initialized, its
mode = Route.BUS
. Applying this modification to the network does not copy the mode info into the new instance of com.conveyal.r5.transit.RouteInfo, which is where the router looks for it. So the field com.conveyal.r5.transit.RouteInfo#route_type remains uninitialized at 0, which in GTFS means "tram".The text was updated successfully, but these errors were encountered: