I am using OD Cost Matrix layer in order to find distances between many origins and destinations points. It works fine, but I want to make sure the results make sense, and since OD Cost Matrix can only produce straight lines (and not true route shapes), I tried to calculate some specific origin-destination pairs using a Network Analyst regular Route layer and compare them to the OD Cost Matrix results.
However, in some of the cases the distances seem to be different between the two methods, even when I use the exact same analysis settings and network restrictions. Sometimes it's only a small gap, but in other cases it's probably a whole different route.
Shouldn't the two tools produce the exact same routes?
Best Answer
So here are the code and summary of the aforementioned bugs, as requested by @Chris W. Basically they seem to refer to the same issue and to have the same cause, i.e. a problem with the OD cost algorithm.
They've been found between versions 10.0 and 10.2.2 and are all assigned.
As I commented before, an alternative could be to use Closest facility analysis (in an automated process) to get a similar output and see if the results are more reliable. I suppose the feasibility of this depends largely of the number of origin and destination points.