Touring Plans and DAS Logic

Without knowing DAS return times, is there a way to somehow take DAS into account when you create touring plans? For instance, there are two adults and one child in the party. DAS is for the child. So for anything that he cannot/would not ride, we don’t have DAS, and MY logic (which might be wrong) says that we should therefore ‘rope drop’ the rides that we can’t use DAS for, because with rider swap, it would be better to make our waits as short as possible with my son’s limits in mind. He is going to have to wait on us, even though he isn’t riding.

Or if TP can’t apply logic that specifically, does anyone know of suggested plans for this kind of scenario? Or does it just need to be a manual process on my part?

1 Like

This is a good strategy. DAS gives returns times based on current times, correct? Takes a little planning and finagling but you could potentially figure a plan of attack by entering LL info based on the wait times TP gives. DAS return time will most likely be longer though. Then you rearrange that step to fall within the return time. I would set my walking to the slowest and set priority to less walking.

I would make 2 copies of a plan, using your own logic to rope drop the intense rides and also put them in twice to allow for rider switch.

Optimise one and Evaluate the other. You can compare the overall wait times but also the general feel of the plans. And choose accordingly.

1 Like