nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Najděte více příspěvků označených jako

Accepted answers

MikeMillerGIS

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

All comments

OsvaldoDiaz

´´Hi Gavin, I faced a similar issue when standardizing my hidrant network (1,401 assets in panama´s Central Provinces). I found that the white dot´ visualization issue is often due to the lack of domain definitions in the presentstatus field during the initial data ingestion.´´

´´My approach to resolve this was :

1- Data Auditing : I cleaned the raw dataset in Excel, ensuring every hydrant had a verified status code before any migration.

2- Schema Enforcement : Instead of assigning random values, I mapped these cleaned records into a defined schema and published them using a Service Definition to enforce domain integrity.¨

3- Visualization : By ensuring the domain values in the Feature Layer matched the simbolization rules of the Water Utility Network, the white dots were eliminated, and all assets correctly reflected their operational status in my Web Maps. Hope this helps!¨

GavinMcGhie

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

MikeMillerGIS

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

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

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

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

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/DataDictionary/#Pipeline_Device_Status)

Hope this helps,
Mike Parma

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.