routing-api | An API based on Itinero | REST library

I am exploring here.com rest api (v8) for the truck.

My rest api to get directions is as below:

https://router.hereapi.com/v8/routes?apiKey={my_api_key}&transportMode=truck&truck[width]=250000&origin=-33.947113,151.078804&destination=-33.86882,151.209296&return=polyline,actions,instructions&avoid[features]=tunnel

It seems like specifying the truck's height or width does not have any effect or is not recognized. I tried to put some very large values (truck[width]=250000) as well.

According to here.com official documentation, Rest api v8 we can specify the truck property as below:

I have to calculate some routes for bringing up do 8 people in a larger car (minibus) to a workplace and bring them home in the afternoon. Is is possible to add an ID attribute to the coordinates? That would help me to evaluate the responses in my Java Code instead of checking the Coordinates ("originalLocation" vs "location").

For example something like that ID 4711 at the end and separated by semicolon

• &via=47.774945410,12.103053452;4711
• &destination=47.7720259654,12.09511552052;4712

Something like the UserLabel in Routing V7 API: [API V7 Waypoint description] (https://developer.here.com/documentation/routing/dev_guide/topics/resource-param-type-waypoint.html#resource-param-type-waypoint__navigation-waypoint-link-positions). The description there said: waypoint in V8: string, {lat},{lng}[;name={name}]

I am using or experimenting with HERE Routing API V8. Or are there more options somewhere in the multiple HERE Telematics APIs that I can see on the Homepage?

I tried some things described in the migration guide (https://developer.here.com/documentation/routing-api/8.20.1/migration_guide/index.html) but they did not work

1. (a) &via=47.7747679928991,12.322371484945947;name=3333
   • returns: Invalid place option .... Unexpected input at end of place option at 'name=3333'
2. (b) &via=47.82695713017682,12.295106144134037!name=3333
   • returns: Invalid waypoint option
3. (c) &via=47.82695713017682,12.295106144134037;4711
   • returns: Place or waypoint option specification '4711' is invalid
   • ...Invalid value for parameter 'via'

By the way: I know that there is a difference in the API between

• "PlaceOptions" that follow the coordinates separated by semikolon/";" and
• "WaypointOptions" that are separated by exclamation mark "!".

The PlaceOptions seem to be fixed specified parameters like course, sideOfStreetHint, stopDuration etc and therefore I thought that the WaypointOptions should be the way to go. But still no luck.

grossWeight = 20000 kg
height = 5000 centimeters
length = 9000 centimeters
I have already read this https://developer.here.com/documentation/routing-api/8.9.1/api-reference-swagger.html
but I don't understand how to use these parameters
my example route, bridge traffic for trucks is prohibited map with Weight restrictions, my test route bridge marked as yellow my postman request example
in response from the server I get this polyline :

BG0zu0sDok2-tB7WkQvRwMnGgF3IwHzFoGnG0KrE4IjD4IrEgPjDoLzUrOrEjD_EjDnL7G7L_EvMrEvMvC7LnB7GUvHoBnLkDvMoGzKoGzjB8V_nBsYjNwH7a0P3XkNoGkhBoBwHkDkS0F8fsJozBgFkcwC8LwC8LzoBkcnG7f_EnajDnQ3DrTvMv-B7B_JnG7fnBnGnBnGnB7GnBnGvHrnB3S3iDzP7xC7G7kBrYz9DrJjwBnBnGnB7GnB7G_ErY3DzU8BvRAnLT3N7BnajDnkBvCrdvCvMrJ7zBzFnf3D3SrE_YTrE_Jz8BjI3wBnBvHnGvlBvC_O7B7LTjD3NvyC3DrY_T0U3S0ZsT4iDwCwMgFkXsJ8fwMgyBUgFoBgK4D0ZwCgPsEgZkDwRkD8Q4DsTzFoG7QwW9NuS
and here is decoded route
The correct route should look something like this

Question:

1. How to specify these parameters correctly?
2. Does the response come with instructions that the grossweight parameter was taken into account when laying this route?

Routing v7 API is available to construct an Isoline from a given location, but I notice v8 API doesn't seem to mention this feature at all. Is it just not in yet? Or is it not expected to be supported after v7?

I have a problem with Here Maps Routing API v8.

Altough the documentation states that: but a request may specify many more intermediate waypoints with via as well. See Route Via Intermediate Waypoint for examples.

... I am at a loss how to create a request with one origin/destination and two or more waypoints. In v7 we had a single waypoints parameter which allowed unlimited waypoints.

In v8, I tried something like: &via=52,13;51,14&.. to send two via points, but that doesn't work.

The v8 documentation (which feel rushed/unfinished) doesn't help, and neither their only example, which only illustrates the use of a single via waypoint.

Help please!!! .