Fleet WayPoint : set range of access hours by waypointHow should one refresh the position of a largish number of marker positions in Here Maps 3.0?Here FindSequence Limit WaypointWaypoints limit [here-api]Route API not working for some waypointsHere Fleet Telematics Waypoint Sequence has limited request a dayFleet Telematics Custom RoutesHow to increase search radius for a road link for a waypoint (Fleet Telematics API)Query about TrafficModeType & departure timeHERE Waypoint Sequence APIFleet Telematics Route Matching, query more attributes for each route link
What is the missing number, can anyone solve this? My original puzzle
What organs or modifications would be needed for a life biological creature not to require sleep?
How to publish superseding results without creating enemies
Why did they ever make smaller than full-frame sensors?
How does a simple logistic regression model achieve a 92% classification accuracy on MNIST?
why car dealer is insisting on loan v/s cash
getting syntax error in simple bash script
Real mode flat model
Does my opponent need to prove his creature has morph?
Can I toggle Do Not Disturb on/off on my Mac as easily as I can on my iPhone?
Why do sellers care about down payments?
Will the UK home office know about 5 previous visa rejections in other countries?
Difference in using Lightning Component <lighting:badge/> and Normal DOM with slds <span class="slds-badge"></span>? Which is Better and Why?
Can derivatives be defined as anti-integrals?
What was the ultimate objective of The Party in 1984?
How can I discourage sharing internal API keys within a company?
I was promised a work PC but still awaiting approval 3 months later so using my own laptop - Is it fair to ask employer for laptop insurance?
Is the Dodge action perceptible to other characters?
Make 1998 using the least possible digits 8
What is my breathable atmosphere composed of?
Can I tap all my opponent's lands while they're casting a spell to negate it?
How do I say "quirky" in German without sounding derogatory?
Bit one of the Intel 8080's Flags register
"Literally" Vs "In the true sense of the word"
Fleet WayPoint : set range of access hours by waypoint
How should one refresh the position of a largish number of marker positions in Here Maps 3.0?Here FindSequence Limit WaypointWaypoints limit [here-api]Route API not working for some waypointsHere Fleet Telematics Waypoint Sequence has limited request a dayFleet Telematics Custom RoutesHow to increase search radius for a road link for a waypoint (Fleet Telematics API)Query about TrafficModeType & departure timeHERE Waypoint Sequence APIFleet Telematics Route Matching, query more attributes for each route link
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Is it possible to set a range of opening access hours for the calculation with findpickups.json?
in the Nokia HERE documentation it is indicated that to establish a range of access hours it must be indicated with this method. "acc: mo10: 30: 00 + 01: 00 | mo12: 00: 00 + 01: 00; st: 600", but is it possible to indicate the following case?
From Monday to Friday from 10:30 a.m. to 12 p.m. and from 4:00 p.m. to 8:00 p.m.
here-api
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
add a comment
|
Is it possible to set a range of opening access hours for the calculation with findpickups.json?
in the Nokia HERE documentation it is indicated that to establish a range of access hours it must be indicated with this method. "acc: mo10: 30: 00 + 01: 00 | mo12: 00: 00 + 01: 00; st: 600", but is it possible to indicate the following case?
From Monday to Friday from 10:30 a.m. to 12 p.m. and from 4:00 p.m. to 8:00 p.m.
here-api
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
add a comment
|
Is it possible to set a range of opening access hours for the calculation with findpickups.json?
in the Nokia HERE documentation it is indicated that to establish a range of access hours it must be indicated with this method. "acc: mo10: 30: 00 + 01: 00 | mo12: 00: 00 + 01: 00; st: 600", but is it possible to indicate the following case?
From Monday to Friday from 10:30 a.m. to 12 p.m. and from 4:00 p.m. to 8:00 p.m.
here-api
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
Is it possible to set a range of opening access hours for the calculation with findpickups.json?
in the Nokia HERE documentation it is indicated that to establish a range of access hours it must be indicated with this method. "acc: mo10: 30: 00 + 01: 00 | mo12: 00: 00 + 01: 00; st: 600", but is it possible to indicate the following case?
From Monday to Friday from 10:30 a.m. to 12 p.m. and from 4:00 p.m. to 8:00 p.m.
here-api
here-api
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
asked Mar 28 at 10:24
RaúlRaúl
124 bronze badges
124 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
The format for specifying access hours is as xsd type xs:datetime only
DDhh:mm:ss[Z|(+|-)hh:mm]|DDhh:mm:ss[Z|(+|-)hh:mm]
For access hours days (DD) are abbreviated with two lowercase characters: mofor Monday, tu for Tuesdainy, we, th, fr, sa, su. Hours (hh) must integer values in the range 0..23. Minutes and seconds must be from the range 0..59.
The first time stamp defines the beginning of the access hours, the second time stamp defines the end of the access hours. The access hours constraints require a service time, which is the length time (to be spent) at the waypoint,
for example acc:mo09:30:00-01:00|12:00:00-01:00;st:600
Specifying the multiple days for one destination is not possible, though you can specify multiple destinations with individual access hours like below illustration
https://wse.api.here.com/2/findpickups.json?departure=2015-05-04T8:00:00%2b01:00&mode=fastest;car;traffic:disabled&app_id=YOUR_APP_ID&app_code=YOUR_APP_CODE&start=DuisburgRuhrort;51.4541,6.7406&destination1=ZecheZollverein;51.486,7.0459;acc:mo09:00:00%2b01:00%7cmo10:00:00%2b01:00;st:60&destination2=KokereiZollverein;51.4879,7.0337;acc:mo10:30:00%2b01:00%7cmo12:00:00%2b01:00;st:600&destination3=MuehlheimRuhrHbf;51.432,6.886;acc:mo08:00:00%2b01:00%7cmo09:00:00%2b01:00;st:60&end=DuisburgHafen;51.4576,6.7717&improveFor=TIME
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
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/4.0/"u003ecc by-sa 4.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%2f55395234%2ffleet-waypoint-set-range-of-access-hours-by-waypoint%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
The format for specifying access hours is as xsd type xs:datetime only
DDhh:mm:ss[Z|(+|-)hh:mm]|DDhh:mm:ss[Z|(+|-)hh:mm]
For access hours days (DD) are abbreviated with two lowercase characters: mofor Monday, tu for Tuesdainy, we, th, fr, sa, su. Hours (hh) must integer values in the range 0..23. Minutes and seconds must be from the range 0..59.
The first time stamp defines the beginning of the access hours, the second time stamp defines the end of the access hours. The access hours constraints require a service time, which is the length time (to be spent) at the waypoint,
for example acc:mo09:30:00-01:00|12:00:00-01:00;st:600
Specifying the multiple days for one destination is not possible, though you can specify multiple destinations with individual access hours like below illustration
https://wse.api.here.com/2/findpickups.json?departure=2015-05-04T8:00:00%2b01:00&mode=fastest;car;traffic:disabled&app_id=YOUR_APP_ID&app_code=YOUR_APP_CODE&start=DuisburgRuhrort;51.4541,6.7406&destination1=ZecheZollverein;51.486,7.0459;acc:mo09:00:00%2b01:00%7cmo10:00:00%2b01:00;st:60&destination2=KokereiZollverein;51.4879,7.0337;acc:mo10:30:00%2b01:00%7cmo12:00:00%2b01:00;st:600&destination3=MuehlheimRuhrHbf;51.432,6.886;acc:mo08:00:00%2b01:00%7cmo09:00:00%2b01:00;st:60&end=DuisburgHafen;51.4576,6.7717&improveFor=TIME
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
add a comment
|
The format for specifying access hours is as xsd type xs:datetime only
DDhh:mm:ss[Z|(+|-)hh:mm]|DDhh:mm:ss[Z|(+|-)hh:mm]
For access hours days (DD) are abbreviated with two lowercase characters: mofor Monday, tu for Tuesdainy, we, th, fr, sa, su. Hours (hh) must integer values in the range 0..23. Minutes and seconds must be from the range 0..59.
The first time stamp defines the beginning of the access hours, the second time stamp defines the end of the access hours. The access hours constraints require a service time, which is the length time (to be spent) at the waypoint,
for example acc:mo09:30:00-01:00|12:00:00-01:00;st:600
Specifying the multiple days for one destination is not possible, though you can specify multiple destinations with individual access hours like below illustration
https://wse.api.here.com/2/findpickups.json?departure=2015-05-04T8:00:00%2b01:00&mode=fastest;car;traffic:disabled&app_id=YOUR_APP_ID&app_code=YOUR_APP_CODE&start=DuisburgRuhrort;51.4541,6.7406&destination1=ZecheZollverein;51.486,7.0459;acc:mo09:00:00%2b01:00%7cmo10:00:00%2b01:00;st:60&destination2=KokereiZollverein;51.4879,7.0337;acc:mo10:30:00%2b01:00%7cmo12:00:00%2b01:00;st:600&destination3=MuehlheimRuhrHbf;51.432,6.886;acc:mo08:00:00%2b01:00%7cmo09:00:00%2b01:00;st:60&end=DuisburgHafen;51.4576,6.7717&improveFor=TIME
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
add a comment
|
The format for specifying access hours is as xsd type xs:datetime only
DDhh:mm:ss[Z|(+|-)hh:mm]|DDhh:mm:ss[Z|(+|-)hh:mm]
For access hours days (DD) are abbreviated with two lowercase characters: mofor Monday, tu for Tuesdainy, we, th, fr, sa, su. Hours (hh) must integer values in the range 0..23. Minutes and seconds must be from the range 0..59.
The first time stamp defines the beginning of the access hours, the second time stamp defines the end of the access hours. The access hours constraints require a service time, which is the length time (to be spent) at the waypoint,
for example acc:mo09:30:00-01:00|12:00:00-01:00;st:600
Specifying the multiple days for one destination is not possible, though you can specify multiple destinations with individual access hours like below illustration
https://wse.api.here.com/2/findpickups.json?departure=2015-05-04T8:00:00%2b01:00&mode=fastest;car;traffic:disabled&app_id=YOUR_APP_ID&app_code=YOUR_APP_CODE&start=DuisburgRuhrort;51.4541,6.7406&destination1=ZecheZollverein;51.486,7.0459;acc:mo09:00:00%2b01:00%7cmo10:00:00%2b01:00;st:60&destination2=KokereiZollverein;51.4879,7.0337;acc:mo10:30:00%2b01:00%7cmo12:00:00%2b01:00;st:600&destination3=MuehlheimRuhrHbf;51.432,6.886;acc:mo08:00:00%2b01:00%7cmo09:00:00%2b01:00;st:60&end=DuisburgHafen;51.4576,6.7717&improveFor=TIME
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
The format for specifying access hours is as xsd type xs:datetime only
DDhh:mm:ss[Z|(+|-)hh:mm]|DDhh:mm:ss[Z|(+|-)hh:mm]
For access hours days (DD) are abbreviated with two lowercase characters: mofor Monday, tu for Tuesdainy, we, th, fr, sa, su. Hours (hh) must integer values in the range 0..23. Minutes and seconds must be from the range 0..59.
The first time stamp defines the beginning of the access hours, the second time stamp defines the end of the access hours. The access hours constraints require a service time, which is the length time (to be spent) at the waypoint,
for example acc:mo09:30:00-01:00|12:00:00-01:00;st:600
Specifying the multiple days for one destination is not possible, though you can specify multiple destinations with individual access hours like below illustration
https://wse.api.here.com/2/findpickups.json?departure=2015-05-04T8:00:00%2b01:00&mode=fastest;car;traffic:disabled&app_id=YOUR_APP_ID&app_code=YOUR_APP_CODE&start=DuisburgRuhrort;51.4541,6.7406&destination1=ZecheZollverein;51.486,7.0459;acc:mo09:00:00%2b01:00%7cmo10:00:00%2b01:00;st:60&destination2=KokereiZollverein;51.4879,7.0337;acc:mo10:30:00%2b01:00%7cmo12:00:00%2b01:00;st:600&destination3=MuehlheimRuhrHbf;51.432,6.886;acc:mo08:00:00%2b01:00%7cmo09:00:00%2b01:00;st:60&end=DuisburgHafen;51.4576,6.7717&improveFor=TIME
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
answered Apr 1 at 6:15
HERE Developer SupportHERE Developer Support
3,4521 gold badge9 silver badges15 bronze badges
3,4521 gold badge9 silver badges15 bronze badges
add a comment
|
add a comment
|
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
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%2f55395234%2ffleet-waypoint-set-range-of-access-hours-by-waypoint%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
