High Performance Routing with RoadEditor with xDimaServer

[daxbin]

Hi,

I'd like to test high performance routing (HPR) with xDima with several profiles which have and have not
HPR (high performance routing) and RE (road editor)

Code: Select all

Profile  HPR  -RE
carslow   –    –
carfast   ×    –
sdp1      –    ×
fdp1      ×    ×

For some reasons the sdp1 and fdp1 profiles do not use Truck Attributes Feature Layer yet, but instead legacy Road Editor.

I've got the following results:

Code: Select all

xServer  Profile  HPR  -RE  Size-X  Size-Y  --Time
xDima    carslow   –    –     400     400   22,6 s
xDima    carfast   ×    –     400     400    1,4 s
xDima    sdp1      –    ×     400     400   69,9 s
xDima    fdp1      ×    ×     400     400   ------

For the fdp1 profile still when trying to create dima with:

Code: Select all

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <createDima xmlns="http://types.xdima.xserver.ptvag.com">
      <int_1>101</int_1>
      <DimaProfile_2 vehicleType="VTTRUCK" dimaCoordFormat="GEODECIMAL" maxLocationCount="2000" linkType="LTSEGMENT" routingType="RT1TON" optimization="90" />
      <CallerContext_3>
        <ns3:wrappedProperties xmlns:ns3="http://baseservices.service.jabba.ptvag.com">
          <ns3:CallerContextProperty key="Profile" value="fdp1" />
          <ns3:CallerContextProperty key="CoordFormat" value="PTV_GEODECIMAL" />
          <ns3:CallerContextProperty key="ResponseGeometry" value="PLAIN" />
        </ns3:wrappedProperties>
      </CallerContext_3>
    </createDima>
  </soap:Body>
</soap:Envelope>

the following exception is thrown:

Code: Select all

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <soap:Fault>
      <faultcode>soap:10003</faultcode>
      <faultstring>Could not create Dima 101. Engine error: Internal routing engine error (code: -101)</faultstring>
      <detail>
        <ns0:XDimaException xmlns:ns0="http://xdima.xserver.ptvag.com">
          <ns4:stackElement xmlns:ns4="http://exception.core.jabba.ptvag.com" message="Could not create Dima 101. Engine error: Internal routing engine error (code: -101)" errorKey="10003" className="com.ptvag.xserver.xdima.XDimaException">
            <ns4:cause xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true" />
            <ns4:wrappedContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true" />
          </ns4:stackElement>
        </ns0:XDimaException>
      </detail>
    </soap:Fault>
  </soap:Body>
</soap:Envelope>

On xRoute instead I get:

Code: Select all

xServer  Profile  HPR  -RE  Size-X  Size-Y  --Time
xRoute   carslow   –    –     400     400   22,5 s
xRoute   carfast   ×    –     400     400    4,6 s
xRoute   sdp1      –    ×     400     400   59,9 s
xRoute   fdp1      ×    ×     400     400    4,6 s

Are there any known issues with legacy Road Editor on xDima?


Best regards, Birk

[Bernd Welter]

Is this still an issue? I'm not aware of an error in this combination...

So the profile fdp1 is the one using the search graph based on traditional TruckAttributes.BIN file?

Best regards Bernd

[daxbin]

Hello Bernd,

yes,

Is this still an issue? I'm not aware of an error in this combination...

there is still an issue with exact this combination.

So the profile fdp1 is the one using the search graph based on traditional TruckAttributes.BIN file?

Yes, the fdp1 profile uses the TruckAttributes.bin file in the re sub folder of the map like spd1 does. But fdp1 has a chData file which seems to can be handled by xRoute but not by xDima because the latter throws the above mentioned exception.

Best regards, Birk

[Bernd Welter]

Hello Birk,

please create a regular ticket via support. Probably you have to provide the BIN file, /CONF and logs.

Best regards
Bernd