Latest Contributions by VishApte

Export Asset Package with data and Reapply Asset Package worked.  Device Status is updated with in-line network attribute of 3 bits. Traces work correctly. It will be nice if Pro UN toolset adds a tool to remove network attribute or reset network attribute and to remove network attribute assignment. ... View more

Trying to fix my model so that inline field bit size updates to 3 to cater for additional value of 4 in the Device Status Combined domain. But I cannot find a tool to remove network attribute or disassociate network attribute so that I can add it again. Adding the same attribute errors out. ERROR 001952: Network attribute with the specified name already exists. Failed to execute (AddNetworkAttribute). Parameters were: Input Utility Network UNWater Utility Network Attribute Name P:Device Status Attribute Type SHORT In Line INLINE Apportionable NOT_APPORTIONABLE Domain Name 6_Pipeline_Device_Status_Combined Is Overridable NOT_OVERRIDABLE Nullable NOT_NULLABLE Substitution NOT_SUBSTITUTION Network Attribute to Substitute Updated Utility Network UNWater Utility Network Looks like I will have to export asset package, fix network attribute and reapply 😞 ... View more

@MikeMillerGIS  I tried the same in Naperville V4 model and I could not reproduce. The only difference I found is Naperville v4 model schema v2.6 does not have "Device Status Combined" domain and does not have "Device Status" domain, only "Valve Status" domain. Also, I found network attribute definition is different. Naperville model has as below.   My model also V4 and created using Pro 2.6.0 has Will it making the difference?  Cheers, Vish   ... View more

Thanks @MikeMillerGIS . Bit more involved than SQL queries and joins but I think that will do the trick. Just a quick query, I guess fromnetworksourceid and tonetworksourceid translate to Junction/Device/Line/Assembly layer that can be queried using from/to globalid for additional details.  Where will the mapping be for fromnetworksourceid and tonetworksourceid to the Junction/Device/Line/Assembly layer ids? ... View more

For Sewer Networks, I would prefer to model Manholes as Sewer Devices rather than Structure Junctions. It  can then control the flow of the resource like sewer. In reality, manhole can get blocked, flooded etc. and is important to trace to/from. I have a customer who wants to model Manhole as a Sewer Line instead of junction or device, albeit it will be a vertical line. And then model inlet and outlet as junctions that connect to manhole. I dont see anything wrong with this modeling but just haven't found courage to try implement it this way 🙂  For inlets and outlets, I can imagine three ways to model them. 1. As attributes for manhole as a sewer device. One of my customer deployed it this way. Inlet level and type, Outlet level and type, cover type, cover elev etc were captured as attributes.  2. Model them as sewer junctions that connect to manholes as devices. Inlet and Outlet can have Z value that represents depth or can have attribute for depth. Pipe(s) connects to inlet or outlet. 3. Model inlet and outlet as "terminals" for manholes. There will be editing overheads to specify terminals for pipes.     Re. 80 different types of manholes, inlets etc specified by an abbreviated code, using FME's AttributeFilter transformer, you can apply filter and specify attribute mapping differently before writing to output UN feature class. Hope this helps, Vish ... View more

Yes, I too observed this behaviour when symbology is based on anything other than assetgroup, the assettype comes as numbers and doesnt display the text. End user doesnt know what those numbers mean. I found that for publishing feature service, it is best to leave the symbology based on assetgroup. If I dont want certain assetgroups, I use definition query in the map to filter them out or create multiple layers such as WaterValve, WaterPump etc out of WaterDevice. And I reset the feature creation templates accordingly. We need to do this any way due to the under-nomalised data model. This is in ArcGIS Pro or Portal Web Maps. I haven't tried with Collector just yet but I guess it is pretty much dictated by the web map used. My guess for this behaviour is, because assettype has different domain for each assetgroup, using symbology based on anything other than assetgroup, the service definition JSON doesn't list domain values for every assetgroup. Hence the numeric code doesn't get converted to text. And I think it as a bug rather than a feature 🙂  ... View more

@JamesWright9 I am assuming you work for either Schneider or Latitude 🙂 I am working with a large Utility migrating them from GN to UN. This client currently has Geocortex Web. The target go live for UN is Q1 2022. Will ArcFM Web be UN ready by then?  ... View more

Though there are UN admin tools and standard GDB tools to perform all required configurations such as adding a new subtype, domain for asset types, topology rules, terminals, network attributes etc, I find Asset Package is still the better way to apply the model changes. The process I follow is 1. Export existing UN model as Asset Package including data. 2. Make changes to the FGDB feature class definitions as necessary 3. Add/update/remove to appropriate B_* tables. 4.  Optionally, make any changes to the data or C_* tables if required. 5. Re-apply asset package in full replacing entire geodatabase. 6.  Version dataset 7. Enable topology. 8. Republish/restart the service. Not sure if this was a bug (or user error 🙂), but tinkering with the feature class definitions especially assetgroup (subtype field) required me to republish the service. Existing service was failing to restart due to a renderer issue of some sort. Downside is, it could be a longer downtime.   ... View more

Thanks @MelissaJarman  I can now see what Status Descriptions mean. However, I am still not sure why my Dirty Areas with status 9 (1 + 😎 doesn't go away after I shortened the geometry and Validate UN Topology was successful. I had to Disable Topology and Re-enable to see those dirty areas go away.  This is with ArcGIS Pro 2.6.3, UN v4, ArcGIS Enterprise 10.8.1 plus UN SP1.    ... View more