Select to view content in your preferred language

Fleet Vehicle Service fails when first order has null or zero coordinates

508
2
Jump to solution
07-24-2023 04:01 AM
Roxana_ElenaUrdea
Regular Contributor

Hi!

I am using this  service: https://logistics.arcgis.com/arcgis/rest/services/World/VehicleRoutingProblem/GPServer/SolveVehicleR... and I noticed a couple of issues:

1. Solve fails if only the first order has x and y coordinates = 0. It seems that everything becomes unlocated (even the depots).

Roxana_ElenaUrdea_1-1690196262140.png

 

2. Solve fails if any order has NULL coordinates.

  1. Roxana_ElenaUrdea_0-1690196161303.png

I also used the 'ignore_invalid_order_locations' set to 'true'

 

Is this a normal behaviour?

 

Thank you,

Roxana

0 Kudos
1 Solution

Accepted Solutions
MaxZeng
Esri Contributor

Hey Roxana,

We are looking into both issues.

The first one is because we are trying to use the first order to determine the network dataset to use, and since it has wrong geometry, we couldn't determine the network dataset, so we fail to locate any inputs. We are revisiting this logic. The second one we are still investigating.

I will provide an update once we have a fix for both issues.

In the meanwhile, I think your request needs to have a valid geometry for first order, and for subsequent orders, just make sure there is geometry (you can have x, y as 0 or -1 when you don't have coordinates for the orders), and with ignore_invalid_order_locations set to true, we should ignore those inputs that don't have valid geometry.

Thank you for brining these issues to our attention!

Max

View solution in original post

2 Replies
MaxZeng
Esri Contributor

Hey Roxana,

We are looking into both issues.

The first one is because we are trying to use the first order to determine the network dataset to use, and since it has wrong geometry, we couldn't determine the network dataset, so we fail to locate any inputs. We are revisiting this logic. The second one we are still investigating.

I will provide an update once we have a fix for both issues.

In the meanwhile, I think your request needs to have a valid geometry for first order, and for subsequent orders, just make sure there is geometry (you can have x, y as 0 or -1 when you don't have coordinates for the orders), and with ignore_invalid_order_locations set to true, we should ignore those inputs that don't have valid geometry.

Thank you for brining these issues to our attention!

Max

Roxana_ElenaUrdea
Regular Contributor

Thank you Max, very helpful!