URN – urn:emergency:uid:gis
Layer Indicator – RCL
Local Unique ID – {AD873541-F41C-409E-A0BE- 1B0C583902A4}
Agency Identifier – co.polk.wi.us

URN – urn:emergency:uid:gis
Layer Indicator – SSAP
Local Unique ID – 100373182
Agency Identifier – waukeshacounty.gov

URN – urn:emergency:uid:gis
Layer Indicator – Ems
Local Unique ID – 55025{AD873541-F41C-409E-A0BE- 1B0C583902A4}
Agency Identifier – countyofdane.com

Name: RoadCenterLine
Layer Indicator: RCL

Name: SiteStructureAddressPoint
Layer Indicator: SSAP

Name: PsapPolygon
Layer Indicator: Psap

Name: PolicePolygon
Layer Indicator: Pol

Name: FirePolygon
Layer Indicator: Fire

Name: EmsPolygon
Layer Indicator: Ems

Name: ProvisioningPolygon
Layer Indicator: Prov

Name: StreetNameAliasTable
Layer Indicator: StrNA

Element Number: 3.1.1
Element Name: NENA Globally Unique ID
Database Field Name: NGUID
Field Type: TEXT
Field Width: 254
Inclusion: Yes
Domain:
Reference Standard: NENA

Database Field Name: NGUID
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
urn:emergency:uid:gis:RCL:47824393:co.polk.wi.us, urn:emergency:uid:gis:RCL:587392034:waukeshacounty.gov, urn:emergency:uid:gis:RCL:90a942e1bc7f4g1h94c5acaadv24r89h:countyofdane.com
Description:
The NENA Globally Unique ID (Primary Key) for each record in a GIS data layer. Each record in the GIS data layer MUST have a globally unique ID. When coalescing data from other local 9-1-1 Authorities into the ECRF and LVF, this unique ID MUST continue to have only one occurrence. Additional detail on how to construct the NGUID can be found in section 2.4 NENA Globally Unique IDs (NGUID).

Database Field Name: AdNumPre_L
Data Type: TEXT
Inclusion: Conditional
Width: 15
Domain:
Examples:
N123, W123, N, W, S123W
Description:
An extension of the Left FROM Address or Left TO Address on the left side of the road segment consisting of the non-integer portion of the identifier for a parcel, house, building or other feature which precedes the address number, as defined by the official Addressing Authority for the given jurisdiction. Used commonly in Wisconsin to include the directional to an address number (e.g., N2554 Johnson Street). Also used in a few counties where grid address numbers exist to include the locally-defined grid cell reference. In Wisconsin, this is typically only the two directionals and the number between them (e.g., W180N8085 Town Hall Road).

Database Field Name: FromAddr_L
Data Type: LONG
Inclusion: Yes
Width: 6
Domain: Whole numbers from 0 to 999999
Examples:
123
Description:
The beginning value of the address range on the left side of the road segment at the FROM node (begin point). This value can be higher than the Left TO Address.

East Main Street
Left FROM Address: 2
Left TO Address: 98
Right FROM Address: 1
Right TO Address: 99

West Main Street
Left FROM Address: 1
Left TO Address: 99
Right FROM Address: 2
Right TO Address: 98

Example of Left FROM, Left TO, Right FROM, and Right TO Addresses

Database Field Name: ToAddr_L
Data Type: LONG
Inclusion: Yes
Width: 6
Domain: Whole numbers from 0 to 999999
Examples:
123
Description:
The ending value of the address range on the left side of the road segment at the TO node (endpoint). This value can be lower than the Left FROM Address.

Database Field Name: AdNumPre_R
Data Type: TEXT
Inclusion: Conditional
Width: 15
Domain:
Examples:
N123, W123, N, W, S123W
Description:
An extension of the Right FROM Address or Right TO Address on the right side of the road segment, consisting of the non-integer portion of the identifier for a parcel, house, building or other feature which precedes the address number, as defined by the official Addressing Authority for the given jurisdiction. Used commonly in Wisconsin to include the directional to an address number (e.g., N2554 Johnson Street). Also used in a few counties where grid address numbers exist to include the locally-defined grid cell reference. In Wisconsin, this is typically only the two directionals and the number between them (e.g., W180N8085 Town Hall Road).

Database Field Name: FromAddr_R
Data Type: LONG
Inclusion: Yes
Width: 6
Domain: Whole numbers from 0 to 999999
Examples:
123
Description:
The beginning value of the address range on the right side of the road segment at the FROM node (begin point). This value can be higher than the Right TO Address.

Database Field Name: ToAddr_R
Data Type: LONG
Inclusion: Yes
Width: 6
Domain: Whole numbers from 0 to 999999
Examples:
123
Description:
The ending value of the address range on the right side of the road segment at the TO node (endpoint). This value can be lower than the Right FROM Address.

Database Field Name: St_PreMod
Data Type: TEXT
Inclusion: Conditional
Width: 15
Domain:
Examples:
Old North County Highway 12
Description:
A word or phrase that precedes all other Street Name elements and is separated from the Street Name element by a Street Name Pre Directional and/or a Street Name Pre Type element. Not commonly used and use should be minimized.

Database Field Name: St_PreDir
Data Type: TEXT
Inclusion: Conditional
Width: 10
Domain: WLIA DirectionDomain
Examples:
East Main Street, Old North County Highway 12
Description:
A word or phrase preceding the Street Name element that indicates the direction taken by the road from an arbitrary starting point or the sector where it is located.

Database Field Name: St_PreType
Data Type: TEXT
Inclusion: Conditional
Width: 50
Domain: NENA Street Name Pre Types and Street Name Post Types Registry
Examples:
Avenue A, Old North County Highway 12, United States Highway 151, State Highway 46, Interstate 90
Description:
A word or phrase that precedes the Street Name element and identifies the type of thoroughfare in the Full Street Name.

Database Field Name: St_PreSep
Data Type: TEXT
Inclusion: Conditional
Width: 20
Domain: NENA Street Name Pre Type Separators Registry
Examples:
Avenue of the Arts, Avenue of Champions
Description:
A preposition or prepositional phrase between the Street Name Pre Type and the Street Name element.

Database Field Name: St_Name
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
Jones Road, County Highway KP, Avenue of the Arts, Avenue C, Azure Court South
Description:
The official name of the road as defined by the official Street Naming Authority for the given jurisdiction. The Street Name element does not include a street type, directional, or modifier unless assigned as such by the official Street Naming Authority.

Database Field Name: St_PosTyp
Data Type: TEXT
Inclusion: Conditional
Width: 50
Domain: NENA Street Name Pre Types and Street Name Post Types Registry
Examples:
Jones Road, Azure Court South
Description:
A word or phrase that follows the Street Name element and identifies the type of thoroughfare in the Full Street Name.

Database Field Name: St_PosDir
Data Type: TEXT
Inclusion: Conditional
Width: 10
Domain: WLIA DirectionDomain
Examples:
Azure Court South, 10^th Avenue West
Description:
A word or phrase following the Street Name element that indicates the direction taken by the road from an arbitrary starting point or the sector where it is located.

Database Field Name: St_PosMod
Data Type: TEXT
Inclusion: Conditional
Width: 25
Domain:
Examples:
Bermuda Boulevard Lower, Lake Road Fire Road 8, Stoughton Road Frontage Road, Interstate 90 westbound
Description:
A word or phrase that follows all other Street Name elements and is separated from the Street Name element by a Street Name Post Directional and/or Street Name Post Type element. Not commonly used and use should be minimized.

Database Field Name: FullStNm
Data Type: TEXT
Inclusion: Yes
Width: 245
Domain:
Examples:
Old North County Highway 12, Azure Court South, Lake Road Fire Road 8
Description:
The Street Name with all Pre/Post Modifiers, Pre/Post Directionals, Pre Type Separator, and Pre/Post Types concatenated: St_PreMod + St_PreDir + St_PreTyp + St_PreSep + St_Name + St_PosTyp + St_PosDir + St_PosMod

Database Field Name: abFullStNm
Data Type: TEXT
Inclusion: No
Width: 175
Domain:
Examples:
Old N CTH 12, Azure Ct S, Lake Rd Fire Rd 8
Description:
The Full Street Name with abbreviations (where appropriate) used for the Pre/Post Modifiers, Pre/Post Types, and Pre/Post Directionals. This field is equivalent to the abFullStNm field in the WLIA Standard.

Database Field Name: LSt_PreDir
Data Type: TEXT
Inclusion: Conditional
Width: 2
Domain: WLIA abvDirectionDomain
Examples:
E MAIN ST, S ELMWOOD DR
Description:
The street direction prefix as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: LSt_Name
Data Type: TEXT
Inclusion: Conditional
Width: 75
Domain:
Examples:
E MAIN ST, S ELMWOOD DR, I 90, CTH U, 10TH AVE W, AZURE CT S
Description:
The street name field as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: LSt_Type
Data Type: TEXT
Inclusion: Conditional
Width: 4
Domain: PSAP MSAG; USPS Publication 28, Appendix C1 [9]
Examples:
E MAIN ST, S ELMWOOD DR, 10TH AVE W, AZURE CT S
Description:
The valid street type abbreviation as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: LSt_PosDir
Data Type: TEXT
Inclusion: Conditional
Width: 2
Domain: WLIA abvDirectionDomain
Examples:
10TH AVE W, AZURE CT S
Description:
The street direction suffix as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: PostCode_L
Data Type: TEXT
Inclusion: No
Width: 7
Domain: USPS City State File Product [10]
Examples:
53527
Description:
The 5-digit code on the left side of the road segment that identifies the individual US Post Office or metropolitan area delivery station associated with the addresses on that side of the road.

Database Field Name: PostCode_R
Data Type: TEXT
Inclusion: No
Width: 7
Domain: USPS City State File Product [10]
Examples:
53527
Description:
The 5-digit code on the right side of the road segment that identifies the individual US Post Office or metropolitan area delivery station associated with the addresses on that side of the road.

Database Field Name: PostComm_L
Data Type: TEXT
Inclusion: No
Width: 40
Domain: USPS City State File Product [10]
Examples:
Cottage Grove, Eau Claire, Minocqua, Harshaw
Description:
The name on the left side of the road segment recognized by the USPS as valid for the ZIP Code of the addresses on that side of the road.

Database Field Name: PostComm_R
Data Type: TEXT
Inclusion: No
Width: 40
Domain: USPS City State File Product [10]
Examples:
Cottage Grove, Eau Claire, Minocqua, Harshaw
Description:
The name on the right side of the road segment recognized by the USPS as valid for the ZIP Code of the addresses on that side of the road.

Database Field Name: Country_L
Data Type: TEXT
Inclusion: Yes
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-1 alpha-2 codes
Examples:
US, CA
Description:
The two-letter abbreviation of the Country on the left side of the road segment where the address is located. Must be in uppercase.

Database Field Name: Country_R
Data Type: TEXT
Inclusion: Yes
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-1 alpha-2 codes
Examples:
US, CA
Description:
The two-letter abbreviation of the Country on the right side of the road segment where the address is located. Must be in uppercase.

Database Field Name: State_L
Data Type: TEXT
Inclusion: Yes
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-2 WLIA FIPSStateDomain
Examples:
WI, IL, MN, MI
Description:
The two-letter abbreviation of the State on the left side of the road segment where the address is located. Must be in uppercase.

Database Field Name: State_R
Data Type: TEXT
Inclusion: Yes
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-2 WLIA FIPSStateDomain
Examples:
WI, IL, MN, MI
Description:
The two-letter abbreviation of the State on the right side of the road segment where the address is located. Must be in uppercase.

Database Field Name: County_L
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: Restricted to the values in ANSI INCITS 31:2009, including casing and abbreviations [11] NG911CountyDomain
Examples:
La Crosse County, Racine County
Description:
The name of the County on the left side of the road segment where the address is located.

Database Field Name: County_R
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: Restricted to the values in ANSI INCITS 31:2009, including casing and abbreviations [11] NG911CountyDomain
Examples:
La Crosse County, Racine County
Description:
The name of the County on the right side of the road segment where the address is located.

Database Field Name: IncMuni_L
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: WLIA FIPSMunicipalityDomain
Examples:
Town of Cottage Grove, City of Green Bay, Village of North Hudson
Description:
The name of the Incorporated Municipality on the left side of the road segment where the address is located, including the incorporated municipality type.

Database Field Name: IncMuni_R
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: WLIA FIPSMunicipalityDomain
Examples:
Town of Cottage Grove, City of Green Bay, Village of North Hudson
Description:
The name of the Incorporated Municipality on the right side of the road segment where the address is located, including the incorporated municipality type.

Database Field Name: UnincCom_L
Data Type: TEXT
Inclusion: No
Width: 100
Domain:
Examples:
Minocqua, Houlton, Gotham, Pray
Description:
The name of the Unincorporated Community on the left side of the road segment where the address is located.

Database Field Name: UnincCom_R
Data Type: TEXT
Inclusion: No
Width: 100
Domain:
Examples:
Minocqua, Houlton, Gotham, Pray
Description:
The name of the Unincorporated Community on the right side of the road segment where the address is located.

Database Field Name: NbrhdCom_L
Data Type: TEXT
Inclusion: No
Width: 100
Domain:
Examples:
Third Ward, Bassett, Greenbush
Description:
The name of an unincorporated neighborhood, subdivision, or area within an incorporated municipality on the left side of the road segment where the address point is located. Neighborhood communities are only used when they are known and have a clearly defined boundary.

Database Field Name: NbrhdCom_R
Data Type: TEXT
Inclusion: No
Width: 100
Domain:
Examples:
Third Ward, Bassett, Greenbush
Description:
The name of an unincorporated neighborhood, subdivision, or area within an incorporated municipality on the right side of the road segment where the address point is located. Neighborhood communities are only used when they are known and have a clearly defined boundary.

Database Field Name: AddCode_L
Data Type: TEXT
Inclusion: No
Width: 6
Domain:
Examples:
Description:
Note: Since this field is not applicable in the US, it will not be populated in WI GIS data layers. A Standard Geographical Classification code used in Canada that specifies a geographic area and is used to differentiate two municipalities with the same name in a province that does not have counties.

Database Field Name: AddCode_R
Data Type: TEXT
Inclusion: No
Width: 6
Domain:
Examples:
Description:
Note: Since this field is not applicable in the US, it will not be populated in WI GIS data layers. A Standard Geographical Classification code used in Canada that specifies a geographic area and is used to differentiate two municipalities with the same name in a province that does not have counties.

Database Field Name: OneWay
Data Type: TEXT
Inclusion: No
Width: 2
Domain: B, TF, FT
Examples:
B, FT, TF
Description:
The direction of traffic movement along a road in relation to the FROM node and TO node of the road segment where: B (Travel allowed in both directions) FT (One-way, travel from FROM node to TO node) TF (One-way, travel from TO node to FROM node)

East Main Street
One-Way: FT

West Main Street
One-Way: TF

Example of OneWay attribution

Database Field Name: SpeedLimit
Data Type: SHORT
Inclusion: No
Width: 3
Domain: WLIA SpeedLimitDomain
Examples:
10, 25, 30, 55, 65
Description:
The posted predominate speed limit of the road segment.

Database Field Name: RoadClass
Data Type: TEXT
Inclusion: No
Width: 24
Domain: Primary, Secondary, Local, Ramp, Service Drive, Vehicular Trail, Walkway/Pedestrian Trail, Stairway, Alley, Private, Parking Lot, Bike Path or Trail, Bridle Path, Other
Examples:
Primary, Secondary, Local, Ramp, Alley, Private, Trail
Description:
The general description of the type of road. These values are based on road classification definitions from the Census MAF/TIGER Feature Class Codes (MTFCC) at https://www.census.gov/library/reference/code-lists/mt-feature-class-codes.html.

• Primary roads are generally divided, limited-access highways within the interstate highway system or under state management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways.
• Secondary roads are main arteries, usually in the US Highway, State Highway, or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not be divided, and usually have at-grade intersections with many other roads and driveways.
• Local roads are generally a paved non-arterial street, road, or byway that usually has a single lane of traffic in each direction. Roads in this classification include neighborhood, rural roads, and city streets.
• Ramp designates a road that allows controlled access from adjacent roads onto a limited access highway, often in the form of a cloverleaf interchange. Ramps typically do not have address ranges.
• Service Drive provides access to structures along the highway, usually parallel to a limited access highway. If these roads are named and addressed, they may be considered local roads.
• Vehicular Trail (4WD, snowmobile) is an unpaved trail or path where a four-wheel-drive vehicle, snowmobile, or similar vehicle is required.
• Walkway/Pedestrian Trail is a path that is used for walking, being either too narrow for or legally restricted from vehicular traffic.
• Stairway is a pedestrian passageway from one level to another by a series of steps.
• Alley is generally a service road that does not generally have associated addressed structures and is usually unnamed. It is located at the rear of buildings and properties.
• Private (service vehicles, logging, oil fields, ranches, etc.) is a road within private property that is privately maintained for service, extractive, or other purposes. These roads are often unnamed.
• Parking Lot is the main travel route for vehicles through a paved parking area.
• Bike Path or Trail is a path that is used for manual or small, motorized bicycles, being either too narrow for or legally restricted from vehicular traffic.
• Bridle Path is a path that is used for horses, being either too narrow for or legally restricted from vehicular traffic.
• Other is any road or path type that does not fit into the above categories.

Database Field Name: FrElev
Data Type: SHORT
Inclusion: No
Width:
Domain: WLIA ElevationDomain
Examples:
0, 1, 2
Description:
Identifies the From routing for intersections and overpasses. Base elevation = 0.

Database Field Name: ToElev
Data Type: SHORT
Inclusion: No
Width:
Domain: WLIA ElevationDomain
Examples:
0, 1, 2
Description:
Identifies the To routing for intersections and overpasses. Base elevation = 0.

Database Field Name: DateUpdate
Data Type: DATE
Inclusion: Yes
Width:
Domain:
Examples:
2020-01-28T15:47.09.3-06:00 (representing a record updated on January 28, 2020 at 3:47 and 9.3 seconds PM US Central Standard Time, with a precision of .1 second); 2020-07-16T08:31:15.2-05:00 (representing a record updated on July 16, 2020 at 8:31 and 15.2 seconds AM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record was created or last modified.

Database Field Name: Effective
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will become active on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will become active on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record is scheduled to take effect (e.g., the date and time an annexation takes effect and a copy of the road centerlines within the annexed area that have had their Incorporated Municipality, ESN, and MSAG Community Name fields populated with the new values are recognized for use in the NG9-1-1 system).

Database Field Name: Expire
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will expire and no longer be valid on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will expire and no longer be valid on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time when the information in the record is no longer considered valid (e.g., the date and time an annexation takes effect and the road centerlines within the annexed area that have their Incorporated Municipality, ESN, and MSAG Community Name fields populated with the former values are no longer recognized for use in the NG9-1-1 system).

Database Field Name: DiscrpAgID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain:
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
Agency that receives a Discrepancy Report (DR), should a discrepancy in the GIS data be discovered, and will take responsibility for ensuring discrepancy resolution. This may or may not be the same as the 9-1-1 Authority. This MUST be represented by a domain name that is an Agency Identifier as defined in the NENA Master Glossary of 9-1-1 Terminology, NENA-ADM-000.23-2020 [21].

Database Field Name: Parity_L
Data Type: TEXT
Inclusion: Yes
Width: 1
Domain: O, E, B, Z
Examples:
O, E, B, Z
Description:
The even or odd property of the address number range on the left side of the road segment relative to the FROM Node where: O (only Odd addresses in the address range) E (only Even addresses in the address range) B (Both Even and Odd addresses in the address range) Z (Address Range is 0-0)

Database Field Name: Parity_R
Data Type: TEXT
Inclusion: Yes
Width: 1
Domain: O, E, B, Z
Examples:
O, E, B, Z
Description:
The even or odd property of the address number range on the right side of the road segment relative to the FROM Node where: O (only Odd addresses in the address range) E (only Even addresses in the address range) B (Both Even and Odd addresses in the address range) Z (Address Range is 0-0)

Database Field Name: ESN_L
Data Type: TEXT
Inclusion: Conditional
Width: 5
Domain: Characters from 000 to 99999
Examples:
35, 810, 7115
Description:
A 3-5 character alphanumeric string that represents the Emergency Service Zone (ESZ) on the left side of the road segment relative to the FROM Node. ESZ is used for 10-digit routing in Legacy Systems and is not used in a full NG9-1-1 implementation.

Database Field Name: ESN_R
Data Type: TEXT
Inclusion: Conditional
Width: 5
Domain: Characters from 000 to 99999
Examples:
35, 810, 7115
Description:
A 3-5 character alphanumeric string that represents the Emergency Service Zone (ESZ) on the right side of the road segment relative to the FROM Node. ESZ is used for 10-digit routing in Legacy Systems and is not used in a full NG9-1-1 implementation.

Database Field Name: MSAGComm_L
Data Type: TEXT
Inclusion: Conditional
Width: 30
Domain:
Examples:
MADISON, MAYVILLE, REDGRANITE
Description:
The Community name on the left side of the road segment relative to the FROM Node, as it appears in the MSAG. This may or may not be the same as the Postal Community Name used by the US Postal Service.

Database Field Name: MSAGComm_R
Data Type: TEXT
Inclusion: Conditional
Width: 30
Domain:
Examples:
MADISON, MAYVILLE, REDGRANITE
Description:
The Community name on the right side of the road segment relative to the FROM Node, as it appears in the MSAG. This may or may not be the same as the Postal Community Name used by the US Postal Service.

Database Field Name: Valid_L
Data Type: TEXT
Inclusion: No
Width: 1
Domain: WLIA YesNoDomain
Examples:
Y, N
Description:
Indicates if the address range on the left side of the road segment should be used for civic location validation. A value of “Y” means the Road Centerline layer can be used for address validation and therefore any Address Number within the address range on the left side of the road segment should be considered by the LVF to be valid. A value of “N” means the Road Centerline layer should not be used for validation and an Address Number within the address range on the left side of the road segment should only be validated using the Site/Structure Address Point layer. If no values are populated, a value of “Y” is assumed.

Database Field Name: Valid_R
Data Type: TEXT
Inclusion: No
Width: 1
Domain: WLIA YesNoDomain
Examples:
Y, N
Description:
Indicates if the address range on the right side of the road segment should be used for civic location validation. A value of “Y” means the Road Centerline layer can be used for address validation and therefore any Address Number within the address range on the right side of the road segment should be considered by the LVF to be valid. A value of “N” means the Road Centerline layer should not be used for validation and an Address Number within the address range on the right side of the road segment should only be validated using the Site/Structure Address Point layer. If no values are populated, a value of “Y” is assumed.

Database Field Name: Exception
Data Type: TEXT
Inclusion: Conditional
Width: 75
Domain: GMS, NGCS
Examples:
999, 401, OAB
Description:
Indicates if the segment is an exception. 999 is a global exception code that will remove the feature from being provisioned to the NG9-1-1 Core Service providers system.

Database Field Name: NGUID
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
urn:emergency:uid:gis:SSAP:17342239:co.polk.wi.us, urn:emergency:uid:gis:SSAP:100373182:waukeshacounty.gov, urn:emergency:uid:gis:SSAP:44f161f2jk7f4g1v45b1hgaw71av189c:countyofdane.co m
Description:
The NENA Globally Unique ID (Primary Key) for each record in a GIS data layer. Each record in the GIS data layer MUST have a globally unique ID. When coalescing data from other local 9-1-1 Authorities into the ECRF and LVF, this unique ID MUST continue to have only one occurrence. Additional details on how to construct the NGUID can be found in section 2.4 NENA Globally Unique IDs (NGUID). The locally assigned unique ID may be the SAP_ExtID (WLIA Standard), an autogenerated unique ID, or a manually generated unique ID.

Database Field Name: RCL_NGUID
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
urn:emergency:uid:gis:RCL:47824393:co.polk.wi.us, urn:emergency:uid:gis:RCL:587392034:waukeshacounty.gov, urn:emergency:uid:gis:RCL:90a942e1bc7f4g1h94c5acaadv24r89h:countyofdane.com
Description:
The Road Centerline NENA Globally Unique ID (RCL_NGUID) is used in the StreetNameAliasTable and SiteStructureAddressPoint as a foreign key relationship between the StreetNameAliasTable and the RoadCenterLine layer or the SiteStructureAddressPoint and the RoadCenterLine layer. A foreign key acts as a cross-reference between RCL_NGUID field in the StreetNameAliasTable and SiteStructureAddressPoint because it references the NGUID field primary key in the RoadCenterLine layer, thereby establishing a link between them. A RoadCenterLine record may have zero to many (0:M) StreetNameAliasTable records and SiteStructureAddressPoint features. Without this relationship, it would not be possible to identify any street name aliases of a road centerline. The values in the RCL_NGUID field MUST exist in the values of the NGUID field in the RoadCenterLine layer.

Database Field Name: AddNum_Pre
Data Type: TEXT
Inclusion: Conditional
Width: 15
Domain:
Examples:
N123, W123, N, W, S123W
Description:
The non-integer portion of the identifier for a parcel, house, building or other feature which precedes the address number, as defined by the official Addressing Authority for the given jurisdiction. Used commonly in Wisconsin to include the directional to an address number (e.g., N2554 Johnson Street). Also used in a few counties where grid address numbers exist to include the locally-defined grid cell reference. In Wisconsin, this is typically only the two directionals and the number between them (e.g., W180N8085 Town Hall Road).

Database Field Name: Add_Number
Data Type: LONG
Inclusion: Conditional
Width: 6
Domain: Whole numbers from 0 to 999999
Examples:
123, 10546
Description:
The numeric identifier for a parcel, house, building or other feature, as defined by the official Addressing Authority for a given jurisdiction.

Database Field Name: AddNum_Suf
Data Type: TEXT
Inclusion: Conditional
Width: 15
Domain:
Examples:
A, 1/2
Description:
The non-integer portion of the identifier for a parcel, house, building or other feature which follows the address number, as defined by the official Addressing Authority for a given jurisdiction. Not commonly used and use should be minimized. Not to be confused with Unit divisions within a building.

Database Field Name: LandmkName
Data Type: TEXT
Inclusion: Conditional
Width: 150
Domain:
Examples:
Lambeau Field, Camp Randall Stadium, Devil’s Lake, Gibraltar Rock, Pop’s Cave, Grand Dad’s Bluff
Description:
The name by which a prominent site or structure is publicly known and which may or may not be associated with a civic address. Note: This element may be impacted by a potential future change in NENA Standards. See Section 9 for more information.

Database Field Name: MilePost
Data Type: TEXT
Inclusion: Conditional
Width: 150
Domain:
Examples:
Mile Marker 284.8, MIN10
Description:
A measured distance travelled along a road, highway, trail, navigable waterway, or other unaddressed route, from a given point, that is typically posted with a milepost sign, a mile marker sign, or other marker. Mile Post numbers may be used in place of, or in addition to, Address Numbers.

Database Field Name: Building
Data Type: TEXT
Inclusion: No
Width: 75
Domain:
Examples:
Building 1, Building 2, Tower A, Tower B
Description:
The type (e.g., Building, Tower) and identifier (e.g., 2, B) for a building among a group of buildings that have the same Address Number and Full Street Name. Note: This element may be impacted by a potential future change in NENA Standards. See Section 9 for more information.

Database Field Name: Floor
Data Type: TEXT
Inclusion: No
Width: 75
Domain:
Examples:
Floor 4, First Floor, 11, Mezzanine
Description:
The floor, story, or level within a building.

Database Field Name: Unit_PreType
Data Type: TEXT
Inclusion: No
Width: 75
Domain:
Examples:
Suite, Apartment, Unit
Description:
Part of the complete unit identifier that precedes the Unit Value and indicates the kind of unit.

Database Field Name: Unit_Value
Data Type: TEXT
Inclusion: No
Width: 75
Domain:
Examples:
2102, 3C, 12, Penthouse
Description:
Part of the complete unit identifier that uniquely identifies a particular unit.

Database Field Name: Room
Data Type: TEXT
Inclusion: No
Width: 75
Domain:
Examples:
Room 101A, 1202, E, Capitol Ballroom
Description:
The name or identifier of a single room within a building.

Database Field Name: Seat
Data Type: TEXT
Inclusion: No
Width: 75
Domain:
Examples:
1, 2, A, B, Registration Desk, Cubicle D6
Description:
An individual seat location.

Database Field Name: Addtl_Loc
Data Type: TEXT
Inclusion: No
Width: 225
Domain:
Examples:
Concourse B; Gate C14; Loading Dock 2B, Stairwell D
Description:
The type and identifier for a part of a subaddress that is not a Building, Floor, Unit, Room, or Seat.

Database Field Name: St_PreMod
Data Type: TEXT
Inclusion: Conditional
Width: 15
Domain:
Examples:
Old North County Highway 12
Description:
A word or phrase that precedes all other Street Name elements and is separated from the Street Name element by a Street Name Pre Directional and/or a Street Name Pre Type element. Not commonly used and use should be minimized.

Database Field Name: St_PreDir
Data Type: TEXT
Inclusion: Conditional
Width: 10
Domain: WLIA DirectionDomain
Examples:
East Main Street, Old North County Highway 12
Description:
A word or phrase preceding the Street Name element that indicates the direction taken by the road from an arbitrary starting point or the sector where it is located.

Database Field Name: St_PreTyp
Data Type: TEXT
Inclusion: Conditional
Width: 50
Domain: NENA Street Name Pre Types and Street Name Post Types Registry
Examples:
Avenue A, Old North County Highway 12, United States Highway 151, State Highway 46, Interstate 90
Description:
A word or phrase that precedes the Street Name element and identifies the type of thoroughfare in the Full Street Name.

Database Field Name: St_PreSep
Data Type: TEXT
Inclusion: Conditional
Width: 20
Domain: NENA Street Name Pre Type Separators Registry
Examples:
Avenue of the Arts, Avenue of Champions
Description:
A preposition or prepositional phrase between the Street Name Pre Type and the Street Name element.

Database Field Name: St_Name
Data Type: TEXT
Inclusion: Conditional
Width: 254
Domain:
Examples:
Jones Road, County Highway KP, Avenue of the Arts, Avenue C, Azure Court South
Description:
The official name of the road as defined by the official Street Naming Authority for the given jurisdiction. The Street Name element does not include a street type, directional, or modifier unless assigned as such by the official Street Naming Authority.

Database Field Name: St_PosTyp
Data Type: TEXT
Inclusion: Conditional
Width: 50
Domain: NENA Street Name Pre Types and Street Name Post Types Registry
Examples:
Jones Road, Azure Court South
Description:
A word or phrase that follows the Street Name element and identifies the type of thoroughfare in the Full Street Name.

Database Field Name: St_PosDir
Data Type: TEXT
Inclusion: Conditional
Width: 10
Domain: WLIA DirectionDomain
Examples:
Azure Court South, 10^th Avenue West
Description:
A word or phrase following the Street Name element that indicates the direction taken by the road from an arbitrary starting point or the sector where it is located.

Database Field Name: St_PosMod
Data Type: TEXT
Inclusion: Conditional
Width: 25
Domain:
Examples:
Bermuda Boulevard Lower, Lake Road Fire Road 8, Stoughton Road Frontage Road, Interstate 90 westbound
Description:
A word or phrase that follows all other Street Name elements and is separated from the Street Name element by a Street Name Post Directional and/or Street Name Post Type element. Not commonly used and use should be minimized.

Database Field Name: FullStNm
Data Type: TEXT
Inclusion: Yes
Width: 245
Domain:
Examples:
Old North County Highway 12, Azure Court South, Lake Road Fire Road 8
Description:
The Street Name with all Pre/Post Modifiers, Pre/Post Directionals, Pre Type Separator, and Pre/Post Types concatenated: St_PreMod + St_PreDir + St_PreTyp + St_PreSep + St_Name + St_PosTyp + St_PosDir + St_PosMod

Database Field Name: abFullStNm
Data Type: TEXT
Inclusion: No
Width: 175
Domain:
Examples:
Old N CTH 12, Azure Ct S, Lake Rd Fire Rd 8
Description:
The Full Street Name with abbreviations (where appropriate) used for the Pre/Post Modifiers, Pre/Post Types, and Pre/Post Directionals. This field is equivalent to the abFullStNm field in the WLIA Standard.

Database Field Name: LSt_PreDir
Data Type: TEXT
Inclusion: Conditional
Width: 2
Domain: WLIA abvDirectionDomain
Examples:
E MAIN ST, S ELMWOOD DR
Description:
The street direction prefix as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: LSt_Name
Data Type: TEXT
Inclusion: Conditional
Width: 75
Domain:
Examples:
E MAIN ST, S ELMWOOD DR, I 90, CTH U, 10TH AVE W, AZURE CT S
Description:
The street name field as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: LSt_Type
Data Type: TEXT
Inclusion: Conditional
Width: 4
Domain: PSAP MSAG; USPS Publication 28, Appendix C1 [9]
Examples:
E MAIN ST, S ELMWOOD DR, 10TH AVE W, AZURE CT S
Description:
The valid street type abbreviation as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: LSt_PosDir
Data Type: TEXT
Inclusion: Conditional
Width: 2
Domain: WLIA abvDirectionDomain
Examples:
10TH AVE W, AZURE CT S
Description:
The street direction suffix as it appears in the MSAG, as assigned by the official Street Naming Authority. Casing should reflect what appears in the MSAG data.

Database Field Name: Post_Code
Data Type: TEXT
Inclusion: No
Width: 7
Domain: USPS City State File Product [10]
Examples:
53527, 54703
Description:
The 5-digit code that identifies the individual US Post Office or metropolitan area delivery station associated with an address.

Database Field Name: Post_Code4
Data Type: TEXT
Inclusion: No
Width: 4
Domain: USPS City State File Product [10]
Examples:
9675, 2871
Description:
A system of 4-digit codes that are used after the 5-digit Postal Code to specify a range of USPS delivery addresses.

Database Field Name: Post_Comm
Data Type: TEXT
Inclusion: No
Width: 40
Domain: USPS City State File Product [10]
Examples:
Cottage Grove, Eau Claire
Description:
The municipal name recognized by the USPS as valid for the ZIP Code of an address.

Database Field Name: Country
Data Type: TEXT
Inclusion: Yes
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-1 alpha-2 codes
Examples:
US, CA
Description:
The two-letter abbreviation of the Country where the address is located. Must be in uppercase.

Database Field Name: State
Data Type: TEXT
Inclusion: Yes
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-2 WLIA FIPSStateDomain
Examples:
WI, IL, MN, MI
Description:
The two-letter abbreviation of the State where the address is located. Must be in uppercase.

Database Field Name: County
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: Restricted to the values in ANSI INCITS 31:2009, including casing and abbreviations [11] NG911CountyDomain
Examples:
La Crosse County, Racine County
Description:
The name of the County where the address is located.

Database Field Name: Inc_Muni
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: WLIA FIPSMunicipalityDomain
Examples:
Town of Cottage Grove, City of Green Bay, Village of North Hudson
Description:
The name of the Incorporated Municipality where the address is located, including the incorporated municipality type.

Database Field Name: Uninc_Comm
Data Type: TEXT
Inclusion: No
Width: 100
Domain:
Examples:
Minocqua, Houlton, Gotham, Pray
Description:
The name of the Unincorporated Community where the address is located.

Database Field Name: Nbrhd_Comm
Data Type: TEXT
Inclusion: No
Width: 100
Domain:
Examples:
Third Ward, Bassett, Greenbush
Description:
The name of an unincorporated neighborhood, subdivision, or area within an incorporated municipality where the address is located. Neighborhood communities are only used when they are known and have a clearly defined boundary.

Database Field Name: AddCode
Data Type: TEXT
Inclusion: No
Width: 6
Domain:
Examples:
Description:
Note: Since this field is not applicable in the US, it will not be populated in WI GIS data layers. A Standard Geographical Classification code used in Canada that specifies a geographic area and is used to differentiate two municipalities with the same name in a province that does not have counties.

Database Field Name: Placement
Data Type: TEXT
Inclusion: No
Width: 25
Domain: NENA Site/Structure Address Point Placement Method Registry
Examples:
Geocoding, Parcel, PropertyAccess, Site, Structure, Unknown
Description:
The methodology used for placement of the address point.

Database Field Name: Place_Type
Data Type: TEXT
Inclusion: No
Width: 50
Domain: Restricted to the values in RFC 4589 [12]
Examples:
Airport, bank, hotel, office, residence, stadium, store
Description:
The type of feature identified by the address.

Database Field Name: AddDataURI
Data Type: TEXT
Inclusion: Conditional
Width: 254
Domain:
Examples:
https://addtl12345.example.com
Description:
A Uniform Resource Identifier (URI) that defines the Service URI for accessing additional data and information associated with the address location, including building information (e.g., blueprints, contact info, floor plans).

Database Field Name: Structure
Data Type: TEXT
Inclusion: Conditional
Width: 3
Domain: WLIA YesNoDomain
Examples:
Yes, No
Description:
Indicates if the address point is associated with a structure.

Database Field Name: DateUpdate
Data Type: DATE
Inclusion: Yes
Width:
Domain:
Examples:
2020-01-28T15:47.09.3-06:00 (representing a record updated on January 28, 2020 at 3:47 and 9.3 seconds PM US Central Standard Time, with a precision of .1 second); 2020-07-16T08:31:15.2-05:00 (representing a record updated on July 16, 2020 at 8:31 and 15.2 seconds AM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record was created or last modified.

Database Field Name: Effective
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will become active on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will become active on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record is scheduled to take effect (e.g., the date and time an annexation takes effect and a copy of the Site/Structure Address Points within the annexed area that have had their Incorporated Municipality, ESN, and MSAG Community Name fields populated with the new values are recognized for use in the NG9 1 1 system).

Database Field Name: Expire
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will expire and no longer be valid on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will expire and no longer be valid on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time when the information in the record is no longer considered valid (e.g., the date and time an annexation takes effect and the Site/Structure Address Points within the annexed area that have their Incorporated Municipality, ESN, and MSAG Community Name fields populated with the former values are no longer recognized for use in the NG9-1-1 system).

Database Field Name: DiscrpAgID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain:
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
Agency that receives a Discrepancy Report (DR), should a discrepancy in the GIS data be discovered, and will take responsibility for ensuring discrepancy resolution. This may or may not be the same as the 9-1-1 Authority. This MUST be represented by a domain name that is an Agency Identifier as defined in the NENA Master Glossary of 9-1-1 Terminology, NENA-ADM-000.23.2020 [21].

Database Field Name: ESN
Data Type: TEXT
Inclusion: Conditional
Width: 5
Domain: Characters from 000 to 99999
Examples:
35, 810, 7115
Description:
A 3 to 5 character alphanumeric string that represents the Emergency Service Zone (ESZ) where the address is located.

Database Field Name: MSAGComm
Data Type: TEXT
Inclusion: Conditional
Width: 30
Domain:
Examples:
MADISON, MAYVILLE, REDGRANITE
Description:
The Community name where the address is located, as it appears in the MSAG. This may or may not be the same as the Postal Community Name used by the US Postal Service.

Database Field Name: Lat
Data Type: FLOAT
Inclusion: No
Width:
Domain: +90 degrees to -90 degrees
Examples:
43.075450
Description:
The angular distance of the address point location north or south of the equator as defined by the coordinate system, expressed in decimal degrees.

Database Field Name: Long
Data Type: FLOAT
Inclusion: No
Width:
Domain: -180 degrees to +180 degrees
Examples:
-89.385161
Description:
The angular distance of the address point location east or west of the prime meridian of the coordinate system, expressed in decimal degrees.

Database Field Name: Elev
Data Type: LONG
Inclusion: No
Width: 6
Domain: Whole numbers from 0 to 999999
Examples:
68, 136
Description:
The WGS84 (GPS) elevation, given in meters above the ellipsoid, associated with the address.

Database Field Name: Exception
Data Type: TEXT
Inclusion: Conditional
Width: 75
Domain: GMS, NGCS
Examples:
999, 401, OAB
Description:
Indicates if the segment is an exception. 999 is a global exception code that will remove the feature from being provisioned to the NG9-1-1 Core Service providers system.

Database Field Name: NGUID
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
urn:emergency:uid:gis:Psap:57311256:co.polk.wi.us, urn:emergency:uid:gis:Psap:410371581:waukeshacounty.gov, urn:emergency:uid:gis:Psap:45a133f2jm7f2g5n41b1hjpw18ay583t:countyofdane.com
Description:
The NENA Globally Unique ID (Primary Key) for each record in a GIS data layer. Each record in the GIS data layer MUST have a globally unique ID. When coalescing data from other local 9-1-1 Authorities into the ECRF and LVF, this unique ID MUST continue to have only one occurrence. Additional detail on how to construct the NGUID can be found in section 2.4 NENA Globally Unique IDs (NGUID).

Database Field Name: Country
Data Type: TEXT
Inclusion: No
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-1 alpha-2 codes
Examples:
US, CA
Description:
The two-letter abbreviation of the Country where the polygon is located. Must be in uppercase.

Database Field Name: State
Data Type: TEXT
Inclusion: No
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-2 WLIA FIPSStateDomain
Examples:
WI, IL, MN, MI
Description:
The two-letter abbreviation of the State where the address is located. Must be in uppercase.

Database Field Name: Agency_ID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: Must be a registered domain name
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
A Domain Name System (DNS) registered domain name which is used to uniquely identify an agency. An agency is represented by a domain name as defined in Internet Engineering Task Force (IETF) RFC 1034 [6]. Each agency MUST use one domain name consistently in order to correlate actions across a wide range of calls and incidents. Any domain name in the public DNS is acceptable so long as each distinct agency uses a different domain name to ensure that each agency ID is globally unique.

Database Field Name: ServiceURI
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain: Must be a registered domain name
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
The Uniform Resource Identifier (URI) used for call routing that defines the URI of the specific service. The URI is usually a Session Initiation Protocol (SIP or SIPs) URI but may be a telephone number (e.g., tel) URI that defines the route to reach the service. Internet Engineering Task Force (IETF) RFC 1035 [13] defines the process to register a domain name

Database Field Name: ServiceURN
Data Type: TEXT
Inclusion: Yes
Width: 55
Domain: NENA urn:emergency:service:responder Registry
Examples:
urn:emergency:service:sos.psap; urn: emergency:service:responder.police; urn: emergency:service:responder.fire; urn: emergency:service:responder.ems
Description:
The Uniform Resource Name (URN) used to select the service for which a route is desired. The ECRF is queried with a location and a Service URN, and then returns the Service URI. NOTE: Spatial Interface providers may auto populate the Service URN based on their system requirements.

Database Field Name: ServiceNum
Data Type: TEXT
Inclusion: No
Width: 15
Domain: A dialable number or dial string
Examples:
911, 18002221212
Description:
The numbers that would be dialed on a 12 digit keypad to reach the emergency service appropriate for the location. This is not the same as an Emergency Service Number (ESN) in Legacy E9-1-1 systems. This field is used for all Emergency Boundaries including PSAP; Law; Fire; EMS; and others such as Poison Control. Within the United States the Service Number for most emergency services is 9-1-1, however, there may be Emergency Service boundaries that have a different number that may be associated with them such as Poison Control.

Database Field Name: AVcard_URI
Data Type: TEXT
Inclusion: No
Width: 254
Domain:
Examples:
https://vcard.psap.allegheny.pa.us; https://vcard.houstontx.gov/fire
Description:
The numbers that would be dialed on a 12 digit keypad to reach the emergency service appropriate for the location. This is not the same as an Emergency Service Number (ESN) in Legacy E9-1-1 systems. This field is used for all Emergency Boundaries including PSAP; Law; Fire; EMS; and others such as Poison Control. Within the United States the Service Number for most emergency services is 9-1-1, however, there may be Emergency Service boundaries that have a different number that may be associated with them such as Poison Control.

Database Field Name: DsplayName
Data Type: TEXT
Inclusion: Yes
Width: 60
Domain:
Examples:
New York Police Department, Med Life Ambulance Services, Houston FD
Description:
A name or description of the entity offering emergency services within a PSAP or Emergency Service Boundary. This value must be suitable for display.

Database Field Name: DateUpdate
Data Type: DATE
Inclusion: Yes
Width:
Domain:
Examples:
2020-01-28T15:47.09.3-06:00 (representing a record updated on January 28, 2020 at 3:47 and 9.3 seconds PM US Central Standard Time, with a precision of .1 second); 2020-07-16T08:31:15.2-05:00 (representing a record updated on July 16, 2020 at 8:31 and 15.2 seconds AM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record was created or last modified.

Database Field Name: Effective
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will become active on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will become active on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record is scheduled to take effect (e.g., the date and time an annexation takes effect and the new PSAP Boundary is recognized for use in the NG9-1-1 system).

Database Field Name: Expire
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will expire and no longer be valid on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will expire and no longer be valid on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time when the information in the record is no longer considered valid (e.g., the date and time an annexation takes effect and the former PSAP Boundary is no longer recognized for use in the NG9-1-1 system).

Database Field Name: DiscrpAgID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain:
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
Agency that receives a Discrepancy Report (DR), should a discrepancy be discovered in the GIS data, and will take responsibility for ensuring discrepancy resolution. This may or may not be the same as the 9-1-1 Authority. This MUST be represented by a domain name that is an Agency Identifier as defined in the NENA Master Glossary of 9-1-1 Terminology, NENA-ADM-000.23-2020 [21].

Database Field Name: Exception
Data Type: TEXT
Inclusion: Conditional
Width: 75
Domain: GMS, NGCS
Examples:
999, 401, OAB
Description:
Indicates if the segment is an exception. 999 is a global exception code that will remove the feature from being provisioned to the NG9-1-1 Core Service providers system.

Database Field Name: NGUID
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
urn:emergency:uid:gis:Pol:71378233:co.polk.wi.us, urn:emergency:uid:gis:Fire:617271786:waukeshacounty.gov, urn:emergency:uid:gis:Ems:54a513f2kk7g5h7n41b0hxwa81jw531c:countyofdane.com
Description:
The NENA Globally Unique ID (Primary Key) for each record in a GIS data layer. Each record in the GIS data layer MUST have a globally unique ID. When coalescing data from other local 9-1-1 Authorities into the ECRF and LVF, this unique ID MUST continue to have only one occurrence. Additional detail on how to construct the NGUID can be found in section 2.4 NENA Globally Unique IDs (NGUID).

Database Field Name: Country
Data Type: TEXT
Inclusion: No
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-1 alpha-2 codes
Examples:
US, CA
Description:
The two-letter abbreviation of the Country where the polygon is located. Must be in uppercase.

Database Field Name: State
Data Type: TEXT
Inclusion: No
Width: 2
Domain: Restricted to the two-letter codes in ISO 3166-2 WLIA FIPSStateDomain
Examples:
WI, IL, MN, MI
Description:
The two letter abbreviation of the State where the polygon is located. Must be in uppercase.

Database Field Name: Agency_ID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain: Must be a registered domain name
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
A Domain Name System (DNS) registered domain name which is used to uniquely identify an agency. An agency is represented by a domain name as defined in Internet Engineering Task Force (IETF) RFC 1034 [15]. Each agency MUST use one domain name consistently in order to correlate actions across a wide range of calls and incidents. Any domain name in the public DNS is acceptable so long as each distinct agency uses a different domain name to ensure that each agency ID is globally unique.

Database Field Name: ServiceURI
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain: Must be a registered domain name
Examples:
sips:sos@psap.columbus.oh.us; tel:+16145551212
Description:
The Uniform Resource Identifier (URI) used for call routing that defines the URI of the specific service. The URI is usually a Session Initiation Protocol (SIP or SIPs) URI but may be a telephone number (e.g., tel) URI that defines the route to reach the service. Internet Engineering Task Force (IETF) RFC 1035 [13] defines the process to register a domain name

Database Field Name: ServiceURN
Data Type: TEXT
Inclusion: Yes
Width: 55
Domain: NENA urn:emergency:service:responder Registry
Examples:
urn:emergency:service:sos.psap; urn: emergency:service:responder.police; urn: emergency:service:responder.fire; urn: emergency:service:responder.ems
Description:
The Uniform Resource Name (URN) used to select the service for which a route is desired. The ECRF is queried with a location and a Service URN, and then returns the Service URI. NOTE: Spatial Interface providers may auto populate the Service URN based on their system requirements.

Database Field Name: ServiceNum
Data Type: TEXT
Inclusion: No
Width: 15
Domain: A dialable number or dial string
Examples:
911, 18002221212
Description:
The numbers that would be dialed on a 12 digit keypad to reach the emergency service appropriate for the location. This is not the same as an Emergency Service Number (ESN) in Legacy E9-1-1 systems. This field is used for all Emergency Boundaries including PSAP; Law; Fire; EMS; and others such as Poison Control. Within the United States the Service Number for most emergency services is 9-1-1, however, there may be Emergency Service boundaries that have a different number that may be associated with them such as Poison Control.

Database Field Name: AVcard_URI
Data Type: TEXT
Inclusion: No
Width: 254
Domain:
Examples:
https://vcard.psap.allegheny.pa.us; https://vcard.houstontx.gov/fire
Description:
Note: This field will be considered for deletion in a future version of this document to align with future changes in the NENA NG911 GIS Data Model. A vCard is a file format standard for electronic business cards. The Agency vCard URI is the internet address of a JavaScript Object Notation (JSON) data structure which contains contact information (Name of Agency, Contact phone numbers, etc.) in the form of a jCard (RFC 7095) [14]. The vCard URI is used in the service boundary layers to provide contact information for each agency. The Service/Agency Locator (see NENA STA-010.3e-2021 [16]) will provide these URIs for agencies listed within it. NOTE: Spatial Interface providers may auto populate the Agency vCard URI based on their system requirements.

Database Field Name: DisplayName
Data Type: TEXT
Inclusion: Yes
Width: 60
Domain:
Examples:
New York Police Department, Med Life Ambulance Services, Houston FD
Description:
A name or description of the entity offering emergency services within a PSAP or Emergency Service Boundary. This value must be suitable for display.

Database Field Name: DateUpdate
Data Type: DATE
Inclusion: Yes
Width:
Domain:
Examples:
2020-01-28T15:47.09.3-06:00 (representing a record updated on January 28, 2020 at 3:47 and 9.3 seconds PM US Central Standard Time, with a precision of .1 second); 2020-07-16T08:31:15.2-05:00 (representing a record updated on July 16, 2020 at 8:31 and 15.2 seconds AM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record was created or last modified.

Database Field Name: Effective
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will become active on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will become active on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record is scheduled to take effect (e.g., the date and time an annexation takes effect and the new Emergency Service Boundary is recognized for use in the NG9-1-1 system).

Database Field Name: Expire
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will expire and no longer be valid on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will expire and no longer be valid on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time when the information in the record is no longer considered valid (e.g., the date and time an annexation takes effect and the former Emergency Service Boundary is no longer recognized for use in the NG9-1-1 system).

Database Field Name: DiscrpAgID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain:
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
Agency that receives a Discrepancy Report (DR), should a discrepancy be discovered in the GIS data, and will take responsibility for ensuring discrepancy resolution. This may or may not be the same as the 9-1-1 Authority. This MUST be represented by a domain name that is an Agency Identifier as defined in the NENA Master Glossary of 9-1-1 Terminology, NENA-ADM-000.23-2020 [21].

Database Field Name: Exception
Data Type: TEXT
Inclusion: Conditional
Width: 100
Domain: GMS, NGCS
Examples:
999, 401, OAB
Description:
Indicates if the segment is an exception. 999 is a global exception code that will remove the feature from being provisioned to the NG9-1-1 Core Service providers system.

Database Field Name: NGUID
Data Type: TEXT
Inclusion: Yes
Width: 254
Domain:
Examples:
urn:emergency:uid:gis:Prov:16424289:co.polk.wi.us, urn:emergency:uid:gis:Prov:210252128:waukeshacounty.gov, urn:emergency:uid:gis:Prov:65e160f2ad7f2g1w55k1hjwa74ap891v:countyofdane.com
Description:
The NENA Globally Unique ID (Primary Key) for each record in a GIS data layer. Each record in the GIS data layer MUST have a globally unique ID. When coalescing data from other local 9-1-1 Authorities into the ECRF and LVF, this unique ID MUST continue to have only one occurrence. Additional detail on how to construct the NGUID can be found in section 2.4 NENA Globally Unique IDs (NGUID).

Database Field Name: DateUpdate
Data Type: DATE
Inclusion: Yes
Width:
Domain:
Examples:
2020-01-28T15:47.09.3-06:00 (representing a record updated on January 28, 2020 at 3:47 and 9.3 seconds PM US Central Standard Time, with a precision of .1 second); 2020-07-16T08:31:15.2-05:00 (representing a record updated on July 16, 2020 at 8:31 and 15.2 seconds AM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record was created or last modified.

Database Field Name: Effective
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will become active on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will become active on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time that the record is scheduled to take effect (e.g., the date and time an annexation takes effect and the new Provisioning Boundary is recognized for use in the NG9-1-1 system).

Database Field Name: Expire
Data Type: DATE
Inclusion: No
Width:
Domain:
Examples:
2021-02-11T01:30:00.1-06:00 (representing a record that will become active on February 11, 2021 at 1:30 and 0.1 seconds AM US Central Standard Time, with a precision of .1 second); 2021-10-15T20:15:30.5-05:00 (representing a record that will become active on October 15, 2021 at 8:15 and 30.5 seconds PM US Central Daylight Time, with a precision of .1 second)
Description:
The date and time when the information in the record is no longer considered valid (e.g., the date and time an annexation takes effect and the former Provisioning Boundary is no longer recognized for use in the NG9-1-1 system).

Database Field Name: DiscrpAgID
Data Type: TEXT
Inclusion: Yes
Width: 100
Domain:
Examples:
co.polk.wi.us, waukeshacounty.gov, countyofdane.com
Description:
Agency that receives a Discrepancy Report (DR), should a discrepancy be discovered in the GIS data, and will take responsibility for ensuring discrepancy resolution. This may or may not be the same as the 9-1-1 Authority. This MUST be represented by a domain name that is an Agency Identifier as defined in the NENA Master Glossary of 9-1-1 Terminology, NENA-ADM-000.23-2020 [21].