Latest Contributions by RobertKrisher

You can use the version differences tool on the versioning toolbar/tab to see all the edits in the version (depending on whether you're talking about ArcMap or ArcGIS Pro). This dialog is very similar to the dialog shown during conflict resolution, and while it will definitely show you all the edited features and their original values, I'm not sure if it actually allows you to revert changes. ... View more

As an update on this thread. Support for subtype group layers was added to the map viewer in ArcGIS Enterprise 11.1. ... View more

@FenuxLabs Another approach is to use the Export Subnetwork or Trace tool to export the connectivity to a JSON file and use the resulting file to walk the graph. You can find a code sample of how to do this along with instructions over on this community article page: Parsing Utility Network Exports (esri.com). ... View more

The correct approach for what you want to do is to use the ArcGIS API for Python. I was able to get around some of this by saving an existing utility network layer to a file, then opening it as a layer file, accessing the first layer in the file. But I ran into problems in getting the rest the tools to behave properly, especially since they don't get me the ability to set/clear locks as I discussed above. ... View more

Switch the order of input/near parameters in your GP tool. You want the poles to each find their nearest road (then use the near_x and near_y), doing it the other way around means that each road will only find its nearest pole 🙂 Specifying a reasonable threshold is always a good idea. One of the biggest limitations of this approach is going to be how streetlights are captured in intersections (which street do they get assigned to?), but this approach will work well for long running stretches of road. ... View more

Cheryl,  Ah, context is always important here. It would make sense for utilities that share the same structures (electric and communications) to be in the same utility network and feature dataset with separate domain networks. For your other domains it is less likely that they are sharing the same structures (e.g. potable water and reclaimed water) so there isn't as much of a benefit in keeping them in the same utility network.  Just to reiterate one of the cons of combining within the context of your current situation. Having everything in the same feature dataset and utility network also means that any time you are administering one of the layers, you need to lock all the features in the dataset (meaning schema changes to water would require kicking editors from all departments out of the GIS). As you mentioned, this isn't a problem now because there's only a single editor, but the moment you start trying to bring in a second editor or have an admin and an editor you will need to be much more deliberate about coordinating changes. I don't know which commodities you have on your campus, but I would expect electric/communications to share a network, the water networks to each be separate, and anything like district energy to also be in a separate network. You're free to combine them into a single network, but you'll experience some of the cons listed above and earlier in the article. ... View more

You could use the generate near table tool to identify the street centerline closest to each pole, and by turning on the Location option it will include the location on the centerline. You can then create a point layer from the coordinates in your near table (remembering the ID of the line), and join in the information from your pole layer whether it has a streetlight or not. That should make it much easier to visually review the centerline data. ... View more

Let's look at the different approaches for separating or combining this data and the pros/cons of each. Firstly, Esri provides standard models to get you started for Water, Wastewater, and Stormwater (links and descriptions can be found in this article), and for the purposes of this discussion let's assume you're starting with one of those models. Your initial approach of putting them all in one network and separating them out by tier would imply that you aren't using one of the Esri models, which separate them out into different domains (Water lines, sewer lines, etc). If you wanted to do this you would need to make your own model (which is a lot of work!) where everything has a single domain and as Mike noted doesn't really align operationally with how you manage these systems. In this situation all of your layers would have a single set of rules, fields, and drop downs that all users would share. Users would be able to view/edit all the data in the network, so you wouldn't be able to restrict editing of water data to water users or vice versa. The second approach often considered is to combine the different domains of models provided by Esri into a single utility network. This sounds good at first, but because everything exists in a single-network that means that all your viewers and editors from each department will need to be able to view/edit all the data in the network. So water people will be able to edit wastewater data and vice versa. The same can be said of the administrative experience. This does make it easier to manage/maintain, but once again it typically doesn't like up with the way that organizations want to administer their systems (in this case IT systems and databases, instead of pressure zones and sewershed areas). Finally, the most common approach is to create separate feature datasets and utility networks for each domain. These allows the user/administration privileges for each domain of data to be managed independently of the other network domains. It is still possible to trace between these separate networks by using tools such as the "Add Starting Locations" gp tool to turn the results of one trace into the starting location of another trace. ... View more

Please log a case with support. ... View more

@rpepato_bizpoke Glad it was able to help you move forward. If you can reproduce the issue, or if you have a copy of the database where you can reproduce the issue, I encourage you to log an issue with support so we can determine what caused this and get it fixed. ... View more

I've been out this week so haven't had a chance to test this on my end, but are you saying if you run a standalone python script that does the following: Create Layer (using feature service URL and giving it some unique layer name) Change version (on layer) Validate topology (on layer) You are seeing that it is still only validating default? If you're performing this test in ArcGIS Pro you should make sure that the layer name you are using is unique. I can tell you that the ArcGIS API for Python does support all this. ... View more