[sumo-user] Manual bus routing via traci, ordering of stops in the getNe

["Schneider, Tim" <st148529@xxxxxxxxxxxxxxxxxxxxx>]

Dear SUMO users,

colleagues of mine and I are trying to route buses in sumo manually using the traci.vehicle.setRoute(...) and the traci.vehicle.setBusStop(...) function.

However, the order in which the buses are inserted in the list, we receive if we call traci.vehicle.getNextStops(...), differs in some cases

from the insertion order in which we called traci.vehicle.setBusStop(...). We wonder: What are the underlying rules in this bus stop list 

resulting in that ordering?

For example we call something like this:

> traci.vehicle.setBusStop(vehicle_id, stop_A, duration)

> traci.vehicle.setBusStop(vehicle_id, stop_B, duration)

> traci.vehicle.setBusStop(vehicle_id, stop_C, duration)

> traci.vehicle.setBusStop(vehicle_id, stop_D, duration)

Then we call

> traci.vehicle.getNextStopList(bus_id)

and expect the returned list of tupels now to be in the order: stop_A, stop_B, stop_C, stop_D.

However, instead we receive something like this (at least in some cases): stop_B, stop_A, stop_C, stop_D.

Does someone knows the background of this? Does the ordering of the stops in the getNextStops list even make a difference?

Unfortunately, we couldn't find information in the documentation about this.

Thanks in advance and best regards

Tim