Fire Hydrants, presentstatus, and UN Water Foundation maps

[GavinMcGhie]

As I begin to integrate our UN into the default maps provided in the Foundation package for water (v1_3), I find that all of our Fire Hydrants are white dots. This appears to be related to the fact that their presentstatus field is null. The symbology appears to expect 3/2 for active/inactive. However, there is no domain associated with this field for the Fire Hydrant AT subtype, so 3 and 2 don't appear to have any meaning except in the map symbology. I confirmed there is no domain associated in the data dictionary. All of our Hydrants are active as well. So now we need to decide whether to add a random value of 3 to this field for all Hydrants, or modify all the default maps for publishing. I'm guessing this was just overlooked when creating the maps? Has anyone else addressed this? Of course the goal is to minimize changing things later as the UN progresses...

Thanks, Gavin

[MichaelParma]

Hi Gavin,
From what I can tell on the data dictionary online, the presentstatus field on water device and fire hydrants uses the Pipeline Device  Status domain: (https://solutions.arcgis.com/water/help/water-distribution-utility-network-foundation/DataDictionary...) 

Hope this helps,
Mike Parma

[GavinMcGhie]

Hi Mike

Thanks for the hint, and I would agree that appears to be the domain that is in use for symbology. However, in the Data Dictionary, under Devices>Fire Hydrants>Fields> presentstatus, there is no associated domain and there is no associated domain for that subtype/field in the asset package, so it's not documented. I always worry about making assumptions on these like this for fear that Esri changes direction and I have to unwind things, which is why I was hoping Esri might weigh in.

Thanks, Gavin

ArcGIS Solutions Utilities Data Dictionary

[MichaelParma]

Ok, I see what you're saying now. In that data dictionary, the domain appears on water device, but not on hydrant.

-Mike

[GavinMcGhie]

Correct. And there is no domain associated in the AP, or the UN created from the AP, for that subtype/field, so the system only knows that it's an integer with no meaning beyond symbology.

cheers, Gavin

[MikeMillerGIS · Accepted solution]

That domain was used in previous versions, but was removed.  I will log an issue to get the map corrected

[GavinMcGhie]

Thanks for confirming the UN is moving away from that field/domain rather than towards it!