POST
|
Thanks Robert! That is very helpful. I'm attaching the requested screenshots. The naming part makes sense now - I found the name field it's using. One file didn't originally have a 'Name' field, so I think that's when I saw 'Location #'. I've pretty much been using the default settings. The only thing I've been adding to the Route Properties are the Time and Length Accumulation Attributes under the Accumulation tab. I thought about the fact that the Network Dataset is so large and wondered if it would help if I create a new network dataset from the TIGER All Lines files only for the 5 counties where the points lie. Would that help with the memory issue? Thank you so much for all of your help! Jenna
... View more
03-13-2013
05:46 AM
|
0
|
0
|
421
|
POST
|
Hi again Robert, It worked once this morning when I tried it with only 10 pairs. After that, I tried 758 pairs and it failed. Then I tried 50, 25, 10 and even 9 - all failed. I don't know what happened between the one time it worked and the subsequent times - I used the same settings. 1. I set the options to 'All Messages' and I still don't receive any error messages other than 'solve failed' 2. It does work if I interactively add 2 points, group them by name and solve, but I have 758 pairs and not much time to complete it that way. One thing I've noticed is that sometimes when I load the locations the names for the stops are either 'Location' with a number (starting at 1) or they are just numbers - sometimes 4 digit, other times 5 with a decimal in it. When that happens, the pairs will have the same number, but the map appears to place everything correctly and their symbol shows them as 'located'. Is it a problem when the load and locate that way? Thanks! Jenna
... View more
03-12-2013
11:26 AM
|
0
|
0
|
421
|
POST
|
Thanks Robert! I was using the default search tolerance and those that had addresses were located. I actually ended up getting rid of the pairs that didn't have both an origin and a destination. A lot of them did not have a location for the destination and those were the ones that were unlocated - I just thought those routes would be 0 or unsolved, but that the other pairs would solve. So now all of the stops are located and when I solve I don't get any of the previous 'unlocated' errors, but it still fails. I don't get any error message now, I just see 'solve failed' in the network analyst sidebar at the bottom. I had 758 pairs of locations and thought that maybe there were too many, so I tried with 10 pairs of locations and it still doesn't work, no message other than 'solve failed'. I'm using files that were geocoded using the 10.0 North American Geocode Service (ArcGIS Online) and using the StreetMap Pro 2007 streets network - I'm not sure if that answers your last question. Any other thoughts Robert? Thank you! Jenna
... View more
03-11-2013
07:01 PM
|
0
|
0
|
421
|
POST
|
If I understand your objective correctly, you want to find the driving distance from one specific origin to one specific destination, not from all origins to all destinations. This is important because, at first glance, you might think the OD cost matrix solver would work best, but actually it's probably best to do the following using a route layer instead: 1. On your dataset, create a new field named RouteName and calculate its value so that it is the same value as your current ID field. 2. Add your origins to ArcMap as a layer. (Tip: File > Add Data > Add XY Data.) Only specify the origin X and Y fields. 3. Rename the output layer that appears in the table of contents to something like Origins. 4. Add your destinations to ArcMap as a layer. Only specify the destination X and Y fields. 5. Rename the output layer to Destinations. 6. Make a Route layer using the Network Analyst toolbar (or a GP tool). 7. Load the Origins layer into the Stops class. (Tip: Right-click Stops in the Network Analyst window and choose Load Locations.) Make sure the RouteName field is mapped to the RouteName field you created. 8. Load the Destinations layer into the Stops class using the same method. 9. Solve By specifying the route name when loading, the stops are grouped together and routes are calculated only for the stops that are in the same group, which in your case is limited to a single origin and destination pair. You can open, and optionally export, the Routes class, which contains the calculated shortest-path driving distances. The Name field values will match the values of your original IDs. I'm having problems with this. I'm able to load the origins and destinations into the Stops and assign the Route Name for each. My stops then show up paired by the Route Name values, which seems correct - I want to know the driving distances for paths between specific pairs of points. When I solve, the solve fails and give the errors "Warning: Location "Location 1" in "Stops" is unlocated." for a lot of locations. These are locations of where women live and the mammography screening facility they attended. I don't have the facility for some women, so I figured those would be unsolved, but it doesn't solve any routes for those that have both locations. When I loaded origins and destinations into OD Cost Matrix, it solved everything, but was obviously more than I wanted since it did all routes, not the specific route per woman. Any suggestions are appreciated!
... View more
03-11-2013
11:28 AM
|
0
|
0
|
815
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|