Latest Contributions by RemiMyers

Hi.  As you probably know, licensing for ArcGIS Pro/ArcGIS Enterprise is composed of four elements.  1) the user identity, 2) the Pro license (basic, standard, advanced), 3) the capabilities (view, editor, creator) and 4) any extensions (such as the Utility Network). The basic license for ArcGIS Pro is exactly what it says, it is a basic configuration that lets you have basic map components and elements but is very limited on advanced capabilities (such as the UN tools exposed in the Ribbon or GP toolbox).  For more details regarding the ArcGIS Pro licensing levels, I recommend this documentation.   The ArcGIS Utility Network Extension provides access to the functionality on the server side but has no ability to provide capability that is driven by licensing on the ArcGIS Pro side.  So you might ask, why did you include it in that statement, well, if someone were to write an add-in for UN-type capability it could work along the lines of a viewer role; we don't constrain that behavior, but we don't provide the tools to enable it.  ArcGIS Pro at the Basic level does not allow editing in a multiuser environment, so it is not available for editing.   If you have more questions about your licensing, I strongly recommend reaching out to your sales manager for more details and I apologize for the confusion in the blog. ... View more

Hi Serguei; I am not aware of any limitations with branch versioning features rendered in Scene.  As always, your best approach is to reach out to Esri Support to be certain that you are not running into a system issue.   For feature configuration guidance, I can walk you through some recommendations (just set up a meeting) and to better document the specific UN configurations (usually a function of device or equipment configuration) I will follow up with a blog on best practices for configuring the UN in 3d later this week. Edit: The below screengrab is a 3d UN project in a branch in a child version    ... View more

Hi Vish; At this time, controller-based traces such as Upstream or Downstream are regulated by the network controller designated in the Subnetwork properties.  Because Subnetwork configurations are limited to a single domain, there is no ability to directionally trace across multiple domains.   Considering that Subnetwork configurations were designed to represent the properties of feeders or circuits, I would not anticipate the core including multiple domains in a subnetwork in near or midterm releases.  If you have an absolute requirement to build a network that can directionally trace over a combined Sewer and Electric network, you always have the opportunity to integrate the two into a single domain, but I would suggest a lot of testing would be needed to ensure you capture all requirements of such a unique configuration. ... View more

Hi Danny; Those duct bank features were elements of the structure boundary layer in a utility network.  Containment associations were used to show the spatial features and nonspatial objects that were represented in each wall of the bank.   Please feel free to reach out to me @ Remi Myers‌ if you have more questions. ... View more