Just a WAG (wild *** guess) but I think a restriction would be the way to go.
Think of it this way; if you add a cost all that does is give the solver a reason to minimize the cost. But what if it can't? Lets say a route for a vehicle is restricted due to barriers of some sort. It would then route under/over the bridge in question just because it could. The cost is what it is. But the real problem is you routed a truck over a bridge that can't support it's weight or under one that isn't tall enough for the load to pass. Ouch...
A restriction like XXX,XXX lbs or XX feet would ensure you from what I like to call a 'resume generating event'...
Just a WAG (wild *** guess) but I think a restriction would be the way to go.
Think of it this way; if you add a cost all that does is give the solver a reason to minimize the cost. But what if it can't? Lets say a route for a vehicle is restricted due to barriers of some sort. It would then route under/over the bridge in question just because it could. The cost is what it is. But the real problem is you routed a truck over a bridge that can't support it's weight or under one that isn't tall enough for the load to pass. Ouch...
A restriction like XXX,XXX lbs or XX feet would ensure you from what I like to call a 'resume generating event'...
OK, that makes sense. But, when I have it entered in, how do I account for the different clearances? Some are 14ft up to 17ft. For instantance. A truck has a height of 15. It can go under bridges 15ft 1in or higher, but not the 14ft 11 in or lower. But as a restriction, it will block all of the bridges, won't it?
You should model it as a parameterized restriction. At solve time you can set the height of the vehicle and then the restrictions will be used appropriately. Read more about it here in the section titled "Parameters for modeling vehicle characteristics":
Jay- After reading through that material, I won't be able to do utilize the Restriction Usage, as I am using 10.0, not 10.1. I will have to do some more reading into the parameters on cost attributes.
