|
POST
|
Check out Code Sample #4 in the Make Route Layer tool reference in the doc. Make Route Layer—ArcGIS Pro | ArcGIS for Desktop # Get the output Routes sublayer and save it to a feature class
RoutesSubLayer = arcpy.mapping.ListLayers(outNALayer, routesLayerName)[0]
arcpy.management.CopyFeatures(RoutesSubLayer, outRoutesFC)
... View more
01-06-2016
09:59 AM
|
1
|
0
|
2493
|
|
POST
|
Hi Dan. The TargetDestinationCount property refers to the NUMBER of destinations to find for each origin, not the specific destination IDs. With OD, you can control how many destinations to find, but you can't specify which ones.
... View more
12-03-2015
01:35 PM
|
0
|
1
|
2781
|
|
POST
|
If you want to specify pairs of origins and destinations and actually control which origin links to which destination, you can use the Route solver. When you load Stops, map the Pair_ID field to the RouteName field. This will ensure that a separate route is created for each pair.
... View more
12-03-2015
11:28 AM
|
1
|
4
|
2781
|
|
POST
|
The custom evaluator probably needs to be registered on the machine hosting the SDE data. That's my best guess.
... View more
11-23-2015
09:22 AM
|
0
|
0
|
925
|
|
POST
|
Are you a developer interested in public transit analysis? We have some tools for public transit analysis in ArcGIS, and we've recently made them available on GitHub. Feel free to play with them and contribute! Esri/public-transit-tools · GitHub
... View more
11-03-2015
01:22 PM
|
0
|
0
|
2313
|
|
POST
|
You do not need to tag me in these posts. I receive automatic e-mail notification of all Network Analyst-related questions anyway.
... View more
10-26-2015
08:22 AM
|
0
|
1
|
2217
|
|
POST
|
Hello, Jan. Google Translate didn't do a great job, so I don't completely understand your question. However, it looks like maybe you need to switch the travel direction setting from Facility to Incident to Incident to Facility. Just a guess. If the only thing you care about is distance, you should not need any restrictions or barriers or anything else. You just need an accurate distance-based cost attribute. Additionally, your network dataset needs to be well connected (a frequent problem). Some resources: Network Analyst tutorials: About the ArcGIS Network Analyst extension tutorial—Help | ArcGIS for Desktop Understanding Connectivity: Understanding connectivity—Help | ArcGIS for Desktop
... View more
10-26-2015
08:21 AM
|
1
|
0
|
2217
|
|
POST
|
Sadly, no, we don't have an Esri product that does this. We might have a partner company that provides such a solution. I suppose it depends on what your goal is. Are you just trying to calculate this for yourself or some analysis project, or are you trying to build an app using Esri technology?
... View more
10-21-2015
10:41 AM
|
0
|
0
|
1557
|
|
POST
|
Hi Chris. Unfortunately, the Network Analyst Route solver simply isn't designed to solve this problem. The Route solver uses algorithms that are meant to optimize travel through the network: to find the fastest or shortest route from one place to another. Finding the best "scenic route" for running or cycling is a very different problem, and NA Route isn't really the right tool for that job.
... View more
10-21-2015
08:34 AM
|
1
|
2
|
1557
|
|
POST
|
This sounds suspiciously like a bug. The best thing for you to do would be to contact Esri Support. They can either help you with the issue or diagnose the bug and send it off to the right team for fixing.
... View more
10-19-2015
08:59 AM
|
1
|
1
|
2466
|
|
POST
|
Hello, Annie. Sorry to answer you in English, but I don't speak French. Google Translate worked well enough for me to understand your question, so hopefully it will work well enough for you to understand my answer. I am familiar with the problem you describe: the GTFS stops snap to a side street, so when you use the Network Analyst Route solver, the bus detours into side streets and makes u-turns. I have struggled with this problem in a tool I have created that is meant to generate a GTFS shapes.txt file by estimating the routes traveled by using the Route solver. It sounds like a very similar application to what you are trying to do. Unfortunately, I have not found a good way to solve this problem. The GTFS data contains only the latitude and longitude of the stops and does not contain any information indicating which street the stop should snap to or which street the buses use. You might be able to extract this information from the stop_name field in stops.txt if the stop names are consistent and are identical to the names used in the street features of your network dataset. You could then use a search query when you run the Add Locations tool, to match each stop with the correct street. However, I think it will be difficult to do this accurately because the stop names and the street names probably are not identical or consistent. Does your GTFS data already have a shapes.txt file? If so, you can use that to create a feature class in the map which might be a closer estimate than creating routes between the stops. You can use this tool to add shapes.txt to the map. Good luck!
... View more
10-14-2015
09:59 AM
|
2
|
0
|
1458
|
|
POST
|
Hello, Tas. I don't think that Hierarchy is really the right tool for the job you are trying to do. Hierarchy is meant to help very quickly solve long-distance routes on large networks, routes that would take a really long time to solve with an exact solution. The hope is that the route computed using Hierarchy is the same or very similar to the exact route computed with Hierarchy turned off, just much faster to compute. Thus, it is not surprising that you got the same solution when you toggled your Hierarchy value. Hierarchy is meant to decrease computation time, not to control which roads get used in your analysis. I think you might get closer to what you want by using restriction attributes based on road class (street, off-road cycle paths, and on-road cycle paths). You can create "soft restrictions" that have a value of "Preferred -[high/medium/low]" which serves to make the route prefer to use those road segments over others. So you could construct your restriction attribute so that off-street cycle paths are preferred a lot, and on-street cycle paths are preferred a little less (or whatever you think is appropriate) and regular streets are just normal. Solve the analysis with the restriction turned off for a normal analysis and then turned on to mimic people's preferred behavior. Here is some information about Restriction attributes: Understanding network attributes—Help | ArcGIS for Desktop Finally, instead of computing the route and then intersecting it with the underlying street features (which may be imperfect in the results returned), instead, use the Copy Traversed Source Features tool (Copy Traversed Source Features—ArcGIS Pro | ArcGIS for Desktop ). This returns a feature class of the network edges that were used in the solved route, which is exactly what you're looking for.
... View more
10-09-2015
09:13 AM
|
1
|
2
|
1809
|
|
POST
|
Okay, your field is called "Oneway", but what is the network's oneway restriction attribute called?
... View more
09-30-2015
10:41 AM
|
0
|
0
|
2347
|
|
POST
|
Hmmm... Does your network have a Oneway attribute, and what is it called? Is it called "Oneway", or does it have some other name?
... View more
09-30-2015
09:56 AM
|
0
|
2
|
2347
|
|
POST
|
It looks like the direction of digitization for that street has changed, but that does not mean that your Oneway attribute is now incorrect. The DissolveNetwork tool knows how to handle Oneway attributes and should update the feature's fields correctly even if it flips the direction of digitization. You can use the Network Identify tool (on the Network Analyst toolbar) to click on that street and get some information about your Oneway attribute to confirm that it is still one way in the correct direction after Dissolve.
... View more
09-30-2015
09:34 AM
|
0
|
4
|
2347
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 1 | 4 weeks ago | |
| 1 | 4 weeks ago | |
| 1 | 06-12-2026 01:53 PM | |
| 1 | 04-21-2026 08:39 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|