Limitation for waypoints when using HERE Route Matching v8 - here-api

Limitations on Waypoints in Here-Maps SDK & Routing Performance measurement
I am using HERE Route Matching v8 and having the same question.
Is there still the limitation of 200 waypoints in a single request now?
Thanks.
I want to know the Limitation for waypoints when using HERE Route Matching v8

Thanks for the question. We would suggest you use waypoints with small sizes, and you are right the current limitation is still under 200 waypoints, this restriction is on the URL characters limitation, not the request itself.

Related

HERE Truck Transport Tile (trucknopttile)

We use Routing API v8 to build truck routes!
In our country constructed many new roads! But info on 'trucknopttile' tile is incorrect at now! Truck route built in incorrect way!
How can we improve this information and change this behavior?
Does v8 API have option like in v7 - 'truckRestrictionPenalty'?
Example:
Wrong weights limit signs on the bridge
Example request:
routes?transportMode=truck&origin=49.81208246726337,24.157407830301196&destination=49.81755155059492,24.147335560752186&return=polyline,tolls,summary,routeHandle,passthrough,incidents&alternatives=3&currency=EUR&units=metric&departureTime=any&avoid%5Bfeatures%5D=seasonalClosure,uTurns&avoid%5BzoneCategories%5D=environmental&vehicle%5Btype%5D=tractor&vehicle%5Blength%5D=1650&vehicle%5Bwidth%5D=255&vehicle%5Bheight%5D=373&vehicle%5BgrossWeight%5D=38000&vehicle%5BweightPerAxle%5D=11500&vehicle%5BaxleCount%5D=5&vehicle%5BtrailerCount%5D=1&spans=incidents,length,duration,countryCode,routeNumbers,speedLimit,dynamicSpeedInfo,notices&apiKey={API KEY}
Routing v7 had a strict approach to truck restrictions. There, no route which violated some truck restriction(s) was ever returned. It was possible to change this behavior with truckRestrictionPenalty parameter, but even then Routing v7 provided only a generic notice: Code: routingOptionViolated, Text: truckRestriction.
If Routing v8 cannot find any route that obeys all specified options and vehicle parameters and that avoids all applicable restrictions, by default, the response will contain a route that violates some restrictions. The response will also contain a set of critical notices explaining which restrictions could not be avoided. In some areas, this is not possible, for example in Romania, where almost all of the main roads have a 11.5t per axle restriction.
For more detail please refer below api document.
https://developer.here.com/documentation/routing-api/migration_guide/index.html

How many way points can I pass in the URL? Can I pass more than 100 way points?

I've been using HERE api to calculate the roughness profiles of the route. I need to pass more than 100 waypoints to get the IRI index. Is it possible to pass n number of waypoints or is there certain limit to it?
We only support GET method, POST will allow more, but it is not (yet) supported currently support whatever URL length limits allow.. So something like 100+ waypoints, but for optimising the route, there is a separate service which solves this is provided below.
https://developer.here.com/documentation/routing-waypoints/dev_guide/topics/quick-start-simple-car.html

Routing Service v8 API question - more than a single waypoint/via?

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!!!
.
You need to add as many times via={lat},{lng} as you have waypoints:
# Note: line breaks and spaces are for readability only (they need to be removed)
https://router.hereapi.com/v8/routes?
origin=52.550464,13.384223
&transportMode=car
&destination=52.477545,13.447395
&via=52.529791,13.401389
&via=52.513079,13.424392
&via=52.487581,13.425079
&apikey={YOUR_API_KEY}

How draw route on Bing map from json response

I'm totally novice for Rest Api, so i'm looking for example code. I've a set of geographical coordinates taken from a database and I need to find best route among these. I'm using Bing Maps, let say I have an idea how to code the Rest request, my problem is how parse and manage the JSON response to draw the route on the map in a asp.net page.
Assuming you're using the Bing V8 HTML control, the directions module will handle making the REST request and displaying the result for you - there's no need to parse the REST response directly yourself. See https://www.bing.com/api/maps/sdkrelease/mapcontrol/isdk/directionscreatedrivingroute
If you're using one of the other controls, similar modules are available.
I've found this JSON, is a step to step guide to request and consume JSON response.

OVI Map Route API Over HTTP

I'm doing some research on route distance calculation APIs, and I came across this API from Ovi/Nokia: http://api.maps.ovi.com/devguide/getting_started.html#Services
Does anyone know if they have an equivalent REST API that can be used outside of a client browser scenario?
If not, what's the best option for route distance calculation APIs? I've looked into Google, Bing, and MapQuest, but I would like to be able to use it internally without a daily rate limit.
Thanks for your help.
There is the maps image API, if showing the routes as images are sufficient. This page has the complete list if Nokia Maps APIs.
I do not want to repeat what is done, so please refer to the Nokia API reference, but to be more accurate use distance method from nokia.maps.geo.Coordinate. The complete documentation is here
Click here!

Resources