How to increase search radius for a road link for a waypoint (Fleet Telematics API)
I'm trying to calculate route summary for a truck using Fleet Telematics Custom Routes API (https://cle.api.here.com/2/calculateroute.json).
And I'm getting an error saying: Cannot match lat/long onto a road link with 100.0m search radius.
The error is, in fact, correct since Truck is in the middle of a big warehouse and there are no roads in 100 radius.
So the question is how can I increase search radius to prevent this error. OR there are any other options?
Thanks in advance!
here-api asked Nov 20 '18 at 16:29
korbenkorben
61
add a comment |
I'm trying to calculate route summary for a truck using Fleet Telematics Custom Routes API (https://cle.api.here.com/2/calculateroute.json).
And I'm getting an error saying: Cannot match lat/long onto a road link with 100.0m search radius.
The error is, in fact, correct since Truck is in the middle of a big warehouse and there are no roads in 100 radius.
So the question is how can I increase search radius to prevent this error. OR there are any other options?
Thanks in advance!
here-api asked Nov 20 '18 at 16:29
korbenkorben
61
add a comment |
I'm trying to calculate route summary for a truck using Fleet Telematics Custom Routes API (https://cle.api.here.com/2/calculateroute.json).
And I'm getting an error saying: Cannot match lat/long onto a road link with 100.0m search radius.
The error is, in fact, correct since Truck is in the middle of a big warehouse and there are no roads in 100 radius.
So the question is how can I increase search radius to prevent this error. OR there are any other options?
Thanks in advance!
here-api asked Nov 20 '18 at 16:29
korbenkorben
61
I'm trying to calculate route summary for a truck using Fleet Telematics Custom Routes API (https://cle.api.here.com/2/calculateroute.json).
And I'm getting an error saying: Cannot match lat/long onto a road link with 100.0m search radius.
The error is, in fact, correct since Truck is in the middle of a big warehouse and there are no roads in 100 radius.
So the question is how can I increase search radius to prevent this error. OR there are any other options?
Thanks in advance!
here-api here-api asked Nov 20 '18 at 16:29
korbenkorben
61
asked Nov 20 '18 at 16:29
korbenkorben
61
asked Nov 20 '18 at 16:29
korbenkorben
61
asked Nov 20 '18 at 16:29
korbenkorben
61
asked Nov 20 '18 at 16:29
korbenkorben
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can add a radius parameter in meters after the position, ex for 500m:
waypoint0=geo!48.85718,2.34141;500
Source doc:
https://developer.here.com/documentation/routing/topics/resource-param-type-waypoint.html
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397388%2fhow-to-increase-search-radius-for-a-road-link-for-a-waypoint-fleet-telematics-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can add a radius parameter in meters after the position, ex for 500m:
waypoint0=geo!48.85718,2.34141;500
Source doc:
https://developer.here.com/documentation/routing/topics/resource-param-type-waypoint.html
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
add a comment |
You can add a radius parameter in meters after the position, ex for 500m:
waypoint0=geo!48.85718,2.34141;500
Source doc:
https://developer.here.com/documentation/routing/topics/resource-param-type-waypoint.html
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
add a comment |
You can add a radius parameter in meters after the position, ex for 500m:
waypoint0=geo!48.85718,2.34141;500
Source doc:
https://developer.here.com/documentation/routing/topics/resource-param-type-waypoint.html
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
You can add a radius parameter in meters after the position, ex for 500m:
waypoint0=geo!48.85718,2.34141;500
Source doc:
https://developer.here.com/documentation/routing/topics/resource-param-type-waypoint.html
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
answered Nov 20 '18 at 21:30
IlyaIlya
3,9142922
3,9142922
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
add a comment |
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
unfortunatelly not. I'm using using Fleet Telematics API and extra parameter for waypoint are not supported except stopOver!. Source: cre.api.here.com/swagger-ui.html?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} As it says: &waypoint1=stopOver,300! 50.12,8.65. None of the optional specifications geo!, stopOver!, passThrough!, altitude, transitRadius, custom label, heading, !StreetPosition, !LinkPosition are currently supported.
– korben
Nov 22 '18 at 21:07
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
Oh. Maybe you could then ask the HERE support if an API change is in the works ?
– Ilya
Nov 23 '18 at 19:08
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397388%2fhow-to-increase-search-radius-for-a-road-link-for-a-waypoint-fleet-telematics-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
