Latest Contributions by DamienPyne

‎02-13-2020

Thanks Paul for the quick reply. I will look into what impacts going to Pro 2.5 / untools 2.5 will have for our project.

‎02-13-2020

I am looking for some support in how to configure parallel ranks. The documentation on Tiers—ArcGIS Pro | Documentation states: Tier rank In a domain network, the relative position of a tier is called a rank. Ranks control the trace order of subnetworks from different tiers. A rank value is assigned to a tier when it's created. A value of 1 represents the highest rank, and higher numeric values represent tiers with lower rank. Parallel ranks are supported for both tier definitions. For example, in a gas network, the System tier and Gathering tier can both have a rank of 3. We defined our tiers with parallel ranks in our model: This produced the following error when applying the AP. 2020-02-12 14:45:04 The asset package has the following errors (1/1): Item Field OID Value Message Level0 B_Tier rank None None Rank must be 2 error Failed to execute (AssetPackageToUtilityNetwork). Once we changed the ranks to sequential 1-11 there were no issues. We are using Pro2.4.3, 10.7.1 Any help would be fantastic, not sure if you could offer help Remi Myers‌ or Paul LeBlanc‌.

‎02-04-2020

Does anyone have any documentation or knowledge on how to use the filter function barrier function within tracing? The only page I can find on this is very limited in its explanation: Barriers—ArcGIS Pro | ArcGIS Desktop I am trying to make this example (from the Barriers—ArcGIS Pro | ArcGIS Desktop page) work: Suppose you want to run a trace and have it stop at any open device, but you don't want the trace to travel more than 500 meters beyond the starting point. To accomplish this, you'd use a barrier condition to control the type of open device that stops a trace, and you'd use a function barrier to calculate the length of the line you travel and set a limit of 500.

‎11-05-2019

Will although you have re-projected the asset package, you need to also re-project the data, and the service territory. In the scenario you are referring to, I projected the AP to GDA2020, the data was transformed from GDA1994 MGA 56 to GDA2020 and the service territory was based on GDA2020. In the data I loaded, I had created some errors for testing, and additionally created new features for dirty area tests.

‎09-05-2019

Kaitlin This appears to be a limitation in earlier version of Pro and has only been supported for version changes with branch versioning since pro2.4. See this post. https://community.esri.com/thread/228267-how-can-i-see-branch-version-changes

‎08-27-2019

The versioning strategy changing was the issue. I will see if we can reproduce and get a support ticket raised.

‎08-27-2019

Strangely enough when we tried to return the owner back to the original user the system errors that the input dataset must be branch versioned. Weird as this was in branch versioning. Next is the re-enable branch versioning then try again. If that fails we will again attempt to return the owner to the original user. I’ll keep you updated as we have seen the database change from branch to traditional without anyone actually changing this.

‎08-27-2019

Melissa Have you heard of any issues with this tool? We have run the GP tool and changed the service owner. After attempting to run disable topology an error is generated. We have also restarted the servers in case there was an impact. Are there any other steps that need to be performed?

‎08-11-2019

I believe the change Portal Utility Network Owner GP tool now updates this field.

‎08-11-2019

Vish This is something available in Pro2.4 UNv3 via a GP tool. This did not work in pro2.3/un v2

‎08-08-2019

Thanks Ben. I will have a ticket raised.

‎08-08-2019

Cheryl In the updated documentation for the Electric Utility v3, there is a section discussing subnetwork management. This explains these codes and their use. https://solutions.arcgis.com/electric/help/electric-utility-network-foundation/design-pattern/advanced-modeling-considerations-for-electric.htm Lifecycle_Status is a domain whose codes and descriptions represent the life cycle phases of a feature and is applied at the subtype level. Each code represents one bit in base 2 binary. The Lifecycle_Status domain has a bit sequence of: Domain code (Base 10) Domain description Base 2 value 0 Unknown 000000000 1 Proposed 000000001 2 Approved 000000010 4 Under Construction 000000100 8 In Service 000001000 16 To Be Retired 000010000 32 Abandoned 000100000 64 Retired 001000000 128 Removed 010000000 256 Out of Service 100000000 The Lifecycle_Combined domain is applied at the feature class level and includes all the values in the Lifecycle_Status domain, along with bit combinations. The following example shows bit addition which are used in the trace framework and subnetwork definition. This is just a subset of values in the domain and does not include every value. Domain code (Base 10) Domain description Base 2 value 0 Unknown 000 1 Proposed 001 2 Approved 010 3 Proposed and Approved 001 + 010 = 011 4 Under Construction 100 6 Approved and Under Construction 010 + 100 = 110 Network attributes use the Lifecycle_Combined domain assigned at the feature class level to present valid options in a trace or subnetwork definition. The subnetwork definition has bitwise operators that can leverage the addition of bits. For example, the domain value 3—Proposed and Approved, is the addition of two domains, 1—Proposed and 2—Approved. Hopefully this helps.

‎08-04-2019

Hussein, When did patch one get released (pro 2.4.1)? Or when is this planned to be available?

‎07-15-2019

Thanks Paul. You stated the "the default dirty area size ...". Does this mean there is a configuration somewhere that can be updated?

‎07-15-2019

From the images relating to the Utility Network - Dirty Area of point features, what unit of measure is used with the buffer distance to create the polygons? It appears the buffer distance is always 0.5 so the diameter/perimeter distance is 1 and the unit of measure is based on the reference coordinate system of the utility network service/datasource. In the Naperville Demo data, the reference coordinate system of the data/service is projected of feet (NAD 1983 StatePlane Illinois East FIPS 1201) and the resulting dirty area is 1ft perimeter. We have developed a PoC with data in Geocentric Datum Australia 2020 (GDA2020) which is geographic in decimal degrees. 1degree in distance is approx. 101-111km depending if relates to Latitude or Longitude. As you can see, the perimeter distance is approx. 100-110kms which is a consistent methodology to the 1feet example with the Naperville data. Also, can it be confirmed this resulting buffer is passed to a minimum bounding box function to produce the rectangle as the buffer on points creates circles? Paul LeBlanc‌ is this related to the projection issue mentioned in Applying WaterDistribution_AssetPackage fails‌ or related to Apply Asset Package error - Get attribute metersPerUnit does not exist‌

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by DamienPyne

Re: Utility Network - Parallel Tier Ranks

Utility Network - Parallel Tier Ranks

How to use: filter function barrier function in tracing

Re: Dirty area measurement of use

Re: Why would 'version changes' command be greyed out?

Re: How to change ownership of UN from portal user "a" to "b"

Re: How to change ownership of UN from portal user "a" to "b"

Re: How to change ownership of UN from portal user "a" to "b"

Re: How to change ownership of UN from portal user "a" to "b"

Re: How to change ownership of UN from portal user "a" to "b"

Re: Editing the Utility Network in 3D - new objects not showing in the scene

Re: Utility Network--how to determine what codes to use for new coded values in a domain?

Re: "Network topology must be enabled" after enabling Network topology on Utility Network

Re: Dirty area measurement of use

Dirty area measurement of use

Re: Comms Utility Network with Electric UN

Re: Contingent values changes the subtype selected

Re: ArcGIS Pro takes the screen focus

ArcGIS Pro takes the screen focus

Re: object snapping not aligned to grid location

APAC Utilities Community of Practice