|
POST
|
I wanted to follow up on the Build Network error. We were able to install a fix for this problem, and it will be available in the upcoming Pro 3.2 release. I'm still not sure whether some part of your editing workflow caused the network to end up in a bad state, but our changes will allow the network to build successfully.
... View more
09-22-2023
10:24 AM
|
0
|
0
|
5998
|
|
POST
|
Thank for the data you sent via a private message. I am able to reproduce the error with Build Network, and I logged an issue for my team to investigate it. Unfortunately, I don't have a short-term workaround for the problem. I have also asked some people who work with topology rules to take a look at it, since it seems likely that this is the real problem. They may follow up with you for more details or data.
... View more
09-11-2023
01:46 PM
|
0
|
1
|
6036
|
|
POST
|
FYI, I have responded. Esri Community's private mail function does not seem to alert you by e-mail. Very annoying.
... View more
09-07-2023
10:04 AM
|
0
|
0
|
6067
|
|
POST
|
To make sure I understand: You are not running the Build Network tool, correct? You're running the Append geoprocessing tool to append records from an egdb feature class to an fgdb feature class. Are these feature classes part of a network dataset? (The data you shared does not involve a network dataset.) If your workflow has nothing to do with Network Analyst or topology, then it's unlikely to be related to the problem the original creator of this thread reported. It's not related to Network Analyst, so this isn't really the right area within Esri Community to get help for that. It's outside my area of expertise, so I can't really help you. Sorry! I recommend posting your question to the general ArcGIS Pro page at https://community.esri.com/t5/arcgis-pro-questions/bd-p/arcgis-pro-questions. Or, call Support. That may be a faster way to get help.
... View more
09-07-2023
08:51 AM
|
0
|
1
|
1735
|
|
POST
|
Okay, if that's the case, please describe your workflow in more detail. It sounds like it's different from what the original user described. Please also share your data, if you're able. That would be very helpful in diagnosing and fixing the issue.
... View more
09-06-2023
02:19 PM
|
0
|
3
|
1807
|
|
POST
|
I have asked some members of another team (the ones who own the topology editing tools) to review this thread. I don't have any answers for you yet.
... View more
09-06-2023
01:31 PM
|
0
|
5
|
6097
|
|
POST
|
We don't currently have any plans to allow full configuration of network dataset properties via Python. Can you describe your workflow or end goal in more detail so I can better understand what you want to do? Typically users create their network dataset once (manually) and then just use it in an automated script without the need to edit it. Or, if you need to create multiple networks with the same schema, you can configure one once (manually) and run the Create Template From Network Dataset tool and then have your automated process use the Create Network Dataset From Template tool.
... View more
09-06-2023
01:27 PM
|
0
|
0
|
1603
|
|
POST
|
What network dataset are you using? Is it one you created yourself? Usually when I see routes like this, it's a symptom of a network dataset connectivity problem or a problem with the way the cost attributes are configured. The Route solver will always return the "shortest" path, but if the cost attributes are returning incorrect values, the shortest path calculation will also be incorrect. Or, if there is no connection between roads at intersections, the shortest path may be to travel very far until it finds a usable connection.
... View more
09-06-2023
06:11 AM
|
0
|
0
|
3208
|
|
POST
|
Yes, network analysis layers were substantially changed when we moved from ArcMap to Pro, and the problems you're encountering are related to those differences. In ArcMap, the data for the sublayers was held in memory. The only data source for ArcMap-style layers was the network dataset, and you could have a relative or absolute path to that dataset. In Pro, the sublayers reference feature classes on disk, so network analysis layers effectively have multiple data sources (the network dataset and the sublayer data). When you save your arcpy.nax solver object results to a .lyr file, it converts the sublayer data to the old-style in-memory feature classes. You're correct that there's no option to set a relative or absolute path to the network dataset. I believe it should work as long as the path to the network dataset is maintained. If you moved the .lyr files to a different folder, then the relative path to the network dataset path is probably broken. I can investigate whether we can fix this, but we are limited as to what we can do with .lyr files at this point. We don't really recommend using these because various settings (like travel modes) aren't fully supported in .lyr files. The .lpkx files are slower to create because it must write the sublayer data to feature classes on disk and go through the packaging process, which can be slow. The .lpkx output will definitely be more accurate and functional than the old .lyr files because they were designed for Pro compatibility. Honestly, both of these outputs are intended primarily for one-off debugging purposes (we use them a lot for debugging problems with network analysis services) where you need to investigate the analysis in a map and determine what went wrong. We don't really recommend that they be a part of regular customer workflows. If you tell me more about what type of logs you want to keep, I can try to suggest an alternate option that might work better. For example, maybe you can just write out all the settings to a json file, and if you needed to reload and re-run the analysis, you could just ingest the json in a script.
... View more
09-05-2023
07:26 AM
|
0
|
1
|
1857
|
|
POST
|
This is more or less expected. The .lyr format is an old ArcMap layer format, and Pro has to do a bunch of modifications and simplifications to the Pro-style network analysis layer to back-port it into the ArcMap-style layers. Various things are not compatible and will get lost in translation.
... View more
09-05-2023
06:39 AM
|
0
|
3
|
1863
|
|
POST
|
I've actually recently been doing some research regarding preassigned origin-destination pair problems. I know this is a common workflow, and my team would like to find a more convenient workflow. If you have a few minutes and are willing, could you fill out the attached survey and return it to me? This would be very helpful in helping us understand user needs so we can design something better in the future. Thanks!
... View more
09-05-2023
06:30 AM
|
0
|
0
|
3224
|
|
POST
|
Happy to help with this. As you've discovered the OD Cost Matrix is useful when you want to calculate the travel time and distance between all origins and all destinations or between all origins and the closest k destinations or all destinations within some cutoff. It's not the right tool to use if you have preassigned origin-destination pairs. You can use the Route solver to handle preassigned origin-destination pairs. You have to make sure each origin and destination are assigned to the same route. You can use the RouteName field in the input Stops for this. All stops with the same RouteName value end up on the same route. Let's say, for example, you have rows for stops A, B, C, and D. A is assigned to B, and C is assigned to D. You should create a RouteName field and give the rows for A and B a RouteName value of A-B and rows C and D a RouteName value of C-D, or something like that. The Route solver will generate two separate routes, one from A to B and the other from C to D. Since the number of routes you have is pretty large, you may benefit from this downloadable toolset: https://github.com/Esri/large-network-analysis-tools One of the tools in there is intended to solve large problems with preassigned OD pairs exactly like you're describing.
... View more
09-05-2023
06:28 AM
|
1
|
3
|
3226
|
|
POST
|
Hi Jonathan. Happy to help. I couldn't tell from your question whether you have already created a cost attribute in your network based on the field you calculated. If not, the first thing you need to do is set up this cost attribute: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/cost-attributes.htm You can't do that via Python. It should be done manually as an edit to the network dataset properties, and once you've set it up, you have to run the Build Network tool to build the network and incorporate those changes. You should probably also configure a travel mode on the network that uses the new cost attribute and any restrictions you want to apply during the analysis: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/travel-modes.htm Once your network is configured correctly, you can use the travel mode when configuring your analysis in arcpy. I noticed that you mentioned using a service area layer in arcpy. This is okay and will work, but we recommend using the newer/faster/simpler arcpy.nax module for doing network analysis in Python. It doesn't use layers but instead uses a set of Python classes that should have everything you need. https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/performing-network-analysis.htm
... View more
08-30-2023
07:41 AM
|
0
|
2
|
1618
|
|
POST
|
I think you're correct and this is not possible. However, if you put a really long delay time for each turn category you care about (for instance, all left turns), this would effectively restrict them.
... View more
08-09-2023
11:26 AM
|
0
|
0
|
2389
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Monday | |
| 1 | a week ago | |
| 1 | a week ago | |
| 1 | 06-12-2026 01:53 PM | |
| 1 | 04-21-2026 08:39 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|