Latest Contributions by MelindaMorang

You're correct that the Directions tool doesn't work when the network analysis layer uses a service as its network data source.  However, turn-by-turn directions are available.  You can print them from the Directions pane.  Or, if you want to do something more custom with them, you can access the DirectionPoints and DirectionLines feature classes in the feature dataset that stores the network analysis layer's data. To find the feature dataset where the network analysis layer's data is stored: Open the properties of the network analysis layer by right-clicking or double-clicking in the Contents pane. Go to the Source page Go to the Analysis Data Source section Refer to the Database and Feature Dataset rows in the table. You'll find the DirectionPoints and DirectionLines feature classes like this: The schema of those feature classes is documented here (for Route): https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/route-output-data-types.htm#ESRI_SECTION1_D2B51A15DC6D45D6AF1167156492240A  (I know this is the arcpy.nax documentation, but it's the same schema.)  The other solvers that support directions have a nearly identical schema, with some minor differences in the ID fields that refer back to the original inputs. Does this serve your needs?  If not, please let us know specifically which features of the Directions tool you would like to see implemented (which output type, etc.). ... View more

Did the Closest Facility solve generate any warning messages like ‘No "Facilities" found for "Unnamed (ObjectID = 1)" in "Incidents".’? I suspect the facilities may be on parts of the network that are disconnected from the rest of the network due to some sort of connectivity problem.  Check whether the roads they're located on are properly connected to the surrounding roads.  You can use the Explore Network tool to click on roads to see what other roads they're connected to. It could also be a problem with a one-way street being incorrectly configured, or a turn restriction preventing travel through an intersection, if you're modeling turns. ... View more

Hello @tcrammond.  Sorry about this.  Unfortunately many of the arcpy modules don't behave nicely with linters, for a variety of technical reasons.  I will investigate this and see what options we have for improving the experience.  However, regardless of what Pylance is telling you, the module should still work as documented when the code is run. Could you please tell me what version of ArcGIS Pro you're running?  I know we made some improvements to arcpy.nax linting and type hinting in the 3.2 release, but it may have been in a limited area. ... View more

Supporting navigation workflows with the Waste Collection solver requires substantial design and non-trivial implementation.  We recognize this as a customer need and are considering our options.  The best thing for you to do is to contact Esri Support or your Esri representative and ask them to add you to the existing official enhancement request for this issue, case # ENH-000177080. ... View more

Sorry, no, Esri doesn't have any new functionality to address this that I'm aware of.  The best thing for you to do is to reach out to your Esri account representative to describe your use case and the functionality you would like to see. ... View more

DistanceToNetworkInMeters is the distance in meters between the point's geographic location and the position where it was located on the network.  Here's some documentation explaining how points are located on the network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/locating-analysis-inputs.htm ... View more

The likely culprits for this type of problem include: The network is disconnected somewhere. It may not be at the intersection you expect, but it could be at some on-ramp or other intersection along the expected route. Some roads along your expected route are incorrectly restricted to travel. Your cost attributes are calculating the travel cost incorrectly.  Either that highway has an unexpectedly low cost, or some other road along your expected route has an unexpectedly high cost. You have some sort of turn restriction preventing travel from one road to another. See this post for some tips on how to debug and diagnose the problem. ... View more

Oh, that makes sense.  So your "landmarks" must have been included in the network as a junction source, and some of them were just sitting there by themselves and not connected to anything. I'm not sure what you mean by "landmarks," but if you mean landmarks that get used in your turn-by-turn directions, here's the documentation for how to set that up: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/setting-directions.htm#GUID-7996C48B-1926-493B-A09F-041ACFC5BE3B.  They should not be included as a junction source but instead as a Landmarks table. ... View more

Hi Karina. Here is some documentation explaining all about how points get located on the network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/locating-analysis-inputs.htm.  In particular, the "Settings that affect how inputs are located" is relevant to your question. However, I suspect that the locate settings aren't actually the cause of the solve failure.  If the point were unlocated, you would see different errors.  They would tell you that the point wasn't located and that at least two valid stops are required for a route.  Instead, your error indicates that no path could be found between the two stops. The first thing to check is where the stop actually located.  It probably found some other, closer spot on the network to locate.  You can check the stop's SnapX and SnapY fields and use the XY Table to Point tool to map the snapped location and see where it falls on the network. Assuming the stop located on some other network edge, the next thing to do is to figure out why no path could be found between the two stops.  That's likely an issue with the network dataset; the roads are disconnected somehow.  See this post for some ideas and diagnosis steps. ... View more

Hello Aidan (and others).  This is Melinda from Esri's Network Analyst development team.  The other replies here have some good suggestions and, on a technical level Network Analyst should be capable of doing the type of modeling you want if you can configure your data and the network dataset attributes in a way that makes sense to you.  Some combination of a cost attribute (to model travel time based on slope and other factors) and restriction attributes (to prohibit or deter travel on streets that are unsuitable or undesirable for cyclists) can be configured.  Often times people try to calculate a Level of Traffic Stress for each street, and this could be used in configuring restrictions, even different restrictions depending on the type of cyclist. We unfortunately don't have any out-of-the-box templates or tutorials to assist with this, but that's something I'm interested in creating.  I'm actually in the process of researching this and trying to determine what the best practice is.  Aidan and anyone else reading this: If you are trying to create or have created a network dataset for modeling travel by bicycle and would be willing to answer some questions or be interviewed to help me move this project forward, please reach out to me at mmorang@esri.com.  Thank you! ... View more