Latest Contributions by MelissaJarman

Welcome and thanks for joining the Utility Network GeoNet community! To get started we invite you to first review the group features on the overview page and familiarize yourself with the group info, space owners, and GeoNet terms of use. As you explore the group, you'll also find tools to connect and collaborate. We encourage you to use the Utility Network GeoNet community space to ask/answer questions, share files, and participate in discussions. Feel free to use industry-focused community spaces to collaborate on items specific to the Utility Network Package tools and configuration process:  Industry community spaces: Electric and Gas‌ Telecommunications‌ Water Utilities‌ We invite you to post a comment below to say "hello" and introduce yourself and share what part of the utility network are you looking forward to working on. We're excited to connect and collaborate with you and we look forward to seeing your contributions. - The Utility Network team ... View more

Questions specific to the Utility Network Package tools will be discussed in the following topic: Utility Network Package Tools FAQ This document compliments the following topic: FAQ help topic for frequently asked questions.   Please contact the utility network space owners to request additional questions to be added to the FAQ.   Can the service territory feature class be updated?  There is not currently a tool that allows the service territory to be updated. The options available to account for this are: Make the initial service territory slightly larger than your intended work area to account for potential growth. Keep in mind that network features can be created anywhere within the service territory extent. Use the Utility Network Package tools to export the current utility network configuration to an asset package, stage the utility network using the modified service territory, and reimport the network configuration using the asset package. Can I change an Asset Group or Asset type in the utility network?  The asset group field is assigned as the subtype field for network feature classes and serves as the major classification for network assets. You can configure additional asset groups by disabling the network topology and adding new code/description subtypes. Existing subtypes cannot be altered or removed, and the subtype field cannot be changed for the feature class. The asset type field is configured using attribute domains to represent the minor classification of network assets. You can configure additional asset types by disabling the network topology and adding new code/description pairs for the coded value domain. Existing coded value domain code/descriptions cannot be modified, and the domain cannot be deleted. BUG-000115603 - Marked as designed What is the maximum number (max code) for an Asset group subtype and an Asset type domain?   The code limit for the asset group and asset type allowed is 1024. This means asset group subtypes and asset type domains can be created with codes as high as 1023. The asset group and asset type fields are used by a utility network for feature classification. These represent the major and minor classification for utility features. To support this, subtypes and coded value attribute domains are configured for these fields. These are stored internally in the network topology as In Line network attributes.  Note - The attribute domain associated with the asset type field must have a field type of short integer.   How many inline network attributes can I have in a utility network? A utility network reserves a total of 64 bits for system and user-defined inline network attributes. The network properties list the network attributes and the bit size for those that are stored In Line. There are various system network attributes that are stored In Line which use a portion of the available bits. For utility networks that are created with ArcGIS Pro 2.8 and earlier, a total of 20 bits are reserved for user-defined In Line network attributes.  The number of reserved bits was increased with ArcGIS Pro 2.9, to 21 bits and further with ArcGIS 3.0, to 25 bits reserved for user-defined In Line network attributes.        Review the network attributes topic to see how to calculate the bit size for In Line network attributes. ... View more