Latest Contributions by RobertKrisher

As long as you are adding the layer from your utility network feature service as a regular layer and not as a subtype group layer you can run the 'add join' tool on the layer, no problem. Join field would be problematic because it would change the schema (and you could only do it once). All the discussions about performance implications still stand, I just wasn't clear enough about using the individual layer from the feature service instead of a subtype layer from the subtype group layer. ... View more

@GISUN If you need to refer to an attribute in order to control tracing or calculate summary statistics, you need to make it a network attribute. Normal attributes are not available in the Trace or Set Subnetwork Definition tools. With that being said, I recommend you download one of the Utility Network Foundations to learn how each industry uses different network attributes to control tracing and produce statistics for their subnetworks. If you want to include an attribute value in tracing/analysis it needs to be defined and validated as part of the network, this ensure that as we are loading the topology for analysis, we are also loading all the attributes required for analysis. You can imagine that if we didn't store this information with the topology and we needed to query individual features (or cache entire areas of the map) as we were evaluating the topology that this would be quite slow! ... View more

While @AyanPalit is correct about being able to change the XY tolerance and resolution I would caution you against changing these values because they are permanent, and they can have unexpected consequences. If you're having issues with features not being connected in your network because of the resolution/tolerance of your source database, then the recommended approach is to include a process to snap and correct these features during your migration to the utility network (using FME or geoprocessing tools). This gives you an opportunity to experiment with different snapping tolerances so you can find the right tolerance that minimizes topology errors and manual cleanup, while also maximizes the number of features that are connected (appropriately). ... View more

The associations widget isn't available in the standard map viewer, but there is a utility network associations widget available out of the box that you can add to your own custom applications. You can learn more about this widget and see the code samples associated with it on this page on developers.arcgis.com. ... View more

1) Relationships can be configured to be 1:1, 1:M, or M:N. The cardinality of associations is determined by the feature restrictions of the utility network. 2) By default, associations are M:N. However, point features are only allowed to have a single container. You can learn more about how associations behave by reading the feature restrictions page I linked to above, or by referring to the specific pages for connectivity, containment, and attachment. ... View more

There are typically two approaches taken: If you wish to draw each meter on the map, you would draw each meter as a device, connect each meter to a common electric junction (that is in turn connected to the LV line), and create a meter assembly to contain each meter device. If your organization is ok with representing all of this as a single location in your GIS than you would create an electric device (meter) in your network, then connect it to the LV line. If you wish to track individual meters in the GIS then you would create them as non-spatial electrical junction objects that are contained within the device. Ryan's approach is an alternative approach of this where they use a junction instead of a device and do not model the meters in the GIS (instead relying on a link to the CIS). ... View more