Latest Contributions by MelindaMorang

The Network Analyst Ready-to-Use Services tools will be deprecated in ArcGIS Pro 3.0, so we will not make any further enhancements to them. However, in general, you can re-open any geoprocessing tool from the History pane, and it will automatically populate with the settings you used in that prior tool run. I think that will work for your needs. ... View more

I see. Yeah, that's a very reasonable thing to want to do. Unfortunately, it's more complicated than simply needing the geometry of the transit lines. What you really need is an enhanced version of Copy Traversed Source Features that includes the transit trips that were actually used, not the lines themselves. The LineVariantElements may be shared by all trips running along that line. However, although under the hood, Network Analyst knows which transit trips were used, the architecture of the network dataset and the evaluator and solver do not allow us to pass that information out of the evaluator where it can be accessed by the traversal result. So, the information is there, but it's inaccessible. I know, super annoying... Note that you should not use barriers to obstruct transit lines. If a barrier blocks one transit line segment, the solver is not smart enough to know that the transit line segments further on will also be delayed or not running. Each transit line segment just checks to see what the schedule is and uses it without regard for anything that may have happened upstream. Instead, if you want to turn service on and off for a particular line, trip, mode, etc., you can do this using the special parameters available with the Public Transit evaluator described here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/public-transit-evaluator.htm#ESRI_SECTION1_9FF9489173C741DD95472F21B5AD8374. This video may also be helpful. With all that said, barriers are perfectly valid to use for blocking pedestrian areas or streets. Just don't put them on transit lines. ... View more

The Copy Traversed Source Features tool will give a warning about empty output being generated whenever any of the three outputs (edges, junctions, or turns) is empty. This very frequently happens for turns. If your network dataset doesn't even include turns (the one from that tutorial doesn't), then you will always see this message. However, you should see something in the output edges and junctions feature classes.  Do you see the layers in the map, and do they have something in them? They should. If not, please include more details, and we'll figure it out. Regarding your other question about making the transit lines match the streets they run on: Unfortunately, that is not possible. LineVariantElements are constructed from GTFS schedule data, which is only loosely tied to the transit line geometries defined in the GTFS shapes.txt file. That file is often missing or of poor quality and is not suitable for creating a well-connected, routable network. The way our transit networks are built, the geometry of the transit lines is unimportant, as long as they connect properly at stop locations. If you want to visualize your public transit lines, you can use the GTFS Shapes To Features tool, but this is unrelated to the network dataset and is purely for visualization purposes. If the network dataset LineVariantElement geometry matters to you a lot, you could attempt to manually edit the LineVariantElements to match the geometry of the GTFS shapes, but I think this would be very arduous and could generate a lot of errors if you accidentally made things disconnected. Could you tell me why the geometry of the LineVariantElements matters to you? I hear a lot of requests for this, so I would like to understand your motivations so I can consider whether this is something we should support in the future. ... View more

The "min" symbol there is merely informative. It tells you that the impedance units of the selected travel mode are in Minutes. The travel mode you have selected right now is called "FireTruckTime". To make this work as intended, your travel mode should be configured to use your Minutes impedance attribute that you were working on earlier. ... View more

From your screenshot, it looks like the yellow polygon has a Cutoff of 0, which doesn't really make sense and doesn't seem to match what's on the screen. What are the Cutoff values configured in the Service Area layer ribbon? If you continue to struggle, you might need to call Esri Support to get some help. They can walk you through the correct procedure and debug whatever is wrong with your network. ... View more

Your field evaluator setup looks fine. However, I notice you have a 2-minute delay for every turn configured under the Turns <default> evaluator. My guess is this is what's slowing everything down. Basically any time the traveler transitions from one street segment to another, they incur a 2-minute delay. ... View more

If the Service Areas look reasonable when you're optimizing for distance, my guess is your network connectivity is fine. If you had a connectivity problem, distance-based analyses would also look incorrect. Rather, it's more likely there is a problem with the way your Time impedance attribute is configured. You should take a look at the cost attribute. Do the units agree with whatever field you're drawing from, if you're using a field evaluator?  How the evaluators are configured, and does it seem correct? ... View more

No, that is not the correct procedure. The Attr_ fields are in the Service Area layer. They are not built into the network dataset. It sounds like you created your own network dataset. You should have created an Impedance attribute with some name, and perhaps the impedance values are being calculated using the Time field from your network dataset's source feature class. That's fine. The thing you care about is the name of the impedance attribute in the network dataset. Let's say it's called MyImpedance. Now look at your Service Area layer and open the attribute table for the Facilities sublayer. You should see a field called Attr_MyImpedance. Put your value of 0.5 in there. (Assuming your impedance attribute has units of Minutes. If not, adjust the value for the correct units.) Here is the correct documentation for a Service Area layer in ArcMap: https://desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/service-area.htm#GUID-23AFA603-CDB3-48A6-9E92-C5B0443CEC3E ... View more

I can't tell from your question how you are solving your Service Area analysis (using a layer in Pro? using Python arcpy.nax?), but you are correct that it's a simple setting. For a Service Area layer in the Pro UI, you can use the "Attr_" prefix fields described here. The field name relates to the impedance attribute you're using in the analysis, so if your travel mode uses an impedance attribute called "TravelTime", the field name to add your turn out time to is "Attr_TravelTime". For a Service Area analysis using the arcpy.nax solver objects, you can use the AdditionalTime, AdditionalDistance, or AdditionalCost field (depending on what you're optimizing - my guess is time). This is described here. ... View more

A feature dataset is not the same thing as a feature layer or feature class. Perhaps you're attempting to select the wrong item as the input to the Create Network Dataset tool. If you haven't already, check out our Create a network dataset tutorial. ... View more

The answer to this question is "sort of". It depends on what details are important to you. You can use the Copy Traversed Source Features tool to get a list of the individual network elements (edges, junctions, and turns) that were used in the route. Bus LineVariantElement features and the time of day they were used will be included in these results. However, this will NOT give you the specific trip_id and other details about which bus was actually used. There is, unfortunately, no way to access that information. What are you trying to do? Perhaps we can brainstorm another way to achieve it. ... View more