Truck Road Problem

[datscher2099]

Hello!

We have the Problem, that some routes are doesn´t work correctly. So we changed the „<MalusByNetworkClass malus="-20"/>“ and now it works for the most routes.

But one route is false, because the route D-Neu-Ulm to I-Bolzano goes trough A-6600 Reute and the "Fernpass Bundesstraße". But this road is not allowed for trucks.

So when i Change the Malus from -20 to 0 then the route is correct. But i have Problems with other routes.

So i have tryed a Exception Path: <ExceptionPath absTimeMalus="0" binaryPathDesc="" extSegments="" relMalus="2501" street="Fernpass Bundesstra&#223;e"/>

And i have also tryed with "B179". But all ways are doens´t work. Have you a Idee what the Problem is?

Thx

[datscher2099]

Hello!

We have the Problem, that some routes are doesn´t work correctly. So we changed the „<MalusByNetworkClass malus="-20"/>“ and now it works for the most routes.

But one route is false, because the route D-Neu-Ulm to I-Bolzano goes trough A-6600 Reute and the "Fernpass Bundesstraße". But this road is not allowed for trucks.

So when i Change the Malus from -20 to 0 then the route is correct. But i have Problems with other routes.

So i have tryed a Exception Path: <ExceptionPath absTimeMalus="0" binaryPathDesc="" extSegments="" relMalus="2501" street="Fernpass Bundesstra&#223;e"/>

And i have also tryed with "B179". But all ways are doens´t work. Have you a Idee what the Problem is?

Update: A employee from you has written a mail and now we change the config File like this:

<AdditionalRules maximumAirLineDistance="4294967295">
<ArrayOfExceptionPath>
<ExceptionPath relMalus="2501" street="B179">
<wrappedNodes xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:nil="true"/>
</ExceptionPath>
</ArrayOfExceptionPath>

But the same Problem again....

Thx

[Joost]

This is a topic that is a bit to complex to easily explain in a forum post since it covers very specific settings in combination with specific parts of the map. I am seeing that you are in contact with our regular support, they should be able to help you with sorting out the details.

[Bernd Welter]

Hello together,

though we already had a phonecall some days ago I'd just like to add a few words here:

• We provide various approaches of how to block / avoid segments in the routing process. While some of them are based on categories
  • network classes
  • toll roads
  • ferries...
  others are based on rough identities
  • ExceptionPath + streetnames
  • RoadEditor with selected segments and their properties
  • FeatureLayer with explicit data...

The usecase you describe sounds like you'd like to prevent the router from using specific area based objects: the first one you encountered is the "Fernpass Bundesstraße", your solution approaches this object and later you face another street or issue of the same category. So what I recommend is to identify the structure (or character) of the unwanted segments and to use one of the category based approaches.
Specifying explicit objects in your request is - quite often - increasing the complexity of the solution while the quality does not necessarily increase (if you miss a specific street segment).
Of course the approach may depend on the data quality (e.g. consumed by feature layer) but with proper data the generic approach covers the whole map universe with only a few lines of code (low complexity).

Best regards Bernd