https://route.api.here.com/routing/7.2/calculateroute.json?xnlp=CL_JSMv3.0.17.0&app_id[app_id]&app_code[app_code]&mode=fastest%3Btruck&representation=display&language=en-us&waypoint0=33.95%2C-117.4&waypoint1=34.43%2C-117.3&waypoint2=34.6%2C-117.33&waypoint3=34.6%2C-117.33&waypoint4=35.0%2C-117.65&waypoint5=35.13%2C-118.45&waypoint6=35.77%2C-119.25&waypoint7=36.51%2C-119.55&waypoint8=36.57%2C-119.61&waypoint9=36.57%2C-119.61&waypoint10=37.69%2C-122.14&waypoint11=37.6930555555%2C-122.1675
2.https://route.api.here.com/routing/7.2/calculateroute.json?xnlp=CL_JSMv3.0.17.0&app_id[app_id]&app_code[app_code]&mode=fastest%3Btruck&representation=display&language=en-us&waypoint0=33.95%2C-117.4&waypoint1=34.43%2C-117.3&waypoint2=34.6%2C-117.33&waypoint3=34.6%2C-117.33&waypoint4=35.0%2C-117.65&waypoint5=35.13%2C-118.45&waypoint6=35.77%2C-119.25&waypoint7=36.51%2C-119.55
Route for these waypoints dont seem to be working.
I did have a look for the first request and it will be calculated the vehicle car without any issue. That points to and issue within the truck routing and the error message NGEO_ERROR_GRAPH_DISCONNECTED underlines this assumption.
We have here an extended demo available which you can use for an analysis:
https://tcs.ext.here.com/examples/v3/fleet_telematics_api
If you add the waypoints there and calculate the truck route the error message points to waipoint 8. With a recalculation you can display a car route and have a look within the truck overlay where the possible connection issue lies.
Related
I am trying to execute a rather simple request using Here FleetApi Demo, this is the request I am trying to do:
https://fleet.api.here.com/2/calculateroute.json?waypoint0=19.3411164,-99.2533428&waypoint1=19.415757,-99.177453&waypoint2=19.344366,-99.251718&mode=fastest;car;traffic:disabled&departure=2021-09-21T11:05:44&alternatives=0&weightPerAxle=0.87t&limitedWeight=1.739t&height=1.67m&width=1.8m&length=4.41m
But this error is returned:
Couldn't reach way point 1 (start links -703403377 703403377 dest links -895284559 895284559 ), closest link to destination reached: 1291258613 at 19.34133/-99.25233, issues: gate
This request has a similar situation on waypoint 2 but this returns the following issue:
Couldn't reach way point 2 (start links 895284559 dest links -832770028 832770028 ), closest link to destination reached: -1077091646 at 19.34552/-99.25272, issues: one way
In both situations, it is possible to travel these routes but Here is unable to calculate it. The only way to do so is by adding a radius to search for the waypoint but that returns wrong routing:
In this example, waypoint blue is the desired waypoint but waypoint green is returned which is not acceptable solution.
Is there a workaround to these issues or am I doing something wrong?
We use Google Maps Directions API to retrieve lat,lon of waypoints.
When you throw the request into demo tool https://tcs.ext.here.com/examples/v3/fleet_telematics_api (expert mode). It will show the error and a red flag at the nearest reached point. Then you see that this is a industrial area or leisure park or similar. The fleet telematics APIs applies various vehicle restrictions and gate restrictions while calculating the route.
If you want to ignore those restrictions you have to set &ignoreWaypointVehicleRestriction=100000 and &traverseGates=true in the request query. Then ,it will ignore the VehicleRestriction and allows the router to traverse all gates.
Sample Request.
https://fleet.api.here.com/2/calculateroute.json?waypoint0=19.3411164,-99.2533428&waypoint1=19.415757,-99.177453&waypoint2=19.344366,-99.251718&mode=fastest;car;traffic:disabled&departure=2021-09-21T11:05:44&alternatives=0&weightPerAxle=0.87t&limitedWeight=1.739t&height=1.67m&width=1.8m&length=4.41m&&ignoreWaypointVehicleRestriction=800000&traverseGates=true
For more details regarding &ignoreWaypointVehicleRestriction=100000 and &traverseGates=true flags ,please refer below API document.
https://developer.here.com/documentation/fleet-telematics/api-reference.html#tag%2FRouting-Extensions-&-Route-Matching%252Fpaths%252F~1v8~1calculateroute.json%252Fget
I'm using the Here API to calculate routes for trucks with 40t. Using the HERE devtools, i got the same error of my APP. The answer is "The API can't calculate the route because of illegal access". I checked the map (image attached) and in the street where my journey will start, with a difference of some meters, it exists two limitations 12t and 18t. The street is one way... If you see the satellite image exists several trucks... The company is testing the software says the trucks goes their...
Can some help me on this?
https://fleet.api.here.com/2/calculateroute.json?waypoint0=41.325299,2.141551&waypoint1=stopOver,3600!41.3291843,2.0317197&waypoint2=stopOver,3600!40.91260530,-8.42291420&waypoint3=38.855951,-9.104382&mode=fastest;truck;traffic:enabled&departure=2020-08-19T02:57:58&alternatives=0&weightPerAxle=14t&limitedWeight=40t&height=4m&width=2.55m&length=16.5m&trailersCount=
If you want to ignore the restrictions for trucks in the route, add the parameter truckRestrictionPenalty and set the value to soft.
The route violating truck restrictions is indicated in the response with dedicated route and manoeuvre notes. The route with the note of the type violation and the text truckRestriction may be travelled at your own responsibility. While driving on such a route, extra care has to be taken as it may result in a vehicle or road infrastructure damage.
You can read more about the parameter here.
Thanks for your feedback, but we are using the Fleet Telematics Api not the Routing API. Using your info, We researched a litle more and we found the equivalent parameter: ignoreWaypointVehicleRestriction.
We added these params &ignoreWaypointVehicleRestriction=5000;0;all and the API returned the route with the warning.
Thanks,
When I use heavy truck (limitedWeight > 18tons) options I can't get route for road. I don't see any restrictions for that road.
This is a sample link with heavy truck calculate route https://fleet.api.here.com/2/calculateroute.json?waypoint0=49.624139,20.722449&waypoint1=49.623984,20.726724&mode=fastest;truck;traffic:disabled&alternatives=3&weightPerAxle=8t&limitedWeight=18t&height=4m&width=2.55m&length=18m&trailersCount=1
If I change limitedWeight (to e.g. 15t) then the route is calculated.
This is the exact setup:
Start: 49.624139, 20.722449
Destination: 49.623984, 20.726724
Traffic is disabled for route calculation
TrailersCount = set to 1
Truck dimensions were tested both with very small values and with real values
It is a problem of HERE's data? or I will must change parameters?
Remember that an API will never have inconsistent data, and in fact you searched for the Fleet API with the intuition to place restrictions on your route. The problem you are experiencing is the following, "the maximum weight for circulation on this road has been carried out", that is, how will it return a result if you passed the correct restrictions to him? What you can do is put the alternative routes, this way it will return the second best result based on your restrictions.
NOTE: This was meant to be a comment, but I can't do it because of the reputation
I am regularly getting the error 'Cannot match 52.19888/11.32296 onto a road link with 100.0m search radius'. In these cases, the location is often a warehouse that is indeed more than 100 meters from the nearest public road.
Here is an example query: http://fleet.api.here.com/2/calculateroute.json?mode=fastest;truck;traffic:disabled&driver_cost=20¤cy=EUR&rollups=total,country,tollsys,country;tollsys&commercial=1&shippedHazardousGoods=0&waypoint0=52.51,13.42&waypoint1=52.2787499,11.4330726&tollVehicleType=3&vehicle_cost=0.5&fuelType=Diesel&emissionType=6&length=1500cm&height=270cm&heightAbove1stAxle=120cm&vehicleWeight=7000kg&vehicleNumberAxles=2&trailerType=2&trailersCount=1&trailerNumberAxles=4&trailerHeight=270cm
Is there a way to increase the search radius for the way points in the Fleet Telematics API? I know that it is possible in the Route API, but can't find a way to do it for Fleet.
Or is there another way to get around this error message and get a valid route? For these calculations, I do not need the exact turn-by-turn directions: a route that is similar to the actual route a truck would drive would be enough.
Add the routeMatch parameter with value 1 so that your waypoints will be treated as a GPS trace and the algorithm will return the most probable route along the trace.
I have the following content in the link (https://www.developer.here.com/documentation/android-premium/dev_guide/topics/routing.html):
You can use RouteWaypoint to add more waypoint details to your route calculations. These details include whether the waypoint is a deliberate stopover or a crossing point through which the route must pass. This affects routing because the path containing the stopover or route may be different. For example, the calculated route may suggest a U-turn maneuver after a stopover, while a route containing the same location as the waypoint is recommended to continue on the same street. The via waypoint type is only supported in car routes and is not supported in other route types.
I guess this passage means that your company's SDK supports path planning between multiple points, but it seems to only support the "car" type. I want to confirm if the truck type is supported.
Adding multiple waypoints for Trucks is supported, but waypoints will always be of type "Stop_Over" , you cannot have a waypoint as type "Via_point" when using Truck Routing. More details can be found in https://www.developer.here.com/documentation/android-premium/api_reference_java/com/here/android/mpa/routing/RouteWaypoint.Type.html
VIA_WAYPOINT
public static final RouteWaypoint.Type VIA_WAYPOINT
No maneuver is generated for a VIA waypoint. After the VIA waypoint, route will continue in the same direction as when it's approached.
Via waypoints will "force" the route to pass through them, but they will not cause any guidance, announcement or maneuvers.
VIA waypoints are not considered during Guidance triggered re-routing nor do they trigger any callbacks upon arrival at the waypoint.
This is only supported by RouteOptions.TransportMode.CAR . It's ignored for other transport modes.