Edit: this description of the problem is outdated; see my 2nd post. Ready/due values seem to be mostly ignored for me apart from the weird occurrence described below I haven’t been able to get it to work:
Using the v2 API I wanted to revisit my home depot somewhere around the evening, so I added another entry in the locations list with “ready” and “due” parameters. However, it seems to ignore specifically the ready and due parameters and just immediatly visits the home depot twice at the start of the route:
node_id,lat,lng,arrival,distance
99999,51.162978,4.1415526,0,0.0
99999,51.163878,4.1416526,10,0.0
3437,51.2078344,4.07736,119,7.7
....
Look specifically at the 2nd last column: ‘arrival’ (0min-10min-119min). It does take into account the 100 minutes servicetime that I specified for the 2nd visit but it ignores the ready and due constraints:
{"address": 99992, "lat": 51.1338804, "lng": 4.5669902, "servicetime": 100, "ready": 435, "due": 465}
I’ve tried:
- Giving it a larger window of time.
- Giving it slightly different lat/lng than the first home depot node
- Giving at a higher service time to make sure it was applying at least some option set in the json object
None of these matters and it only takes into account the ready/due parameters if I give the second visit a different label (here 10000):
99999,51.162978,4.1415526,0,0.0
3437,51.2078344,4.07736,19,7.7
...
100000,51.162988,4.1415626,464,77.4
I can work around it but it still seems like unintended behaviour and poses some problems for me as the label is an id that I use, could this be fixed?