Latest Contributions by RobertKrisher

There are two users presenting on this topic at the upcoming User Conference (2023): Managing Facilities & Vertical Assets with GIS ... View more

@RomuldKiobya when you export your asset package you can (and should!) choose to include the data from your database. Then after you've adjusted your service territory in the asset package you should apply the asset package to a new geodatabase. ... View more

Try running the tools directly from the geoprocessing pane instead of through the task framework and see if that produces more consistent results. ... View more

@JeffBlake The best practice depends on what kind of user you're sharing your map with. For a collection of best practices for creating maps referencing utility network data, I recommend you refer to the following tutorial. This tutorial demonstrates the importance of configuring things like subtype group layers and display filters. For desktop users, you should create a map using ArcGIS Pro that references those feature services and either share the individual map with them as a map file or if you have a collection of items (multiple maps, page layouts, etc) you may choose to share an entire project with your users. For web users, you will likely still use ArcGIS Pro to author your map, but you will share the resulting map as a Web Map. This web map should be very similar to your desktop map, especially with regard to the use of subtype group layers. The only catch is that you must be using at least ArcGIS Enterprise 10.9.1 for subtype group layers to appear in your field maps and at least ArcGIS Enterprise 11.1 for subtype group layers to appear in the Web Map Viewer in ArcGIS Enterprise. ... View more

@JeffBlake the map used to publish the feature service should not have subtype group layers. The subtype group layers should be used when you are consuming the feature service in your desktop maps or web maps. ... View more

As long as the cable is spatially coincident with both the network distribution point and the address point you should be able to achieve this by creating an attribute rule that runs when a new drop cable is created. It can then perform a spatial query to find the network distribution point and the address point information and perform the logic you have outlined above (calculate the cable type, update the customer count on the distribution point, and associate the address point with the distribution point). You can learn more about attribute rules on this page in the online help. You can also try out two free tutorials that show you several examples of how to use attribute rules (one and two). ... View more

The scratch workspace is a great idea, since you can re-use the same table within the same session instead of having to recreate it every time your run your tool. If you did want to create a new temp layer each time you ran your tool, I'd recommend you use the memory workspace for the duration of the trace. To do this just use the word "memory" for the workspace path (e.g. "memory\\temp_start_barriers"). ... View more

Open the Set Subnetwork Definition tool, select your low voltage tier, and look at the Subnetwork Trace Configuration > Summaries section. You will see that there either isn't a summary for calculating circuit length on this tier. You should be able to add a summary with the function of "Add", on a network attribute of "Measured Length" into the "circuitlength" attribute. Every model is a little bit different so if some of these attribute names don't match up you should use the same configuration as in your distribution/mv tier but remove the filter (that limits it to MV conductor). The circuit length is calculated using the measured length of all medium-voltage conductors in a subnetwork, so it would make sense that it isn't being calculated for your low-voltage tier. ... View more