Latest Contributions by JaySandhu

Generally I recommend to generate mid points on every edge NOT intersections. And also set a curb approach right property and you can set u-turns at dead ends only.  That way streets are travelled to the end. That said, covering every street efficiently requires a different approach then using the TSP solver that ArcGIS provides but you may get good results.  Also are you using local street network data or online service? There are limits on the stops you can pass to the online service not for local data, but there are practical limits on how much you can optimize in one solve. BTW, what is your use case for travelling every road in the city? Jay Sandhu  ... View more

This looks like an issue with the network. The Location-Allocation process starts by computing shortest path costs between all the facilities and demand within the cutoff.  Can you create a route layer and add two locations and find a path using the length or time cost attribute? What is the cost of that path? Is it reasonable according to your network. Are you using a cutoff in the Location-Allocation? Also, did you Build your network dataset after you created and made changes to it? Jay Sandhu ... View more

The OD Cost Matrix does not return the shape of the path travelled. This is because it can take longer to compute for very large values of Origins and Destinations. The OD solver is designed for the case when you only need the shortest travel distance/cost and not the route geometry. Straight lines are returned between each origin/destination pair for convenience to identify the pair. If you also want to get the actual route geometry then use the Closest Facility Solver. Load your origins as Incidents and your Destinations as Facilities. Set the CF solver to solve for the number of Destinations/Facilities that you have. When you solve this CF layer you will also get the paths travelled. Jay Sandhu ... View more

Use the OD Cost Matrix Analysis. You can load your Origins and Destinations and it will solve all N by M routes and return the travel distance/cost. You can look at the tutorial here: Calculate the travel time between origins and destinations with OD Cost Matrix—ArcGIS Pro | Documentation Jay Sandhu ... View more

When you load the point locations into a route layer as Stops, the x,y location of these is the same as the input. They edge they snap to can be based on the location rules such as bearing/bearing tol and restricted road elements, etc. You cannot "see" where they located on the map. However if you open the Stops attribute table and look at the SourceOID and Position, that will tell you the edge and position along the digitized edge (percentage between 0 and 1) that point located. When you solve the route it will visit the stops where they were located. Jay                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        ... View more

Looks like the attached graphic did not get added. Jay Sandhu ... View more

The import stops tool is fine. Internally it is calling Add Locations. So the bearing/bearingtol fields are being used when you import.  If, before importing, you add the same fields to the Stops sub layer then you will see the values copied over as well after import. When you import, the X, Y location of the stops will be at the same location of where the input points are. But the edge they snap too will be different IF the bearing/bearingtol values have an impact. Jay Sandhu ... View more

If you have already loaded the Stops and then are adding the Bearing/BearingTol fields and adding values, they will not be used. The values should be present when Add Locations is called so that when the location is happening the fields are getting used. You can add these fields to the Stops Analysis layer using the GP tool Add Field to Analysis Layers Add Field To Analysis Layer (Network Analyst)—ArcGIS Pro | Documentation If these fields are present then when Add Locations is called, the values of the Bearing and BearingTol are also copied over to the Stops field. Now if something happens to cause a network re-build, the locations are computed again at solve time and these fields will continued to be used. Jay Sandhu ... View more

Bearing and BearingTol field values are used when the points are initially used by Add Locations to load them as Stops. The value units for both are in degrees. What values are you putting into them? And what happens when you load these points? Do you get any warning message about feature not being located? Jay Sandhu ... View more

You can also download the Network Analyst tutorial data and look at the way the SanFran and SanDiego network datasets have been put together. Network Analyst ArcGIS Pro Tutorial Data - Overview Jay Sandhu   ... View more

The red question mark means the locations are not located on a network edge. If you expand the Facilities layer symbology in the Table of Contents, you will see this information shown. There can be many reasons for the facilities and demand to be not located, primarily issue with the network dataset being used. Is it built? Or was it re-built after the location-allocation layer was created? Can you try running a simple two point route? You can in the Network Analyst window, right-click on the Facilities and choose Recalculate Location Fields to see if that will fix the issue. Same for the demand points. Jay Sandhu ... View more