Latest Contributions by RobertKrisher

@KokilaM I can't remember the specific asset type, but that's correct. The Power transformer that steps transmission/subtransmission voltages down to distribution levels would be a subnetwork controller for the distribution side of the station, then the circuit breakers for each feeder are also subnetwork controllers for each circuit. ... View more

@VishApte_NGIS an upstream trace as you have described it would show you the path upstream to the valve(s) to isolate the starting location(s), but not the area affected by the isolation. ... View more

If you want to do that you can use something like the batch trace tool to do a connected trace to get everything upstream of the processing plant. You can also set up each controller to have the same subnetwork name, maybe broken by rank (PP1 Gathering, PP1 Trunk), they're allowed  to be disjoint. If you keep the model as it is right now, and set up your compressors/pumps as your controllers then when you run an isolation trace it will show you how to cut off pressure from the pump/compressor to prevent gas/oil from leaking out into the enviornment. If you were to switch to a sink-based model, the isolation trace would only show you how to prevent gas/oil from getting to the treatment plant, but it wouldn't show you how to isolate the pressure source. Given that there is a workaround for naming your processing areas (batch trace tool) but not for isolation traces, I would lean towards rely on the model as it was built. You know your data and your business requirements better than I do. Those trunk lines are probably much easier to understand how to isolate than a typical distribution system, but if you model the pipework inside stations than it will be very beneficial to have that isolate trace working the way it was originally configured. ... View more

@Joshua-Young @PierreloupDucroix If you haven't already, please log a case with support on this so they can get a bug created and get a fix out for the next person who comes along with an unwieldy map! ... View more

@SamDeLore tips for looking at logs to understand performance: Utility Network Diagnostics Parsing Utility Network Diagnostic Logs ... View more

@VishApte_NGIS what devices are responsible for moving resources through the system? is it the wellheads, pumps, and compressures that are pressurizing and moving materials through pipes? or something at the destination which is drawing materials towards it? The most important consideration to all of this is how it will respond to an isolation trace. The isolation trace shows you how to isolate an area of a subnetwork from its controllers. If you model your tiers using sinks, then the isolation trace will show you how to prevent materials from arriving at their destination, and which production sites will be cut off. If you model your tiers using sources (the typical way for pipeline) the isolation trace will show you how to isolate an area of the network from its supply and which processing plants/refineries might not receive materials as a result. @TomDeWitte  ... View more

I can't think of a way to do that, since you're talking about dynamically symbolizing every manhole based on subnetworks that aren't shown. ... View more

Another way you can do this is to set up a Survey123 form to capture the information that includes a unique ID for the asset. You can then use a dashboard (or arcade expression, python script, join layer, etc) to bring the two datasets together for reporting purposes. I just got done writing a series of microblogs outlining this technique on LinkedIn, and I'm in the process of rewriting the series into a series of community posts. DM me if you want the link to the original article(s) in the meantime. ... View more

Depending on the database you're using you may need to run something like a prune or vacuum if you want to reclaim the disk space associated with deleted records. If you are pruning on a regular basis, then doing this after every prune isn't necessary, since you'll need to reallocate the same disk space. If you've hit some kind of unreasonable high water mark, then reclaiming the disk space may be worth while. ... View more

See @NicoleJohnson 's response. ... View more

I'm not sure if deleting unnecessary attribute rules for view only data is going to provide any benefit, unless those rules reference objects that aren't in your read-only instance. It`s not a bad idea to apply different levels of post-processing after creating our read-only instance, but just make sure they're providing good value. ... View more

From my previous response: "The feature service definition doesn't support the full capabilities of the web map, so you'll always need a web map to create full-features web/mobile applications". That is why you get that warning when you overwrite a feature service. There are known issues and limitations with trying to put the full configuration of a web map into your feature service definitions. The most common example is that this can cause subtypes and coded value domains to stop working. ... View more

@jsarthur There is a lot of nuance, pro/cons to the questions you are asking that you're going to have to work through. The easiest, most reliable, and often fastest way to move a whole dataset is by doing a database backup/restore. This creates a 1:1 duplicate of your database. You can also use feature services to synchronize data, python scripts, FME workbenches, etc. But you'll need to find the right approach that meets your requirements of complexity to implement/maintain, performance (of transfer and final system), and functionality of the final system. As you pointed out, if you are just trying to view and query data in this other system, you don't need to bring over the utility network. But if you do bring over the utility network, the data will need to be versioned. ... View more

@D_Atkins the best practice is to put the majority of your definitions for symbology, labels, etc in a web map instead of the service. The feature service definition doesn't support the full capabilities of the web map, so you'll always need a web map to create full-features web/mobile applications. Additionally, putting all your configuration in a feature service means you're limiting yourself to only supporting a single user experience. A single feature service supporting multiple web maps uses less server resources and is more scalable than creating a bespoke feature service for each web map. ... View more

I don't immediately know the answer to this one, please log a case with support. ... View more