Add County Domain Values

[geofinne]

Add the list of County values into the domain.

Per the standard, the domain should be:
Restricted to the names of counties and county equivalents. For the US, a complete list is maintained by the US Census Bureau as ANSI INCITS 31:2009 [17] (Formerly FIPS 6-4) and the Domain is restricted to the exact listed values as published in ANSI INCITS 31:2009 [17], including casing and use of abbreviations.

[tomneer]

Adding County and Equivalents would create a domain containing several thousand records. General practice is for the GIS Data Provider to customize this domain to their organizational county(s) and surrounding counties. Documentation has been added about GIS Data Provider Specific Domains, their population and management.

However, if you feel this is something to discussion with the Data Model Template WG, we can add it to our next agenda.

[geofinne]

I think it's worth a discussion. If we don't add the values, it opens up the possibility for misspellings and incorrect formatting (e.g., "King" instead of the required "King County" format).

[jasonhorning]

We did discuss this in V1 and chose not to add the 3000+ US county values, and just left it up to the users to populate for their state or region. We did add this documentation to our readme in V1.

Domain Use Within the templates there are some domains that have no entries. These domains include AdditionalCode, AgencyID, County, ESN, PostalCode, PostalCommunityName and ServiceURI. The entity is expected to populate these domains, in accordance with guidelines specified within the NG9-1-1 GIS Data Model standard, based on the needs within their jurisdiction.

Consider that we'd also have to add all of the same values for MX and CA so there would likely be far more than 3k.

If you'd like to still have a conversation about it we can but that's the background.

[geofinne]

Good point for Mexico and Canada! I'm good with leaving the responsibility on the user(s).

[tomneer]

Per Working Group meeting [2022-12-21] due to the number of A3 domain values, it will be left to each organization to populate these values to keep this manageable.