I am trying to get a Vehicle Routing Problem to work as a geoprocessing service on one of our servers.
I used the default_date with unix time stamp in miliseconds and set the times of orders and depot in the format of "10:00 AM UTC". Now I get a time constraint violation for the orders ("ViolatedConstraints": 32)
If I take out the line "MaxViolationTime1":0 from the orders in my REST url, a route is calculated with correct travel times and distances and I can see the results. Especially the following lines (attributes of output route) caught my eye:
... "TotalCost": 42.5174562651664, "RegularTimeCost": 42.5174562651664, ... "TotalTime": 42.5174562651664, "TotalOrderServiceTime": 20, ... "TotalTravelTime": 22.517456265166402, ... "StartTime": 1369180800000, "EndTime": 1369183351047, ... "TotalViolationTime": 30.35018770210445, ...
I can change the default date and the earliest/latest start time, but the route starts still on the current date, at 2 AM. Could it be that some date and time options are "hard coded" somewhere in the module that was used to create the geoprocessing service? I checked the module again and can't find any options to change default date and time settings.