Hi!

I'm creating OD cost matrices of walking distance between transit stops in Chicago. So, because my origins and destinations are the same files and because pedestrians don't care about one-way restrictions, the distance from Stop A to Stop B is always equal to the distance from Stop B to Stop A.

Is there a way to cut down the analysis time and output file size by having Network Analyst calculate the distance between A and B only once, instead of twice (A->B and B->A)?

Thanks!

~Melinda

PS. I have already cut down the run time and output file size by using cutoff distances. Still, when your cutoff distance is 2 miles, it still takes forever and results in a very large output file.

I'm creating OD cost matrices of walking distance between transit stops in Chicago. So, because my origins and destinations are the same files and because pedestrians don't care about one-way restrictions, the distance from Stop A to Stop B is always equal to the distance from Stop B to Stop A.

Is there a way to cut down the analysis time and output file size by having Network Analyst calculate the distance between A and B only once, instead of twice (A->B and B->A)?

Thanks!

~Melinda

PS. I have already cut down the run time and output file size by using cutoff distances. Still, when your cutoff distance is 2 miles, it still takes forever and results in a very large output file.

Second, how many origins and destinations do you have for this solve? By any chance, does your network datset have hierarchy and it is set ON by default, then, if you are usinga 2 mile cutoff, set the hierarchy to OFF and the performance will increase. Note that hierarchy helps when you have long distance routes, but not when you have small cutoff's like 2 miles.

Jay Sandhu