POST
|
Can you do a service area lines from a location on the blue lines and does it get stopped at the junction where it connects to purple lines? If yes, then there is some issue in the connectivity there. Perhaps the blue line is not snapped to the purple lines. Or it could be a restriction or negative attribute value that prevents the path. It is hard to "debug" without looking at the data. If the data is small (or make a subset), perhaps you can package up the data with a couple of locations that do not route and send/post it. Jay Sandhu
... View more
06-02-2020
12:45 PM
|
0
|
5
|
152
|
POST
|
The screen shot in question shows the blue lines connecting to the purple lines at one location. Is the purple line split at that location if you are using End point connectivity? If it is not split, is there a vertex there for the blue lines to connect IF use Any Vertex connectivity? If you do not have it split AND you do not have a vertex on it for any vertex connectivity then you may want to run the GP tool Integrate to create those vertices. If you do use Integrate, make sure you use it on a copy of the data as it will modify the data. Integrate—Data Management toolbox | Documentation Jay Sandhu
... View more
06-02-2020
11:51 AM
|
0
|
7
|
152
|
POST
|
You can also do a service area (with the lines option, not polygons) from one of your stops and see if you can reach the second stop. It might show the connectivity problem area. Jay Sandhu
... View more
05-27-2020
09:27 AM
|
0
|
9
|
152
|
POST
|
When you create a network dataset, you specify the line/road features, attribute and restrictions, connectivity policy, etc. These settings are the schema of the network dataset. You can export the schema, and use it to create another one. For example, some one sends you an updated line/road feature class. So instead of going through the property pages and re-defining all the attributes/restrictions, you can use the schema to create a new network dataset on this updated road feature class. Everything about the input data and the fields that take part in the schema must be the same. If the data for the island and then the data for the rest of the country is in the same format then you can use the schema from the island to make a network dataset on the country. All the schema does is save you steps in re-creating a new network dataset. Do you already have the road data from all the country? It might be easier to use the Ready To Use services from ArcMap and do your drive time analysis on the street data we host via ArcGIS Online. In the Catalog view, you can expand the Ready To Use item and find the logistic services for Service Area. You will need an AGOL account and will have to use some credits to use these services. Info here: Consuming the logistics services using ArcMap—Help | Documentation GenerateServiceAreas—Help | Documentation Jay Sandhu
... View more
05-18-2020
08:54 AM
|
2
|
1
|
39
|
POST
|
Glad you have the travel modes figured out and using them! Jay Sandhu
... View more
05-15-2020
04:32 PM
|
5
|
0
|
108
|
POST
|
The status of the Pro network dataset says Not Built. So Build the network and the service area will work. Also note that in general, the same network dataset for ArcMap can be used in Pro. You do not need to have two different geodatabases unless you have some other reasons to do so. Jay Sandhu
... View more
05-12-2020
09:24 AM
|
5
|
1
|
41
|
POST
|
If you have a good connected street network, then you can construct a network dataset on it. With this network dataset, use the GP tool Make Route analysis layer with the Find Best Order option to create route analysis layer. You need to load this layer with stops or locations to visit. You can use the GP tool Feature To Point with the inside option to create one point per input street feature. Now you can load these resulting points as stops into the Route analysis layer. Make sure to set the curb approach to No U-Turn. And solve the route layer. It should give a reasonable result for what you are looking for. If you have not use network analyst before, I suggest you run through some of the beginning tutorials. Create a network dataset—ArcGIS Pro | Documentation Tutorial: Create routes—ArcGIS Pro | Documentation Jay Sandhu
... View more
05-11-2020
08:26 AM
|
1
|
0
|
31
|
POST
|
Jamal, I tried your data and I do not see the results you are seeing. In Pro, I get the same results as in ArcMap. You could try creating a new project, re-add the data and re-create the Location-Allocation layer and solve. If you still see the different results, then click on the Share tab, and choose the left most option "Project" and then follow the instructions to package the whole project and share it back here and I can take a look at it again. Jay Sandhu
... View more
05-10-2020
10:18 AM
|
5
|
1
|
5
|
POST
|
All network analyst solvers like the Route solver minimize the impedance attribute. It can be set to a time based impedance or a distance based impedance. However the Vehicle Routing Problem Solver is designed to work with a time based impedance and also uses a length attribute for certain constraints and settings. The travel mode sets up which of the impedance attributes should be used. And if your network dataset has more than one impedance attribute and some are time and some are distance, it sets up which one to use for time and which one to use for distance if needed beyond the impedance attribute. For example, see the travel modes for the tutorial Paris network dataset which has driving and pedestrian travel modes. In your screen shot, the impedance is set to Time Cost. This is what is used to solve the route. Below the impedance attribute, the property page shows what was set up as the time based attribute, in this case Travel Cost and it is grayed out meaning that is what has been set for impedance for this travel mode. Below that is the distance based attribute, Length in this case. The distance based attribute is not being used by the Route solver. Only the VRP solver could use it if certain constraints were set up. So, in summary, the Impedance attribute is used to solve the network analysis. Jay Sandhu
... View more
05-10-2020
09:00 AM
|
5
|
2
|
108
|
POST
|
I will suggest that rather than trying to make a m by n network, use a grid. A M by N network can become very densely connected if M and N start becoming large. For example a 50 by 100 means there will be a 100 lines originating from each of the 50 locations. The path finding code which is used to compute the OD Cost Matrix on this resulting network will start to run slower. So I suggest that you use the GP tool Fishnet to create an appropriately dense or sparse grid that encompasses your point locations and build a network and solve VRP on it. This will more resemble a street network! f you still need a M by N directly connected network, I suggest that once you have this grid network, simply use the OD Cost Matrix tool on your M by N points and it will create the straight lines between all your points as part of the output. Jay Sandhu
... View more
05-08-2020
12:33 PM
|
0
|
0
|
32
|
Online Status |
Offline
|
Date Last Visited |
Tuesday
|