Afficher les statistiques de voyage O/D individuelles dans Calculate Accessibility Matrix

Question

Bonjour @MelindaMorang , j'essaie d'obtenir la sortie qui était disponible dans les anciens outils d'ArcMap maintenant dans Pro. L'outil calculate time matrix avait l'habitude d'avoir une option pour enregistrer les calculs individuels. C'est-à-dire, j'ai besoin de la sortie du temps total de trajet, de la distance, du temps de marche, du temps d'attente, etc. pour chaque paire O/D pour chaque heure sélectionnée. Est-ce toujours possible ? De plus, s'il existe un moyen de combiner certaines fonctionnalités des Copy Traversed Transit features pour chaque enregistrement, ce serait incroyable. J'essaie de construire une régression en examinant divers facteurs sur les temps de trajet, et connaître ces informations ainsi qu'au moins le numéro de route de départ serait très utile. Toute suggestion serait grandement appréciée.<\/SPAN><\/P>

Melinda Morang · Answer

Hello again.  Just wanted to follow up on a part of this thread.  I have created a downloadable script tool that adds transit information to the output of Copy Traversed Source Features, including the Run ID, ride time, wait time, and transit trip arrival and departure time to each transit segment.

The tool runs a post-process that queries the Public Transit Data Model tables to make a good guess as to which transit runs were used for each segment based on the constraints of the analysis settings and the arrival and departure times for that segment.  This isn't a terribly efficient way to solve the problem, but it gets the job done.

Please consider this a prototype.  Definitely let me know if the tool doesn't return the output you want or if you experience any problems. I would like to get this behavior into the core software at some point, and feedback on this prototype will be very valuable in doing so.

Note that this functionality is not yet integrated into the Route version of the Calculate Travel Time Statistics tool like we discussed above.  That's up next on my plate but will require some surgery on that tool. I'll report back here when I've done that.

Download the tool from ArcGIS.com or GitHub.  (This download includes several tools; the new one is called Copy Traversed Source Features With Transit.)

Melinda Morang · Answer

Hi Phillip.  Sounds like you have multiple questions and problems, so let me separate them by category so we don't get all mixed up and so I don't forget anything.

Validation error

The validation error you see in the tool appears to me like a python path error.  I made changes to the python files in the latest update, and it looks like Pro isn't picking it up.

* Have you closed and reopened Pro since you updated the tool files?  If not, do that.  It will probably fix it.
* If that doesn't work, then my guess is the Python files associated with the tool are messed up, and you have somehow mixed the old files with the new.  Either you downloaded the updated version of the tool and not everything got copied or updated correctly, or if you pulled the GitHub version, something didn't go right.  I would delete all the files associated with the tool and start afresh.

Limiting walk time/distance

Regarding the walking problem - yeah, that's a weakness of our implementation of this transit stuff.  There is no way to separately cap the walking time or distance from the overall travel time.  I know this is something we need to do, but the core structure of Network Analyst itself does not give me a way to make this happen.  Best I can suggest is you talk to your Esri representative or leave a post on the ArcGIS Ideas site advocating for this.

You could also put barriers around your stops to prevent people from walking further than your desired distance, although you have to make them not cross the transit lines.

Cutoff walk time being ignored

"the cutoff walk time in the origins seems to be ignored"

Can you tell me more about this?  Please tell me exactly what you're seeing so I can determine if this is a bug.

Joined names

"the output of the individual iterations joins the origin and destination names into one field"

Are you referring to the Calculate Travel Time Statistics (OD Cost Matrix) tool here, or Calculate Accessibility Matrix? (Super helpful to me if you are very explicit about which tool you're talking about.)

Are you referring to the Name field in the output OD Lines?  You can parse that if you want to, but if you want to get the Name fields from the original Origins and Destinations tables, you should just join the output Origins and output Destinations to the output OD Lines using the OriginOID and DestinationOID fields in Lines.  They correspond to the ObjectID fields in the output Origins and Destinations.

This documentation page has the complete schema for the outputs.  Calculate Travel Time Statistics (OD Cost Matrix) tool output is described explicitly here.

PhillipCarleton · Answer

Sorry for the delay. I'm actually using both but mainly the OD Cost Matrix. I use the route with the traversed features tool to try to understand the behavior of the algorithm. I've found I have to do quite a bit of teasing with the walking speed to keep down the number of only walking or mostly walking trips. Since I'm using bus stops as both the origins and destinations (I'm only interested in waiting and in-vehicle travel times, I've found that at 80 m/min the shortest path will actually walk along the road to other stops instead of waiting on the next bus. This would seem to imply that a rider would have perfect information about when the next bus was to arrive which seems unrealistic to me. I can't set the walk speed to 0 though because that wouldn't allow for transfers. Even though 20 m/min is very slow and unrealistic I think that seems to be the best balance I've found. Just two other small issues I'm finding is that the cutoff walk time in the origins seems to be ignored and the output of the individual iterations joins the origin and destination names into one field. I just go back to edit the results as needed though (i.e., removing trips with too much walking and pulling out stop IDs).

I really appreciate all the work on the parallel version of the statistics tool. I have given it a try but am having errors that are preventing it from running. I'm not sure if I'm doing something wrong or if there is a bug that I've found. Would you be able to look at the screenshot I've added and see if I'm doing something wrong? I'd appreciate any thoughts on this issue.

ODCMErrorMessages.png