Latest Contributions by MelindaMorang

Yes, the OD Cost Matrix will use any non-restricted network components, including streets and transit lines.  Otherwise, how would the traveler walk from their initial location to the bus/rail stop in the first place, and how would they make transfers from one line to another if they have to walk around the block or something?  In some cases, walking the whole way may simply be faster or more practical than taking transit.   The OD Cost Matrix tool does not store the "traversal result", meaning after it has done the calculation of travel time and distance, it doesn't remember anything about what parts of the network were used.  So, in general, for any OD Cost Matrix problem, it is not possible to determine which streets, or transit lines, were used.  If you want this information, you can use the Closest Facility solver or the Route solver.   For Route or Closest Facility, you can use the Copy Traversed Source Features tool to determine which network dataset components were used and post-process those results however you want.  For the old Add GTFS to a Network dataset toolbox (which is no longer supported, by the way), you can use the special Copy Traversed Source Features (with Transit) tool, which wraps the core version of the tool with some special transit information.   Regarding when you can add multiple GTFS datasets: In the old Add GTFS to a Network Dataset tool, just dump both of them in as input when you run the 1) Generate Transit Lines and Stops tool.   I encourage you to spend some more time with that User's Guide if you're having trouble.  Because the tool is deprecated, I cannot provide extensive help with it.   As for whether you should or shouldn't combine your multiple datasets - It really depends on what you're trying to do.  If you are trying to model the way real passengers travel, then you should probably include both.  On the other hand, if you're trying to model the differences in bus service vs rail service, you should probably keep them separate.   If you switch to using the newer tools in ArcGIS Pro, there is a way to exclude transit modes in the analysis (see the section on supported parameters here).  So, you could build the network to include bus and rail, but for a particular analysis, you could "turn off" rail service using the "Exclude modes" parameter. ... View more

It is not available in ArcGIS Pro yet. We are actively working on this feature and hope to make it available to customers soon. ... View more

DanPatterson1's link is correct.  I will repost the response here (with better formatting) in case other users have this question. This behavior is as designed. The feature datasets and feature classes for network analysis layers use automatically-generated unique names. In previous releases, this was done using a numbering scheme, but this was changed later on to a string of alphanumeric characters.   When writing scripts, you should not try to access the network analysis layer’s sublayers directly by their data paths, as this is not a supported workflow and the naming convention is not static or guaranteed. Instead, here are two ways to directly access the results of a network analysis: Method 1 Use this method if you have a layer-based workflow in a python script. Retrieve the output sublayer’s layer object and grab the data source from this or just use the layer object itself as input into further tools. Here is an example for a Closest Facility layer. You can retrieve the Routes sublayer object from the parent Closest Facility layer object like this: routes_sublayer = layer_object.listLayers("Routes"])[0] You can then do routes_sublayer.dataSource if you want to see the actual catalog path to the data source. You can use that catalog path or the routes_sublayer object itself as input into other geoprocessing tools. Note that with the release of ArcGIS Pro 2.7, you will be able to use the new arcpy.na.GetNASublayer() function to retrieve the sublayer of a parent layer instead of the listLayers() method. To see a full workflow example similar to this, see the “MakeODCostMatrixAnalysisLayer example 4” code sample here: https://pro.arcgis.com/en/pro-app/tool-reference/network-analyst/make-od-cost-matrix-analysis-layer.htm (This uses OD Cost Matrix instead of Closest Facility, but it’s the same idea.) Method 2 This is an entirely different way of solving a network analysis problem in python, one that does not involve layers at all. In ArcGIS Pro, we introduced a new python module, arcpy.nax, that provides a new python interface for doing network analysis. The new interface is more pythonic and easier to use in many ways. You can learn the basics of how it works here: https://pro.arcgis.com/en/pro-app/arcpy/network-analyst/performing-network-analysis.htm To summarize, you create a network analysis object for the solver you want, load the desired inputs, solve, and then retrieve the results in one of several ways. You can use the export() method on the solver result object to save the outputs to a feature class. You can also retrieve the outputs using a cursor, so it’s possible to retrieve only the fields you care about and write them directly into another table that already has your desired schema. ... View more