Latest Contributions by JaySandhu

The service area solver (drive time polygons) start from a point location. If you want to do it for a line, then turn it into a series of points, especially  at the junctions of those lines with other lines. Then load all the points as facilities and choose the merge the output polygon option so that a combined polygon is returned. Jay Sandhu ... View more

Most likely you are using the "High or Detailed Polygon" option when you are generating the service areas. This option will find all the unreachable areas and give you those small holes. If you do not need this level of detail, use the Standard option. Jay Sandhu ... View more

Are you using the online service to solve the service areas? If yes, you can specify a start time/day of week and get drive times based on historical travel times. Or you can use current time/date and use real time traffic values. Jay Sandhu ... View more

Location-Allocation Minimize Weighted Impedance uses the demand weight. Basically we minimize weighted demand. That is, multiply the length or cost of the shortest path by the demand weight. That way, the locations with more demand have a higher pull on the facility location. Jay Sandhu ... View more

What software/version are you using? What are the exact error messages that you get? Are your new streets split at intersections? Do they connect to existing edges which are also split or have a vertex there? Are you using AnyVertex or EndPoint connectivity? All these settings help build/connect a network. When you build a network dataset, a temporary log file called build.txt file is created in the %TEMP% folder, in a sub folder for the ArcGIS process. It may have more information on the issue you are running into. Jay Sandhu ... View more

Looks like you are getting a larger service area polygon. It is likely that the costs or distance attribute on the network dataset is not behaving correctly. Can you make a new service area on that network dataset with one facility set to 3900 feet and does it solve correctly? Jay Sandhu ... View more

Glad to know you figured it worked. Pro can solve network analyst layers either on AGOL or your portal OR use local ND. Existing layers cannot be changed to work on a different source. But new layers can be configured to work on any available source. Jay Sandhu ... View more

How are you running your service area analysis? Are you using Pro and calling the online service which has the limits? OR are you adding the Streetmap Network dataset to Pro and then creating a service area layer based on that local network dataset and seeing issues? Jay Sandhu ... View more

Every street in your street network dataset has a length, say 100 meters between two intersections, and a travel speed say 50 kilometers per hour. From this information the time to travel those 100 meters can be computed as 0.12 minutes and stored in the network dataset. As Melinda mentioned, you can look at the cost attribute settings for your network dataset to find the exact settings. Jay Sandhu ... View more

In your use case (screen shot) the chosen sites are the correct solution. You could choose candidates that further away from each other, or at least the distance you care about. That way the chosen sites will not be near by. You can use the Create Random Points tool and specify the Minimum Allowed Distance that works for you to create candidates with the minimum spacing. Jay Sandhu ... View more

As you noted, Location-Allocation does not provide a model that takes both capacity and attractiveness into account. Usually attractiveness is in used in retail industry where the retail establishment usually do not have a capacity of customers they want to deal with. Can you describe your use case? How should these two properties impact the location decision? Jay Sandhu ... View more

You can use many techniques to generate "potential" candidates. One way I create these is to place a point on every street that is in your study area and then select from them, either randomly or using other spatial analysis techniques. Assuming you have a street feature class in your study area, use the GP tool Feature To Point with the INSIDE option to create one point per street. Feature To Point (Data Management)—ArcGIS Pro | Documentation  This create a lot of points. You can select, say 100 points, randomly using the Create Random Feature using the point feature layer as the constraining layer. Create Random Points (Data Management)—ArcGIS Pro | Documentation  Or you can can buffer (or drive time polygons) your hubs to create zones where you do/don't want to place your locations and select from the street points. Of course you can get census tract population data and further weight these points. So, there are lots of ways to make value added data by doing standard GIS operations like overlay. Jay Sandhu ... View more

Glad you can proceed with it! You could add a new text field to the Routes attribute table and set it some combination of the FacilityID and IncidentID that remains unique and then you will have a single field to join the two route attribute tables and sum up the travel times. Jay Sandhu  ... View more

As I mentioned earlier, if you are solving CF for ALL closest facilities and there are no cutoffs, you will get the same set of routes back unless some are not possible. If you have 3 incidents and 4 facilities and solve for 4, you will get 12 routes back. And when you switch the travel direction you will still get 12 back. The FacilityRank ordering may be different. So do you have some limits on the CF that you are solving?  Jay Sandhu ... View more