POST
|
@MichaelAdornetto1 If your utility network is not already a UNv7 and you are trying to run Upgrade Dataset from Pro 3.3.x/Enterprise 11.3 please create a case with Support so that we can look into this further.
... View more
4 weeks ago
|
0
|
0
|
58
|
POST
|
@abderhman97 The Telecom Domain Network for ArcGIS Pro 3.5 Beta is now available on the Early Adopter Community here.
... View more
4 weeks ago
|
1
|
0
|
77
|
POST
|
Good day @abderhman97 The telecom domain network is currently in beta and is not available outside of the Early Adopter Community. The beta program will be available shortly and we will update this thread with an invitation once available.
... View more
06-24-2025
08:00 AM
|
2
|
1
|
269
|
POST
|
@AndreLoerch
The active portal user account as the owner of the dataset in portal and is based on the active portal user when the dataset is created. This owner allows you to restrict access for administrative tasks to be performed on on the dataset. If the account used for your portal dataset owner has the potential to change it would be a good practice to create a headless user that your team would use for this purpose.
As you noted in your solution above, we allow you to change this portal trace network owner assignment easily using the Update Portal Dataset Owner GP tool as long as you can connect to the dataset using the trace network dataset owner account.
Thank you for pointing out the issue with the documentation. I will work with our team to make updates to this topic in a future release.
Jon
... View more
10-14-2024
01:14 PM
|
1
|
0
|
707
|
POST
|
ArcGIS Solutions has updated Utility Network Package toolbox 3.3.1 with a new parameter in Stage and AP to Geodatabase to specify the Utility Network version to create (6 or 7).
... View more
08-29-2024
09:07 AM
|
1
|
0
|
1299
|
POST
|
@MatteoMagnani_WT I would add that the Rebuild Network Topology tool (and the rebuild current extent command on the Validate command dropdown are intended to specifically address inconsistencies in the network topology which prevent the topology from being properly validated and updated. Here is an example: As John mentioned, these can be targeted against a specific extent of your network exhibiting the issue. Think of this as a targeted enable network topology operation that rebuilds the network in the extent regardless of the presence of dirty areas. The Verify and Repair Network Topology tools on the other hand are intended as diagnostics to identify potential issues in the internal system tables and address these. These tools do not provide a spatial filter and are run against the entire network.
... View more
08-27-2024
07:04 AM
|
0
|
0
|
1017
|
IDEA
|
07-23-2024
09:53 AM
|
0
|
0
|
498
|
POST
|
To add to Mike's response... If you were to run an aggregated geometry trace using the Synthesize Geometries parameter, this would also return aggregated geometry for the edge object or association from which you could derive length. Synthesize association geometry in a trace Synthesize geometry for edge objects in a trace
... View more
06-18-2024
12:48 PM
|
1
|
0
|
684
|
POST
|
@ReyesAlami You referenced you're working with ArcGIS Pro 3.3 and Enterprise 11.2. When working within an enterprise deployment, the version of ArcGIS Pro and the portal's federated server are used to determine the compatible Utility Network Version. UNv7 is supported starting with Enterprise 11.3 so this combination would create a UNv6. Being that you are already at this version this is why you are seeing the "dataset is already upgraded". https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/utility-network-compatibility.htm
... View more
05-24-2024
04:54 AM
|
0
|
2
|
993
|
POST
|
@rlyding This appears to be a bug. I will look into this further, and I'd recommend reaching out to Support to get this logged.
... View more
05-16-2024
06:15 AM
|
1
|
1
|
2653
|
POST
|
You mention elevation features; however, based on the description it sounds like you are looking for guidance on setting up display filters to display different features and/or labels at different scales. https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/display-layers-at-certain-scales.htm Depending upon what you are looking to achieve, Containment Associations can also be used to control the level of detail shown in the map. https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/association-visibility.htm Does this align with what you are trying to achieve? Jon
... View more
04-15-2024
11:36 AM
|
0
|
0
|
1021
|
POST
|
Good afternoon Ben, Single-user deployments in either a file or mobile geodatabase provide access to the same analytic capabilities of the utility network; however, these cannot be published to create a utility network service. The publishing and consuming services topic touches upon this. While it does not explicitly state that utility networks in file and mobile geodatabases cannot be published, it does communicate that "map layers must be from a database connection established as the database utility network owner, and that all network layers must be registered as branch versioned", both of which are only possible when the data source is an enterprise geodatabase. While you cannot publish the UN in the file geodatabase, you can still configure and test your network in the file geodatabase and copy the UN into an enterprise geodatabase for publishing once you feel comfortable with it. Hope that helps, Jon
... View more
11-16-2023
12:21 PM
|
1
|
0
|
948
|
POST
|
Good morning, I am unable to reproduce this behavior with a trace network in 3.1.2 or 3.1.3. If there are current TN_Temp_Starting_Points and TN_Temp_Barriers feature classes in your project's default geodatabase, could you test deleting these and recreating them by placing the trace locations again to see if the issue persists.
... View more
09-05-2023
04:50 AM
|
0
|
0
|
862
|
POST
|
Good evening Alex, I am not clear on what the end goal of these traces are so cannot comment on alternatives but... for the first example, we cannot evaluate network attributes across two separate classes in this way. Because the values associated with the network attributes are not present on both feature classes, the expression will never evaluate as true and stop the trace. The second example you show using the value of "h_l = 214" applies a simple condition barrier that stops the trace once satisfied at the highlighted line (as well as the line south of the junction) . The highlighted line is excluded from the trace because it satisfies the barrier condition and the Include Barrier Features parameter is unchecked. Checking that box should return the expected result:
... View more
07-26-2023
11:46 AM
|
1
|
1
|
1006
|
IDEA
|
This capability was added in ArcGIS Pro 2.9. Here is the text from the What's new in ArcGIS Pro 2.9: You can migrate utility network datasets between geodatabases for staging and testing using Copy and Paste tools and the Export XML Workspace Document and Import XML Workspace Document geoprocessing tools.
... View more
07-18-2023
11:53 AM
|
0
|
0
|
1787
|
Title | Kudos | Posted |
---|---|---|
1 | 4 weeks ago | |
2 | 06-24-2025 08:00 AM | |
1 | 10-14-2024 01:14 PM | |
1 | 08-29-2024 09:07 AM | |
1 | 06-18-2024 12:48 PM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|