xLocate cannot give back planned route

[biro.daniel]

Hello guys,

we are facing the following issue in xLocate. In the case of adding e.g. city 'Szczecin' os 'Székesfehérvár' into the Address field the findAddressByText request results correct coordinates (in the city centres), but unfortunately PTV cannot give back a planned route as a result into this locations by using the truck profile.

Is there any method to influence the result coordinates in order to get back another correct coordinates which are reachable by trucks?

Thanks in advance
BR
Daniel

[LNM_PTV]

Hello Daniel,

I geocoded both 'Szczecin' and 'Székesfehérvár' with findAddressByText on the EuropeCityPremium2017.1H and the EuropeCityPremizm2017.2H and calculated a routing into these cities using the truckfast and truckslow profile.

Here is the sample request:

Code: Select all

 {
  "waypoints": [
    {
      "coords": [
        {
          "point": {
            "x": 934998.10798,
            "y": 6269667.2487
          }
        }
      ],
      "linkType": "NEXT_SEGMENT"
    },
    {
      "coords": [
        {
          "point": {
            "x": 2047137.5178,
            "y": 5967459.8659
          }
        }
      ],
      "linkType": "NEXT_SEGMENT"
    }
  ],
  "options": [],
  "exceptionPaths": [],
  "details": {
    "binaryPathDesc": false,
    "boundingRectanglesC": 0,
    "boundingRectanglesOffset": 0,
    "brunnelManoeuvres": false,
    "detailLevel": "STANDARD",
    "dynamicInfo": false,
    "manoeuvreAttributes": false,
    "manoeuvreGroups": false,
    "manoeuvres": true,
    "nodes": true,
    "polygon": true,
    "segmentAttributes": false,
    "segments": true,
    "texts": true,
    "totalRectangle": false,
    "urbanManoeuvres": false
  },
  "callerContext": {
    "properties": [
      {
        "key": "CoordFormat",
        "value": "PTV_MERCATOR"
      },
      {
        "key": "ResponseGeometry",
        "value": "WKB"
      },
      {
        "key": "Profile",
        "value": "truckfast"
      }
    ]
  }
}

The second route Point is Székesfehérvár.
In all cases I achieved a valid routing.

Can you try out my request on your side?

Best regards,
Lars

Edit by JCL: added code blocks for readability

[biro.daniel]

Hello Lars,

we tried what you said with the raw request runner and get a valid route.
But we found a difference between this and our general used calls, that we are using truck attributes.

Our extra parameters are the followings:
RoutingOption parameter="ENABLE_ROADEDITOR" value="true"
RoutingOption parameter="ROADEDITOR_ADDITIONAL_OPTIONS" value="MAX_WEIGHT=40000,MAX_HEIGHT=400,MAX_WIDTH=250,MAX_LENGTH=17500,MAX_AXLE_LOAD=1150"

Is there any possibility that xLocate could use somhow the TruckAttributes?

Tahnks agian,
BR
Daniel

[LNM_PTV]

Hello Daniel,

xlocate cannot use truckattributes.
The linking-problem usually occurs when there are truck restrictions in an area directly around the located geocoordinate.
The xroute searchs for a segment of the roadnetwork, where the geocoordinate can be linked to,within a certain linking distance.
The maximum distance that the xroute server considers can bei set by maximumDistanceToSegment:
http://xserver.ptvgroup.com/fileadmin/f ... efault.htm
If there are only segments that are forbidden for trucks within this area, the xroute-server cannot find a valid link.
If you enlarge the linking distance, the xroute-server will find a valid segment to link to, but it could be "a little bit away form the located geocoordinate".

Best regards,
Lars

[Joost]

Extra tip: consider enabling violations. This turns all blocking into very high avoidance. If an complete area is covered with a attribute is does occurs that their are sometime small gaps inside without the blocking where our linking engine then will link to. Since a point is then in an isolate area the route calculation will fail and throw an exception with the message in the form of "can not calculate route leg <number>" (I don't remember the message on top of my head). Enabling violations prevents this.

You can enable violation by adjusting your profile by setting Routing / Course / Violations / SegmentBlockingViolations / @enabled to true or adding a routing option with the parameter set to ALLOW_SEGMENT_VIOLATIONS and value set to true.

For details on violations affect you use case, please check http://xserver.ptvgroup.com/fileadmin/f ... ibutes.htm , paragraph "Calculate a route considering vehicle dimensions but allowing violations"