|
POST
|
No, the tool should run reasonably quickly no matter what field mappings you use. Unless you've purposefully pre-calculated location fields (and if you don't know what they are, my guess is you haven't), you should load using geometry.
... View more
11-06-2019
09:05 AM
|
0
|
11
|
2664
|
|
POST
|
That workflow seems okay. To answer your first question: When you drag and drop a network dataset into the map, it does not add the network source feature classes to the map. In ArcMap, it would ask you every time, which we thought was annoying. For Pro, we just disabled that behavior, so this is expected. As far as the workflow, everything you've done is correct, but for some reason the Add Locations tool is taking forever. Sometimes we see this if the network dataset's source feature classes or the the points you're locating don't have a spatial index. It takes a really long time to calculate the network locations if the features aren't indexed. For each source feature class of your network dataset, find it in the geodatabase in the Catalog pane, right-click and open the Properties, and go to the Indexes tab. Check what's under the "Spatial Index" part and calculate it or re-calculate it as necessary. If that's not the problem, then I don't really know what to tell you. You should probably call Esri Support so they can examine your data and workflow in detail.
... View more
11-06-2019
08:14 AM
|
0
|
13
|
4437
|
|
POST
|
Okay, that seems reasonable. Can you write down step-by-step what you did that got you to the problem? I'm sure there's just a simple mistake in your workflow. Once we figure that out, I'm sure it will work fine.
... View more
11-01-2019
12:38 PM
|
0
|
16
|
4437
|
|
POST
|
You haven't really given me enough information to understand your workflow, so it's hard for me to guess what the problem might be. Can you write out the specific steps that got you to this point? And what data are you using (how many stops, what network data source, etc.)?
... View more
10-31-2019
01:35 PM
|
0
|
18
|
4437
|
|
POST
|
I assume you're referring to ArcGIS Pro. In ArcGIS Pro, when you initially add stops to a Route analysis layer (either using Add Locations or with the manual Editing tools), the symbology will show a number 9. After you solve the Route layer, the stops will be assigned an order (which you can see in the Sequence field in the Stops attribute table), and the symbology will update to show the number in the Sequence field. To better understand the correct workflow for solving a route, please run this tutorial: Tutorial: Create routes—ArcGIS Pro | ArcGIS Desktop
... View more
10-31-2019
10:55 AM
|
1
|
20
|
4437
|
|
POST
|
Hello Martin. I'm glad these new tools have been useful to you so far. In order for the FromCumul_/ToCumul_ fields to be populated in your output table, I think you just need to set the Accumulate Attributes to accumulate the relevant cost attributes you care about. If you want to see the accumulated WalkTime, you have to check on WalkTime in the Accumulate Attributes. See the Accumulate Cost Attributes section in this documentation page: Service area analysis layer—ArcGIS Pro | ArcGIS Desktop Regarding your second question: You cannot limit the overall walking time/distance. You cannot make the solver force the traveler to stop walking after 5 minutes but allow them to continue riding for another 25 minutes. Our solvers currently do not have this capability. However, using an accumulate attribute as described above, you can at least see what the overall walking time is.
... View more
10-25-2019
08:55 AM
|
0
|
0
|
1603
|
|
POST
|
The Time properties of the Stops layer (your second screenshot) does not apply to network analysis at all. That information is not used by Network Analyst. A Route analysis layer can have only one start time for the route. You set that start time using the settings on the ribbon (your first screenshot). So, you can set the start time to be 8am, and then the Route will attempt to visit each of your stops during the requested time window. If it cannot do so, it will result in a time window violation. The amount of violation time, and the amount of wait time if the route is early, will be listed in the output Stops and Routes tables in the fields with "Wait" and "Violation" in their names. So, if you have set up a multi-route problem (you have multiple route names with different stops in each route name), you still can have only one start time for the overall Route. It will start each route at the first stop at that time. If the time window of the first stop doesn't match the route start time, you'll get either some wait time or some violation time at that first stop.
... View more
10-24-2019
08:43 AM
|
2
|
0
|
1947
|
|
POST
|
If you want to calculate the travel time along some existing street network (presumably to account for real road and traffic conditions), you could export the vertices of the existing bus line feature (try the Feature Vertices To Points tool) and use all the vertices as "Stops" in a Route analysis. You'd get way more stops that you really need, but it should ensure that the calculated route follows the desired path. If you include both the vertices and the real Stops as Route analysis "Stops" (sorry for the confusing terminology), you can still check the arrival times for the real Stops in the final output and use that for your timing, ignoring all the dummy "Stops" (the vertices). Not sure if I explained that well...
... View more
10-18-2019
04:31 PM
|
0
|
0
|
2035
|
|
POST
|
The Find Nearest tool can calculate straight-line distance OR distance along roads. You just need to tell it to use the Walking Time or Walking Distance travel mode. Here is the documentation for the Find Nearest tool: Find Nearest—ArcGIS Online Help | Documentation If you have over a million points, you might want to double check the credit usage before running your analysis. You can weigh that against building your own network dataset or purchasing Streetmap Premium to run the analysis locally.
... View more
10-18-2019
04:27 PM
|
0
|
0
|
1512
|
|
POST
|
These very small overlaps are unfortunately an artifact of the Service Area polygon generation algorithm. It doesn't always make a perfectly clean split between the adjacent polygons. If you see overlaps that are large, then we would consider it a bug, but ones this small are basically considered artifacts. If even these overlaps are too large for you, can you further explain your use case and workflow? I'd like to understand it better.
... View more
10-11-2019
10:23 AM
|
1
|
0
|
1262
|
|
IDEA
|
In ArcMap or ArcGIS Pro, you can use the search_query parameter in the Add Locations or Calculate Location tool to force the points to locate on an edge with a specific ID from some field. Add Locations—ArcGIS Pro | ArcGIS Desktop I don't think the REST API supports a search query, but if you're pre-calculating your location fields anyway, you could probably just do it this way.
... View more
10-10-2019
02:26 PM
|
0
|
0
|
1369
|
|
IDEA
|
In case it's relevant to you or anyone else all these years later, you can accomplish this using the Generate Near Table tool. Generate Near Table—Help | ArcGIS Desktop
... View more
10-09-2019
04:38 PM
|
0
|
1
|
1288
|
|
IDEA
|
In case anyone is looking at this post all these years later, here is a tool you can use in ArcGIS Pro to identify areas of your network dataset that are topologically disconnected from one another: https://www.arcgis.com/home/item.html?id=b2227f745a6c4e1c94dd57810729d2a9 It is not as comprehensive as the Idea posted here, and we hope to improve offerings in this area one day.
... View more
10-09-2019
04:13 PM
|
0
|
0
|
1039
|
|
IDEA
|
In case anyone is looking at this post all these years later, here is a tool you can use in ArcGIS Pro to identify areas of your network dataset that are topologically disconnected from one another: https://www.arcgis.com/home/item.html?id=b2227f745a6c4e1c94dd57810729d2a9 It is not as comprehensive as the Idea posted here, and we hope to improve offerings in this area one day.
... View more
10-09-2019
04:13 PM
|
0
|
0
|
931
|
|
POST
|
If your goal is the find the most-used road segments, Dan's suggestion to the the OD Cost Matrix solver will not work. OD Cost Matrix does not return the used road segments but rather only gives you the travel time or distance between the points. Instead, you need to use the Network Analyst Route solver. You need to set up your input Stops carefully so you can create one route between each start and end location. You can do this using the Route Name field. You need to map a unique identifier for each start-end location pair into the Route Name field. This will cause the Route solver to generate one route per unique Route Name, rather than putting all the points into the same route, which isn't what you want. Once you have solved the route, you can use the Copy Traversed Source Features tool to see which road segments were actually traversed, and then you'll probably have to do some further processing to figure out the number of times each segment was traversed.
... View more
09-12-2019
08:25 AM
|
1
|
0
|
1505
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-12-2026 01:53 PM | |
| 1 | 04-21-2026 08:39 AM | |
| 1 | 04-15-2026 02:24 PM | |
| 1 | 02-03-2026 11:41 AM | |
| 1 | 03-16-2026 08:58 AM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|