I've been using the HERE Routing API v7 for quite a while and how now tried to upgrade my app to v8. One marked difference is that for my test route the API v7 came up with about 900 waypoints, whereas the v8 API gave me almost 7000!
The routes themselves look fairly identical, but the resolution of the V8 API appears to be much higher. Is there a way to reduce the resolution to the old level, which was plenty for my application?
One difference on my side is that with the V8 API I am using flexible polyline by going through all returned sections, decoding the polyline and appending it to my route. With the V7 API I got a "shape" array within the returned route, so no polyline and no iterating through sections. It seemed a lot simpler.
There is a parameter "resolution" in the V7 API, which I usually set to 10. This parameter doesn't seem to exist in V8.
Related
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.
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¤cy=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
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}
I am migrating Google Analytics API from V3 to V4. I seem to have come across a strange problem.
When I query for number of users ga:users with the segment gaid::-1 which stands for All Visitors, in V3 I get some number of users x and when I query the same parameters in V4, I am not getting the same number x. In fact the new number lets call it y is much greater than x. Almost twice of x.
Other metrics are all fine. Only ga:users is coming out to be a wrong value. Also, if I use some other segment like gaid::-2 then it comes out to be the same value as in V3. The problem is with gaid::-1 only.
Does anyone have an idea of what might be wrong?
I'm using the ThoroughfareName property of google maps api v2 which is very handy to get only the address part.
I didn't see any equivalent to this in api v3. Is there some best practices / recognized algorithm to build it back using address_components ?
So far what I have done is use the route type of address_components + the street_number. This is probably not the correct algorithm but it suits my needs.