|
POST
|
First, I encourage you to use arcpy.da.SearchCursor instead of the old arcpy.SearchCursor, which is deprecated and slow. SearchCursor—Help | Documentation With arcpy.da.SearchCursor, you specify explicitly which fields you want to retrieve from the data. for row in arcpy.da.SearchCursor(<your layer>, [python list of field names]):
print(row) The field name to retrieve depends on your network dataset and the output you care about. In the example script you're looking at, I guess the impedance attribute being used for the analysis was called "TravelTime", so the output field in the output routes sublayer was "Total_TravelTime". Basically you need to retrieve a field called "Total_[name of impedance attribute]". Let's say you solved using an impedance attribute called TravelTime. Then do this: for row in arcpy.da.SearchCursor(<your layer>, ["Total_TravelTime"]):
print(row[0]) Let's say you additionally accumulated a field called "Miles". Then you can also do this: for row in arcpy.da.SearchCursor(<your layer>, ["Total_TravelTime", "Total_Miles"]):
travel_time = row[0]
travel_distance = row[1] An explanation of all input and output fields for a Route analysis is here: Route analysis—Help | Documentation
... View more
04-06-2020
04:04 PM
|
0
|
1
|
3162
|
|
POST
|
Your screenshot looks like ArcMap, so I presume you are using the Add GTFS to a Network Dataset toolbox. If that is the case, then this topic in the Troubleshooting Guide answers your question: public-transit-tools/TroubleshootingGuide.md at master · Esri/public-transit-tools · GitHub Note that the Add GTFS to a Network Dataset toolbox is now deprecated since the functionality has been added to core ArcGIS Pro: Network analysis using public transit data—ArcGIS Pro | Documentation
... View more
03-31-2020
08:20 AM
|
1
|
1
|
1487
|
|
POST
|
You can modify your Service Area layer's travel mode even if you're using the ArcGIS Online services. On the Service Area ribbon, there's a little launcher button in the travel mode section. You can click that to open the layer's Travel Mode properties and configure which restrictions are being used.
... View more
03-26-2020
02:53 PM
|
1
|
0
|
2155
|
|
POST
|
What's considered "part of the network" entirely depends on which network you're using for your analysis? Are you using your own network dataset (something you created or your company/city created)? Or are you using Streetmap Premium that you purchased from Esri? Or are you using the ArcGIS Online services? In general, if you're missing rural roads and driveways, there are two possibilities: 1) Those rural roads and driveways aren't in the network at all and need to be added. 2) They are included in the network, but your travel mode settings prevent travel on them. If you don't want them to be restricted to travel, you just need to update your travel mode settings. Regarding ferries: If your network dataset includes ferry routes and the travel mode you're using for your analysis allows ferry travel, then yes, ferries will be used. Learn more about travel modes: Travel modes—ArcGIS Pro | Documentation
... View more
03-26-2020
02:33 PM
|
2
|
2
|
2155
|
|
POST
|
Are you using ArcMap or ArcGIS Pro? This is an important distinction because Pro uses a newer Service Area polygon generation algorithm. Pro's service areas will generally be cleaner and neater, and polygon barriers should be neatly clipped out from the results. You said: "I'm creating generalized precision service areas because the standard precision output excludes a lot of area that I would like to be included." Can you elaborate? It sounds like you have some area you want to be included and some area (like water bodies) that you want to be excluded. Sounds like a hard balance to strike when the only thing the Service Area algorithm knows about is which roads were reached.
... View more
03-26-2020
01:11 PM
|
0
|
4
|
2155
|
|
POST
|
In ArcGIS Pro (starting with 2.4), you can access a network dataset's build status from standalone python using the NetworkDataset class's isBuilt property. There's another property to get the network's build timestamp. NetworkDataset—Network Analyst module | Documentation
... View more
03-25-2020
11:05 AM
|
2
|
1
|
1995
|
|
POST
|
The ability to create a network dataset from scratch was added in ArcGIS Pro 2.5 with the Create Network Dataset tool. This tool creates a "blank" or "default" network dataset. You can then customize the properties of the network dataset using the network dataset property pages. The only thing you cannot yet do is create a new network dataset that includes live or historical traffic. If you need traffic, you still need to use ArcMap.
... View more
03-03-2020
09:56 AM
|
0
|
0
|
2023
|
|
POST
|
If you already had a network dataset, you could use the arcpy.nax.NetworkDataset class (requires ArcGIS Pro 2.4 or higher) to iterate over edges (the lines) and retrieve the lists of junctions attached to those edges. Then you could count which junctions show up more than three times. However, creating a network dataset can be somewhat arduous and is probably overkill for this problem. You would have to do a lot of filtering of the cursor results to make sure you were only getting the junctions that you created and not the automatically created system junctions that the network dataset creates.
... View more
02-28-2020
02:48 PM
|
0
|
0
|
1517
|
|
POST
|
As you can see from the error traceback, the BetterBusBuffers tool is failing when it runs the FeatureToPolygon tool. This is one of several internal steps that the BetterBusBuffers tool does. The tool calculates Service Area polygons around all the transit stops and then post-process those polygons using several other geoprocessing tools, including FeatureToPolygon. For some reason, this tool is not able to run successfully on the inputs it's getting from the Service Area polygons. My guess is that the geometry created by the Service Area polygons has something degenerate in it that is causing geometry errors later. I think the only option you really have is to change the BetterBusBuffers tool settings so that the Service Area polygon geometry is different, with the hopes that the degenerate polygons go away. Here are some ways to do impact the output polygon shapes: - Run the analysis in ArcGIS Pro (Pro uses a newer and better polygon generation algorithm) - Use a different network dataset - Use different network analysis settings (impedance attribute or restrictions) - Use a different buffer size - Use a different polygon trim If you have access to ArcGIS Pro, that would be the best thing to try first since you can maintain all of your other analysis settings. If not, adjusting the polygon trim is probably the simplest and will impact your analysis results the least. It might not resolve the issue, but it's worth a try.
... View more
02-26-2020
04:13 PM
|
0
|
0
|
843
|
|
POST
|
I am happy to help you, but I do not understand the question. (Hablo un poco de español si es mas facil.)
... View more
02-24-2020
08:25 AM
|
0
|
0
|
1133
|
|
POST
|
If you are using ArcMap and the Add GTFS to a Network Dataset toolbox, you should upgrade to ArcGIS Pro and use the tools included with ArcGIS Pro (no download anymore). Here is a tutorial: Create and use a network dataset with public transit data—ArcGIS Pro | Documentation ArcGIS Pro is more efficient and better for solving large problems. If the problem is still too slow, please include more details in your question so we can help you.
... View more
02-24-2020
08:23 AM
|
0
|
0
|
793
|
|
POST
|
Hi Robert. Here is the documentation for the Calculate Travel Time Statistics tool, in case you didn't find it: public-transit-tools/UsersGuide.md at master · Esri/public-transit-tools · GitHub You're right that the documentation doesn't give you the python parameter names, though. If you find the toolbox in the Catalog pane in ArcMap or Pro, you can right-click on the tool it and choose Properties. On the Parameters tab of the Properties window, you can see the list of the parameters. Instead of using the values in the Label column (that's what displays in the tool dialog), you can use the values in the Name column. Those are the python keywords. You can also run the tool once manually in the map, then right-click the result and copy the python snippet. You may need to change the input and output data paths to make it work, but the syntax should be pretty much as expected from arcpy.
... View more
01-20-2020
02:58 PM
|
0
|
0
|
2185
|
|
POST
|
Script evaluators are calculated at solve time. For this reason, they are a little slower, but they are also more flexible. I think the problem with your script evaluator is the syntax. I realize it's not completely straightforward how you are supposed to set these up. Essentially, I think you need to do something like this: Edge.AttributeValueByName( "AnalysisTier" ) instead of just "AnalysisTier".
... View more
01-16-2020
08:50 AM
|
0
|
0
|
1294
|
|
POST
|
If you want your exported polygons layer to have the same symbology, you can use the Apply Symbology From Layer tool.
... View more
01-13-2020
08:26 AM
|
0
|
0
|
2794
|
|
POST
|
In ArcMap, with Detailed polygons, I see the behavior you describe. With regular polygons, and in ArcGIS Pro for all types of polygons, I still see wrong behavior, but the ToBreak field always look correct (the problem is in the FromBreak field). So, another workaround for you would be to use ArcGIS Pro and base your logic on the ToBreak field, ignoring whatever it says in FromBreak. I think the polygons are correct; the break field values are just mislabeled.
... View more
01-06-2020
02:47 PM
|
1
|
1
|
2976
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Monday | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 06-12-2026 01:53 PM | |
| 1 | 04-21-2026 08:39 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|