Latest Contributions by RobertKrisher

‎09-23-2024

Yes: One-way feature service-to-feature service sync (esri.com)

‎09-23-2024

Try just using start_reading

‎09-23-2024

Before you start reading/writing data with the version, make sure you call either start_reading or start_editing to establish a shared or exclusive lock with the version. When your script finishes/cleans up make sure you stop reading/editing in order to release locks.

‎09-23-2024

Instead of directly accessing the internal variable that holds the version manager (_version) you should go through the front door. Here is how I get the version manager, default version, and un object in most of my scripts: # Get the version and Utility Network reference messages.addMessage(f"Connecting to {version_service_url}") version_manager = VersionManager(version_service_url, gis=gis, flc=feature_layer_collection) messages.addMessage(f"Connecting to version: {version_name}") default_version = version_manager.get(version_name) utility_network_manager = default_version .utility

‎09-23-2024

For customers who haven't historically modeled their elbows, that's usually the first step. If you have a structure or assembly, make sure it shares the same container as the transformer. Ideally, when migrating your data to the utility network, you would create all your elbows, so you have nice, consistent pad-mounted transformers/elbows/busbar/pads and all the corresponding associations.

‎09-23-2024

It seems a little like cheating, but my preferred way to get a UN pointed as a specific version is to get it from the version itself. there is a "utility" property on each version that contains a reference to the utility network for that version (if one is present in the service).

‎09-23-2024

Most pad-mounted and underground transformers have elbows on them, it's just that they haven't historically been modeled in the GIS. It would look something like this: Most of the models released by Esri have contained both underground fuses as well as elbows, so you might as well capture these locations as elbows to start with.

‎09-23-2024

In the overhead system, an open point is usually an air gap between two conductors, typically at a dead end. In the underground system, an open point is usually one or more elbows in a cabinet (transformer, switchgear, etc) that are disconnected. In those cases, you should model it as an elbow, underground fuse, or the actual piece of equipment that is open/disconnected.

‎09-20-2024

This is not supported and doing so will corrupt your data because you will be bypassing the utility network which manages system-maintained fields and tracks edits made to the topology. For a discussion of approved methods for loading/manipulating data (Python, Rest, etc) read this series of articles: Journey to the Utility Network: Integrations Overview (esri.com)

‎09-18-2024

If you want to capture your basins you can choose to them as a point (BMP Point), polygon (BMP Boundary) or both, depending on your preferences.

‎09-18-2024

The boundary of a basin should also be modeled using the BMP Boundary asset group in the Structure Boundary layer. Each Basin will then contain all the BMP Inlets, BMP Points, and outlets associated with the basin. The various device features contained within the basin allow you to model the connectivity/flow for how water can enter/exit the basin. See screenshot from sample data below:

‎09-18-2024

If the ETL is going directly against the database and not through the Esri software, then this is the expected behavior. In order for the rule to run, the edit must occur in a location where the Esri software can respond to the edit and run this code. If you have web services published for these features you can have your IT department rewrite their ETL to use those web services. If you don't have web services or ArcGIS Enterprise available you could consider having your IT department use something like the ArcGIS Data Interoperability extension or Safe Software's FME to perform the ETL. If none of those options work, you can consider having your IT department perform this calculation as part of their ETL or performing this calculation as a batch process that runs after the ETL. This batch process would likely be a python script that recalculates this value using a field calculate that has this Arcade script embedded in it.

‎09-17-2024

Condition barriers apply to all the features in your trace unless you specify otherwise, so it is used to stop the trace at ALL out-of-service features. The output filter applies to ALL the features returned by the trace, so it will filter out the proposed features where the tracing stopped. You can control which lifecycle status values are included and excluded by modifying your conditions. You'll likely set it up to only include things that are in service or pending removal (if that's in your workflow/model).

‎09-16-2024

@MobiusSnake you can find them, along with their documentation, in this GitHub repo: arcade-expressions/attribute_assistant at master · Esri/arcade-expressions · GitHub. For any questions, please follow up with @MikeMillerGIS from the Solutions team.

‎09-16-2024

Use a condition barrier to stop the trace, then add an output condition to only return the in-service features: The Solutions team also has some tools available if you want to maintain your retired/abandoned/deleted features in a separate layer in case you only want in-service features in the network and all other features in the GIS but non-traceable.

Online Status	Online
Date Last Visited	51m ago

My Ideas

Latest Contributions by RobertKrisher

Re: Is it possible to replicate branch versioning feature classes in geodatabase to child geodatabase?

Re: Using python to Validate Network Topology in a version

Re: Using python to Validate Network Topology in a version

Re: Using python to Validate Network Topology in a version

Re: Electric UN Asset Type for Underground Open Point?

Re: Using python to Validate Network Topology in a version

Re: Electric UN Asset Type for Underground Open Point?

Re: Electric UN Asset Type for Underground Open Point?

Re: Insert record to a Utility Network feature class from PostgreSQL

Re: Why are catch basins and inlets represented as points instead of polygons?

Re: Why are catch basins and inlets represented as points instead of polygons?

Re: Immediate Calculation Attribute Rule Not being Triggered when table is updated on SQL Server and not in ArcPro

Re: How to filter trace configuration features by LifecycleStatus?

Re: How to filter trace configuration features by LifecycleStatus?

Re: How to filter trace configuration features by LifecycleStatus?

Re: Pre UN migration data cleanup workflows

Re: Can one web map hold two separate utility netw...

Re: Issue adding multiple view only utility networ...

Re: Mapping Energy Justice: How GIS Can Help Under...

Re: Add Network Attribute (Trace Network) Issues

European Utility Network Community (UNC)

APAC Utilities Community of Practice