Latest Contributions by MelindaMorang

You can do this using global turns. ArcMap: https://desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/global-turns-about-global-turns.htm ArcGIS Pro: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/turn-category-evaluator.htm (Please note that ArcMap is entering mature support in March of 2024, and you are highly encouraged to migrate to Pro.) ... View more

This warning means that some origins couldn't find any destinations.  Either the origin is located on part of the network that's completely disconnected from where any of the destinations are located, or none of the destinations were close enough (if you're using an impedance cutoff).  Example: You used an impedance cutoff of 10km, and the closest destination is 11km away. It's possible that there is no problem here and the origins are just far away or on an island or something.  It's also possible that your underlying network geometry has some problems that need to be resolved. One good way to start diagnosing the problem is to do a Service Area analysis for each of the origins that didn't find any destinations.  If you use the Lines option for the output, you can see which streets in the network are connected to the origin and may be able to easily identify disconnected areas.  Service Area tutorial: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/service-area-tutorial.htm  You can use the Explore Network tool to investigate problem areas in more detail. https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/explore-network.htm We also have a little downloadable tool you can use to identify disconnected areas of the network: https://www.arcgis.com/home/item.html?id=b2227f745a6c4e1c94dd57810729d2a9  Since you're using OpenStreetMap, be sure to check your network dataset's connectivity policy.  Usually OpenStreetMap has long street features that extend through many intersections and have vertices there instead of endpoints, so you need to use Any Vertex connectivity. https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm Finally, although you didn't ask this specifically, if you find that solving your OD Cost Matrix is too slow, you might find this tool useful: https://github.com/Esri/large-network-analysis-tools  ... View more

Okay, thanks for following up.  If at some point you have more time and are able to share the problematic GTFS feed, I'd be happy to take a look and figure out why it's not working in the Pro tools. ... View more

Working on this for the Pro 3.2 release. ... View more

Hi.  I've never seen this error before, but I'd like to investigate.  Would you be able to share your data?  If you can't share it publicly, you can send me a private message through this system and we can work something out. ... View more

(Side note: If, by any chance, you are trying to do healthcare network adequacy calculations, Esri has some specific tools designed especially for that.  You would need to talk to your Esri representative to find out how to get started with that, though.) ... View more

Happy to help you with this. There's not quite enough information here for me to determine whether this will work for your needs, but this downloadable toolset for solving large Network Analyst problems may do the trick: https://github.com/Esri/large-network-analysis-tools If you just need the travel time and/or distance between origins and the closest destination (and not the route geometry), you can use the Solve Large OD Cost Matrix tool, and will go waaaaayyyy faster than what you're doing now.  It does a bunch of pre-processing to improve performance, chunks up the problem and solves it in parallel across all the cores of your machine, and also uses the arcpy.nax solver objects under the hood, which are faster than the network analysis layers you can use in a model. Also, here is a video from a DevSummit 2022 presentation about how to solve large network analysis problems: https://mediaspace.esri.com/media/t/1_hzppnv8p  ... View more

Great, I'm glad I was able to solve your problem. I don't think we will be able to incorporate the Large Network Analysis Tools into the core software for a variety of technical reasons, but my team continues to maintain them and expand them based on user feedback.  We are always working toward improving performance of the Network Analyst solvers, and you should be able to solve problems much larger than 1000x1000 with local data even without chunking. A lot of users ask us about the OD Cost Matrix analysis limits in the ArcGIS Online services, and while I can't promise any changes to those limits, I can send your feedback to our product manager. ... View more

Okay, I understand. I think you may be able to achieve at least part of your goal by simply running the Calculate Locations tool or the Add Locations tool and checking the Status field or the network location fields afterwards.  You don't actually need to do a solve operation to determine if the points are not routable. You can also set the Search Tolerance property to something fairly small to reduce the likelihood of the point getting snapped to another street that's far away. Does this help at all? ... View more

Hello Melisa.  The behavior you're seeing in Pro is as designed.  Points will always locate on the closest routable and non-restricted point on the network according to the specified locate settings and travel mode.  In your case, the closest edge is restricted, so it locates on the next-best option. When designing this behavior, our assumption is that there was no benefit to locating on a restricted edge or junction because this would just cause the route to fail or be unable to reach the point.  Could you tell me what you're trying to do and why you want to see the solve failure? A couple of other things that may be useful to you (just a guess, since I don't know what you're really trying to do): When a point locates somewhere that isn't the closest option because the closest option is restricted, the Status field in the attribute table will be set to 7, or "Not located on closest".  If you just need to determine which points aren't located where expected, you can filter the inputs to find rows with this value. You might be able to achieve your goals by adjusting various locate settings, such as setting a search query, adjusting search tolerance, etc. This documentation may help: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/locating-analysis-inputs.htm  ... View more

I think that option isn't available when you use the Load Locations dialog, but you can find it in the Add Locations tool.  That tool does the same thing, but it uses Geoprocessing.  https://desktop.arcgis.com/en/arcmap/latest/tools/network-analyst-toolbox/add-locations.htm Please note that ArcMap is will enter Mature Support in March 2024, which means you'll be limited in what help you can get.  Please work on migrating to ArcGIS Pro.  Note that in Pro, network analysis inputs are not located on restricted network elements by default, so Pro is automatically doing what you want already. ... View more

Hi KD.  I just wanted to check in with you to see if my proposed method to delete records in the data model tables with the GRouteType values you wanted to exclude worked for your needs.   ... View more

The Route Stops Sequence field is a long integer, so you can't add a letter to it.  Can you explain what you're trying to do?  Maybe we can come up with some better way to do it. ... View more

The limits are not solely in place to prevent users from accidentally consuming huge amounts of credits.  Rather, they are in place to ensure that the services continue to function adequately and remain performant using the back-end architecture they run on.  If a single user submitted an enormous OD Cost Matrix job, the service could become unresponsive for other users, and you may also run into limits in the amount of data you can send via a JSON response. If you need to solve a large OD Cost Matrix problem and want to use the AGOL service (indeed, a reasonable desire), you can download this toolbox to help solve large network analysis problems: https://github.com/Esri/large-network-analysis-tools.  This tool will automatically chunk up the problem into and solve the chunks in parallel using whatever data source you want.  For AGOL, the chunk size is limited to 1000 and the number of parallel processes is limited to 4, but you should get your answer eventually. Another option is to purchase Streetmap Premium so you can have your own Esri-provided high quality network dataset that you can use for unlimited analysis. ... View more