OD Cost Matrix with End Time (Arrive At)

04-21-2017 02:09 PM
Status: Open
Labels (1)
Occasional Contributor

So currently the Network Analyst has the Closest Facility tool and the Origin-Destination Cost Matrix tool that are similar with the two main differences (for me at least) being:

1) CF ranks facilities and is not capable of handing matrix level volume

2) CF allows for both start time AND end time 

The Service Area tool also accommodates for end time (arrive at) as well as start time (depart at).

So the only network tool that doesn't allow for this is OD Cost Matrix.   

I would very much like to see the OD cost matrix tool to allow for end time (arrive at) as well as the existing start time (depart at).  The CF tool is essentially doing this but only allowing for a handful of results (facilities to find).

Please, please, please accommodate end time in the OD Cost Matrix tool...(psssst Google Directions mapping services does it but you have to develop a batch tool on your own and have an api key)

Hierarchy Rank Settings (optional)

Prior to version 10, this parameter allowed you to change the hierarchy ranges for your analysis from the default hierarchy ranges established in the network dataset. At version 10, this parameter is no longer supported. If you wish to change the hierarchy ranges for your analysis, update the default hierarchy ranges in the network dataset.

Output Path Shape (optional)

Specifies the shape type for the route features that are output by the analysis.

  • TRUE_LINES_WITH_MEASURES—The output routes will have the exact shape of the underlying network sources. Furthermore, the output includes route measurements for linear referencing. The measurements increase from the first stop and record the cumulative impedance to reach a given position.
  • TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.
  • STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.
  • NO_LINES—No shape will be generated for the output routes.

No matter which output shape type is chosen, the best route is always determined by the network impedance, never Euclidean distance. This means only the route shapes are different, not the underlying traversal of the network.

U-Turn Policy (optional)

The U-Turn policy at junctions. Allowing U-turns implies the solver can turn around at a junction and double back on the same street. Given that junctions represent street intersections and dead ends, different vehicles may be able to turn around at some junctions but not at others—it depends on whether the junction represents an intersection or dead end. To accommodate, the U-turn policy parameter is implicitly specified by how many edges connect to the junction, which is known as junction valency. The acceptable values for this parameter are listed below; each is followed by a description of its meaning in terms of junction valency.

  • ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.
  • NO_UTURNS—U-turns are prohibited at all junctions, regardless of junction valency. Note, however, that U-turns are still permitted at network locations even when this setting is chosen; however, you can set the individual network locations' CurbApproach property to prohibit U-turns there as well.
  • ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).
  • ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY—U-turns are prohibited at junctions where exactly two adjacent edges meet but are permitted at intersections (junctions with three or more adjacent edges) and dead ends (junctions with exactly one adjacent edge). Oftentimes, networks have extraneous junctions in the middle of road segments. This option prevents vehicles from making U-turns at these locations.

If you need a more precisely defined U-turn policy, consider adding a global turn delay evaluator to a network cost attribute, or adjusting its settings if one exists, and pay particular attention to the configuration of reverse turns. Also, look at setting the CurbApproach property of your network locations.

Restrictions (optional)

List of restriction attributes to apply during the analysis.