|
POST
|
Since you need to solve paths between pairs of addresses, you can use the Route Analysis layer to accomplish that. You can either load each pair and solve OR you can load all pairs but use the ROUTENAME property to match the pairs and then solve. You can read more on the routename at: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//004700000045000000.htm Basically when you load the start and end addresses in as stops, give them a common ID. That way the route solver will know which stop pairs with which stop. Load the residential addresses first and then load the work place addresses that way the paths are computed from residence to work. Regards, Jay Sandhu
... View more
10-13-2010
06:39 AM
|
0
|
0
|
382
|
|
POST
|
A high level discussion of the location-allocation algorithm is discussed here: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Algorithms_used_by_Network_Analyst/004700000053000000/ If you want to discuss this more then e-mail me at jsandhu at esri.com Regards, Jay Sandhu
... View more
10-08-2010
10:01 AM
|
0
|
0
|
423
|
|
POST
|
The route attribute table contains the overall route feature. The individual stop information is on the Stop attribute table. There will be column at the end with the cummulative distance to each stop. You can use it get the distance between each stop. Regards, Jay Sandhu
... View more
10-07-2010
06:58 AM
|
0
|
0
|
449
|
|
POST
|
a 500 mile service area is quite large and ends up traversing a lot of edges. The traversed edges are kept in memory. You could look at the following resource to not keep the traversal results around and see if that will solve your problem: http://resources.arcgis.com/content/kbase?fa=articleShow&d=30760 Jay Sandhu
... View more
10-06-2010
03:30 PM
|
0
|
0
|
480
|
|
POST
|
The VRP solver is set to use a time based attribute as it honors customer time windows. So you can not solve on some arbitrary attribute. However if you only have "one" vehicle, i.e. optimize one set of orders then use the Route Analysis layer and there you can choose your fuel based attribute and set the option on the Analysis Settings tab to "Reorder Stops to Find Optimal Route". Jay Sandhu
... View more
10-04-2010
07:31 AM
|
0
|
0
|
510
|
|
POST
|
The directions button can be grayed out after solving a route if the underlying network dataset does not have any street name information defined. So bring up the properties of your network dataset and click on the directions tab to see if any field has been defined for street names. If not, you will have to set that and then re-do you route layer, solve and then directions should be fine. Jay Sandhu
... View more
10-04-2010
07:27 AM
|
0
|
0
|
526
|
|
POST
|
Pawan, You are on the right track with the picture you attached. You need add more of the Add Locations tools to connect each of your orders, routes, etc to the Vehicle Routing Layer. You already do that for the Depots. Once all of them are attached, then call Solve on the last VRP layer. Also you may want to post such questions to the appropriate forum (e.g., the network analyst forum or the geoprocessing forum and not the data model forum for better response. Regards, Jay Sandhu
... View more
09-29-2010
03:30 PM
|
0
|
0
|
448
|
|
POST
|
So it sounds like you can solve the route but need to analyze the results more. One way can be to spatially select all the roads that overlap your route and then summarize them and the other can be to add the "traversal" results being stored in memory as a feature class to ArcMap and summarize them. The traversal results has every edge of the route with its network attributes. You can use the following link to see how to access the traversal result: http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#//000100000245000000 Jay Sandhu
... View more
09-28-2010
08:13 AM
|
0
|
0
|
613
|
|
POST
|
I am glad it worked. The acknowledgement format is fine or follow the guidelines of where you are submitting the article. If you need any further information you can write me directly jsandhu at esri.com Regards, Jay Sandhu
... View more
09-24-2010
07:42 AM
|
0
|
0
|
1956
|
|
POST
|
During load locations, you can map the name field to your store name., that is fine. You do not need to set any of the others. But in general, here you can load additional information. For example, if the service area around each facility should have a different break value, you can map that filed to the Breaks_LENGTHFT. If there is a "delay" associated with any facility, you can map that value as Attr_LENGTHFT (attr is short of attribute). For example, if you were generating a service area around fire stations in minutes and each fire station location had a different amount of time it takes to "leave" that location, i.e. a delay, you can map that value here. So a delay of 0.5 minutes with a 5 minute break will lead to a 4.5 minute service area from that location. You can choose to sort the data loading on a certain field such as loading them by city but again you can ignore that if it is not important. If your facility is physically not coincident with the edges of the network that is fine. During the load locations, it will find the closest edge to snap to. And loading by geometry is fine as that is the normal way to do so. If you plan to reuse the same locations many times with the same network then you can run the GP tool CalculateNetworkLocations to compute the SourceID, OID, etc fields and use them. So let me ask, are the facility locations that you are loading ALSO part of the network dataset? i.e. is it a network source. If yes, then that is probably the source of your problems. These facilities are not connected to the network but LoadLocations is going to "snap" to them as they are the closest source. So either remove them from the network and re-build OR, on the network locations tab, below the tolerance, there is a list of sources to which the locations can snap to. UN-check that point source and only leave the line or edge source active. Re-Load your locations and solve. If that is not the reason, then can you solve a path on your network? Can you solve a service area by adding a location using a mouse click? i.e. let's rule out network dataset problems. Regards, Jay Sandhu
... View more
09-23-2010
01:25 PM
|
0
|
0
|
1956
|
|
POST
|
First of all I do not think this problem has anything to do with snapping to network locations. If no locations were located then the solve would not have happened. So your facilities are snapping on to the network. If you are getting messages like "All network edges were excluded from line/polygon generation" then it is likely you could be located on a restricted edge or the network attribute values are wrong. That is, you are solving on some length attribute with breaks of 1/4, 1/2 and 1 mile. Are you sure your length attribute is in miles? Use the network identify tool (second icon from right on the NA toolbar) to click on the edge where you facility is snapping to and see what length attribute values are getting returned. It could be they are all 0 (not set to anything) or in meters or feet and thus 1/4. 1/2 and 1 are not returning anything useful. Regards, Jay Sandhu
... View more
09-23-2010
08:53 AM
|
0
|
0
|
1956
|
|
POST
|
Here are some places you can look for data: Streetmap Premium for Europe: http://www.esri.com/data/streetmap/europe-streetmap.html ESRI UK's web site for data links: http://www.esriuk.com/products/data/data_sourcing.asp Most likely, Tele Atlas and NAVTEQ are your best bets for finding local street data. Another possibility is the opensource street data: http://www.openstreetmap.org/ Regards, Jay Sandhu
... View more
09-21-2010
07:03 AM
|
0
|
0
|
761
|
|
POST
|
Knowing which city is connected to which city is the key. Without it you can not generate the information. As far as I am concerned, the shortest path between two cities gives you the summed up cost of the links making up the path between the cities. So you can simply use OD for that AND if you want one shape that combines all the shapes making the path, use the Closest Facility Solver. It is same as OD but also returns back the true shape of the path that connects two locations. Hint: You can run CF between all cities and export the resulting paths to a new Feature class and then make network dataset from it. BTW there is also a GP tool in Network Analyst toolset called DissolveNetwork that will remove all possible two valent junctions from a network dataset (by merging adjacent edges). Perhaps that can be used to simplyfy your network. More info here: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Dissolve_Network/00480000000w000000/ Regards, Jay Sandhu
... View more
09-16-2010
06:46 AM
|
0
|
0
|
426
|
|
POST
|
You can make another point source be part of your network dataset. So you could include the cities to be part of th network. Then change the code to only look at junctions of type cities. However, I am not sure how you will get length to the next city with the code I sent as the cities may not be linked to other cities with one to one edges. In fact, your post has again made it un-clear what you are trying to achieve. It looks like all you need is shortest distance between SOME set of cities. How do you determine what cities are connected to a given city? Jay Sandhu
... View more
09-15-2010
07:00 AM
|
0
|
0
|
1565
|
|
POST
|
Ok. What you want is the connectivity matrix of the network graph and the edge costs. You can generate that by using some VBA that I list below. To use this, add the network dataset to ArcMap. Make sure to change the name of the attribute name (in this case I have it as meters) to the one that is in your data. The run it in the VBA. The immedate window will show the results. You can re-format the debug.print lines (change them to write to a file) as needed. The output will currently look like this: Junction: 1 is adjacent to: 1 junctions. Adjacent Junction: 2 Length 235.7 Junction: 2 is adjacent to: 3 junctions. Adjacent Junction: 1 Length 235.7 Adjacent Junction: 4 Length 470 Adjacent Junction: 6287 Length 287.8 Regards, Jay Sandhu Public Sub List_Adjacent_Junctions() On Error GoTo eh Dim pMxDoc As IMxDocument Set pMxDoc = ThisDocument Dim pNLayer As INetworkLayer Set pNLayer = pMxDoc.FocusMap.Layer(0) Dim pND As INetworkDataset Set pND = pNLayer.NetworkDataset Dim pNQ As INetworkQuery Set pNQ = pND Dim pEnumNE As IEnumNetworkElement Set pEnumNE = pNQ.Elements(esriNETJunction) Dim pNEdge As INetworkEdge Set pNEdge = pNQ.CreateNetworkElement(esriNETEdge) Dim pNEFromJunc As INetworkJunction Set pNEFromJunc = pNQ.CreateNetworkElement(esriNETJunction) Dim pNEToJunc As INetworkJunction Set pNEToJunc = pNQ.CreateNetworkElement(esriNETJunction) Dim pNE As INetworkElement Set pNE = pEnumNE.Next Dim pNEJunc As INetworkJunction Set pNEJunc = pNE Dim i As Integer Do Until pNE Is Nothing Debug.Print "Junction: " & pNEJunc.EID & " is adjacent to: " & pNEJunc.EdgeCount & " junctions." For i = 0 To pNEJunc.EdgeCount - 1 'For each connected edge... pNEJunc.QueryEdge i, True, pNEdge 'Get that connected edge pNEdge.QueryJunctions pNEFromJunc, pNEToJunc 'Get To junction of current edge Debug.Print " Adjacent Junction: " & pNEToJunc.EID & " Length " & pNEdge.AttributeValueByName("Meters") 'List the adjacency Next Set pNE = pEnumNE.Next Loop Exit Sub eh: MsgBox "Error: " & Err.Description End Sub
... View more
09-14-2010
06:49 AM
|
0
|
0
|
1565
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-21-2023 09:39 AM | |
| 1 | 11-20-2024 09:29 AM | |
| 1 | 10-09-2024 09:23 AM | |
| 1 | 09-09-2024 08:54 AM | |
| 1 | 09-05-2024 10:42 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-31-2025
08:20 AM
|