Latest Contributions by JaySandhu

‎02-08-2022

A solve for Tuesday 7:30 PM time uses the historical travel times when creating the service area. Cerritos to Long Beach is about 15 miles, so a 20 minute drive seems reasonable to get there. Also note that the historical travel times are averages for all Tuesdays in the last few years and the last two has had lighter traffic due to the pandemic. BTW, in your estimate, how long should it take to drive from Cerritos to Long Beach? Jay Sandhu

‎01-28-2022

In the ArcGIS Pro, catalog pane, you should be able to right-click on the feature dataset and choose to create a network data set. If the Network Dataset already exists, then you should be able to right-click on the ND and choose to Build Network. What steps are you doing so that you are not able to see your feature dataset? Jay Sandhu

‎01-28-2022

Just to give you some idea of tools that could be of use, look at Location-Allocation solver in Network Analyst. It can find a place that minimizes overall travel times to multiple locations. For example if you are trying to build a warehouse to service some warehouses. Jay Sandhu

‎01-26-2022

I think you need to describe what your goal is for this analysis as finding a point that is equal distant to 40 other points may not be possible. Just try to visualize where this point would be located and you will realize that there is no solution. Jay Sandhu

‎01-20-2022

You can use the Location-Allocation solver. Make the park entrances as facilities and the friend locations as demand. Solve for 1. It will find the location of the park that minimizes overall travel time from all the friend's. However the solution may not be equitable to everyone as some may have to travel more than others. You can put in a travel time cutoff and try to find another solution. This solver has many options, so you can see what gives you a good solution. More info here: Location-allocation analysis layer—ArcGIS Pro | Documentation Jay Sandhu

‎01-14-2022

Glad that worked! Jay Sandhu

‎01-14-2022

If you are using ArcMap, then on the NA toolbar, there is connectivity checker tool (second from right) that you can use to explore the connectivity. If switching to any vertex did not work then that means the line going up does not have a common vertex where the lines going to the right should connect. You will need to use the Integrate tool to create the required vertices and then rebuild again. Jay Sandhu

‎01-14-2022

Generally speaking, if you use OSM data, you should set Any Vertex connectivity and build the network. You do not Integrate as that WILL create end points/vertices where streets cross. Also you do not need to remove the motor ways and links. Just have a restriction that turns them off in the network dataset for pedestrian routing. Jay Sandhu

‎01-14-2022

It is likely they are not connected to the other lines! You can change the service area to generate polygons and lines and re-run the analysis to see if those lines are part of the output. But a better way is to check the connectivity. Click on the network dataset in the TOC to make it active and then use the network dataset tab to pick the Explore Network tool and click on the lines to see what they are connected to AND what travel attributes they have. That might give you a clue to where the problem exists. The connectivity issues may have happened due to End Point connectivity policy when the streets are not all split at all the connecting ends. You may be able to switch the Any Vertex connectivity and rebuild the network. Again that will only work if the lines that are not split have a vertex where the other lines connect. Jay Sandhu

‎01-13-2022

The important thing to model is the connections, turning restrictions and having accurate travel times. You do not need to digitize the curves as long as the road centerlines capture the connections accurately. You can add in turn restrictions at places where turns are not allowed. Jay Sandhu

‎12-17-2021

Well assuming that the change from 50 to 25 will make it twice as slow, AND entire line features are affected, you can set the scale cost factor to be 2.0 You can select the affected line features and then load them as barriers. If the slow down happens to start and/or end in the middle of a road then you will have to create an appropriate line feature. The slow down should still be 2.0 If this is a permanent change then you should consider updating the values in the network dataset and rebuilding it. Jay Sandhu

‎12-16-2021

The concept of barriers in a network analysis layers is designed for this scenario. You can have point, line or polygon barriers. The barriers can be a restriction or a scaled cost. So you can have a polygon of an area where a weather event is slowing down traffic by 20%. You can load that into your route analysis layer with the a scale cost of 1.2 More info: Barriers—ArcGIS Pro | Documentation Jay Sandhu

‎12-16-2021

The arcpy.nax api uses different field names that when using a layer so “Cutoff_Minutes” is not automatically used. In your scenario you can rename the input field or use a field map. Using the field map will look like: # Map fields fieldMap_demandPoints = loc_alloc.fieldMappings(arcpy.nax.LocationAllocationInputDataType.DemandPoints) fieldMap_demandPoints["Cutoff"].mappedFieldName = "Cutoff_Minutes" # Set the default value to use if the field value is null (optional) fieldMap_demandPoints["Cutoff"].defaultValue = 15 # Load inputs loc_alloc.load(arcpy.nax.LocationAllocationInputDataType.DemandPoints, input_demand_points, fieldMap_demandPoints) You can always get the field names list if you don’t know what to map or which names will be used automatically: print(loc_alloc.fieldNames(arcpy.nax.LocationAllocationInputDataType.DemandPoints))

‎12-16-2021

Do you get this message if you do not leave the default value null? Even if there is a default value present, the field values on the demand points take precedence. So it should be ok to set a default value if that works. Jay Sandhu

‎10-20-2021

The Location-Allocation solver does not use a GPU or parallel computing. It first needs to compute the travel distances (over the network) for every candidate to every demand point within the cutoff. And then the capacitated solver needs to make sure that the capacity is not exceeded. That requires more work then the default Minimize Weighted Impedance problem type. Location-Allocation uses heuristics to solve the various problem instances and hard to say the complexity in terms of O notation. I would suggest solving with the default Minimize Weighted Impedance with 750 cutoff and seeing how long it takes for the problem to finish, and also if the resulting allocation already honors the 1200 demand. If it does not, see the max distance travelled. Maybe it will give you a better cutoff to use that will help reduce the problem space and help speed up the Maximize Capacity case. Jay Sandhu

Online Status	Offline
Date Last Visited	‎05-29-2026 01:54 PM

My Ideas

Latest Contributions by JaySandhu

Re: AGOL Analysis Drive Time Areas for California? How accurate are they?

Re: Building a Network Dataset Error 030178

Re: Finding a central drive-time point for a layer of point features

Re: Finding a central drive-time point for a layer of point features

Re: Closest Park Analysis

Re: Service Area Analysis

Re: Service Area Analysis

Re: Network analysis using OSM roads data

Re: Service Area Analysis

Re: Building a Network Dataset for fire response times at an airport

Re: Network Analyst temporary speed changes

Re: Network Analyst temporary speed changes

Re: Location-Allocation failed because 'cutoff must be present for every entry in "Demand Points"'

Re: Location-Allocation failed because 'cutoff must be present for every entry in "Demand Points"'

Re: Location Allocation, type Maximize Capacitated Coverage is running slow, how to speed up?

Re: Creating a maximum walkshed around each point

Re: Closest Facility - Remove Facilities and Incid...

Re: Polygons for Best Dump Site By Site Cost and T...

Re: Delay in routes

Re: Delay in routes