NetMaps URl too large error

[Alberto]

Hi, max number of Wps for Here and no traffic is 120, sending 94 wps I get this error, see pic.
How to solve this?
Thanks

[Bruce]

what's a wps?

[Alberto]

waypoints

! GET ROUTE -------------------------------------------------------------------------------------
! The maximum number of waypoints including the start point and end point is 120 without
! traffic and 50 with traffic. If the routing mode pedestrian is used, the distance
! between each two of the waypoints must not be greater than 5km.

[Bruce]

It would appear that Nginx has a limit to the overall length of the URL. That's the server on that side, so nothing we can do about that limit.

I guess the next best thing to do would be to see if the URL length can be reduced. In order to see that it might be helpful to see what your URL is currently set to...
(perhaps your waypoint ID's can be shorter or something like that.)

cheers
Bruce

[Alberto]

Bruce, problem to get the URL shorten is that you use the Legend of the Waypoint and it is very usefull as Tiptool on the map.

In NetMapsHERE._MakeWaypointsForOptimize   Procedure()
you use the Waypoint.ID to send to HERE, ID is very short.

but in NetMapsHERE._MakeWaypointsForCalc       Procedure()
you use the Waypoint Label, Label may be an Address

any way to send the ID in GetRoute?

mhhhh problem is it is used to make the line Start at... when each instruction set begins...

Im using part of the address, so how much can I shorten it?

Ive send an email to Here, waitin for response.

[Bruce]

I've read this a number of times, but I'm still not sure I understand what you are asking.

[Alberto]

Sory, I will try to be more specific.

All this come from my first post: Error 414 URL too large from Here server.

You make the URL in two procs, Optimize() and GetRoute()

In NetMapsHERE._MakeWaypointsForOptimize   Procedure()
when making the URL series of waypoints you use the Waypoint.ID to send to HERE, the IDs are normally shorter than Label.
the optimize is only to get the best "order" or "sequence" of waypoints, then its ok to use the ID to identify them.

but in NetMapsHERE._MakeWaypointsForCalc       Procedure()
you use the Waypoint Label, in my case Im using the first part of the Address and you, in the demo, are using a name.

Why do we need to use Label instead of ID in Getroute?
Because when you GetRoute, Here response with the Instructions and Here uses the Descripcion of the waypoint to make it, and response like:
Begin at "Description of waypoint 1" and go forward to "Description of waypoint 2"

Using the Label you will get:
Begin at "Capesoft Headquaters" and go forward to "Hamiltom street Nr12 Department 5"

But Using the ID may be you will get:
Begin at "11" and go forward to "123"
what is not OK for the user.

As the waypoint ID is shorter than the Label, then the URL for Optimize is shorter than for Getroute, using the same quantity of waypoints.
Then, with the same quantity of waypoints, you can Optimize without error but cannot GetRoute.
And the user does not understand what the error is or came from

So we need to check the length of the URL before posting and if its longer than the max length use by Here show a message to the user to shorten the descriptions.
This may be a template value "HERE URL max length" that we can change, because its a value defined by the HERE server.
I think this check must be done in .APIOptimize() and .APIGetroute()
May be just cheking the length before doing the .get()

Hope it helps.
Regards

[Bruce]

Doesn't seem like there's much I can do, except set a property
(self.MaxUrlLength)
- if you try and do a GET longer than that then you'll get a call to ErrorTrap.

the value in the property defaults to the length of CommandQueue.URLParameters. (which I've made 8K long)

cheers
Bruce

[Alberto]

Thanks a lot