Address points represent all sites and structures with an assigned street address. The Address Points layer is strongly recommended in the NENA standard, but it is required in the Kansas NG911 GIS Data Model.At minimum, there is a point on every addressable single-unit building, a point on each living unit/occupancy of every multi-unit building or complex, and a point for every telephone service address in the TN listing. This data is updated quarterly.Please refer to the Kansas NG911 GIS Data Model for more details: Kansas NG9-1-1 GIS Data Model (kansasgis.org)Some Kansas PSAP GIS Data Stewards prefer to handle their address point GIS data distribution on a per request basis. If you would like to request address points for an area not included in this public dataset, you can do so by registering for an account and submitting a GIS Data Request on the Kansas NG911 Program Portal (https://portal.kansas911.org/).

A spatial data layer containing line geometry features for representing the center line of roadways in Baltimore City, as documented in the City's enterprise GIS database and Department of Transportation right-of-way data sources. The data contains information on street address ranges, speed limits, one-way designations, street types, and many other street related data. The data employs what's referred to as the Next Generation 9-1-1 (NG911) schema/data standard, which has specific attribute field names, field formats, and data standards to support the standardization required by a future public safety NG911 system, as set forth by the National Emergency Number Association (NENA). The data contained in this data layer (number of features, accuracy, locations) will match the data in the other street centerline layer on Open Baltimore (“Street Centerline (Native)”), just the format of the attribute field names and data standards will be different. This data also employs the WGS 1984 projected coordinate system (WKID: 4326). Data is updated on a quarterly basis.Data Dictionary:

field_name description data_type range_of_possible_values example_values searchable

1 OBJECTID The database’s internal unique identifier for the data table record. Number 0 - 999999999 4721 No

2 DiscrpAgID Agency that receives a Discrepancy Report (DR), should a discrepancy 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 [1]. Free Text Entry % (any ID, per NG911 standard) pgcpsc.pgc.md.us.msi911.net (example from PG County, MD) Yes

3 DateUpdate The date and time that the record was created or last modified. This value MUST be populated upon modifications to attributes, geometry, or both. Date 1/1/1990 00:00:00 - 12/31/2100 00:00:00. 8/31/2021 10:04 Yes

4 effective The date and time that the record is scheduled to take effect in a NG911 system. Date 1/1/1990 00:00:00 - 12/31/2100 00:00:00. 8/31/2021 10:04 Yes

5 expire The date and time when the information in the record is no longer considered valid in a NG911 system. Date 1/1/1990 00:00:00 - 12/31/2100 00:00:00. 8/31/2021 10:04 Yes

6 RCL_NGUID The NENA Globally Unique ID for each Road Centerline. Each record in the Road Centerlines 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. One way to accomplish this is to append the 9-1-1 Authority’s domain to the end of the “locally unique ID”. Free Text Entry % (any name, per NG911 standard) RCL243246@pgcpsc.pgc.md.us.msi911.net (example from PG County, MD) Yes

7 AdNumPre_L An extension of the Address Number that precedes it and further identifies a location along a thoroughfare or within a defined area, on the Left side of the road segment relative to the FROM Node. It contains any alphanumeric characters, punctuation, and spaces preceding the Left FROM Address and Left TO Address. Free Text Entry % (any alphanumeric value),

8 AdNumPre_R An extension of the Address Number that precedes it and further identifies a location along a thoroughfare or within a defined area, on the Right side of the road segment relative to the FROM Node. It contains any alphanumeric characters, punctuation, and spaces preceding the Right FROM Address and Right TO Address. Free Text Entry % (any alphanumeric value),

9 FromAddr_L In a GIS Road Centerlines layer, each feature has a begin point and an endpoint. The FROM Node is the begin point while the TO Node is the endpoint. Each has a left side and a right side relative to a begin node and an end node. The Left FROM address is the address number on the Left side of the road segment relative to the Left FROM Node. Number 0 - 9999 400 Yes

10 ToAddr_L In a GIS, each feature has a begin point and an endpoint. The FROM Node is the begin point while the TO Node is the endpoint. Each has a left side and a right side relative to a begin node and an end node. The Left TO address is the address number on the Left side of the road segment relative to the Left TO Node. Number 0 - 9999 498 Yes

11 FromAddr_R In a GIS Road Centerlines layer, each feature has a begin point and an endpoint. The FROM Node is the begin point while the TO node is the endpoint. Each has a left side and a right side relative to a begin node and an end node. The Right FROM address number is the address number on the Right side of the road segment relative to the Right FROM Node. Number 0 - 9999 401 Yes

12 ToAddr_R In a GIS Road Centerlines layer, each feature has a begin point andan en dpoint. The FROM Node is the begin point while the TO node is the endpoint. Each has a left side and a right side relative to a begin node and an end node. The Right TO address number is the address number on the Right side of the road segment relative to the Right TO Node. Number 0 - 9999 499 Yes

13 Parity_L The even or odd property of the address number range on the Left side of the road segment relative to the FROM Node. Category E=Even, O=Odd, B=Both, Z=0-0 Address Range or NULL-NULL Even, E Yes

14 Parity_R The even or odd property of the address number range on the Right side of the road segment relative to the FROM Node. Category E=Even, O=Odd, B=Both, Z=0-0 Address Range or NULL-NULL Odd, O Yes

15 St_PreMod A word or phrase that precedes and modifies the Street Name element but is separated from it by a Street Name Pre Type or a Street Name Pre Directional or both. The field length is currently 15 for existing special cases, but all attempts should be made to follow the domain for this field. Free Text Entry % (any name),

16 St_PreDir A word preceding the Street Name element that indicates the direction taken by the road from an arbitrary starting point or line, or the sector where it is located. Category North, South, East, West, Northeast, Northwest, Southeast, Southwest,

17 St_PreTyp A word or phrase that precedes the Street Name element and identifies a type of thoroughfare in a complete street name. Category NENA defined list,

18 St_PreSep A preposition or prepositional phrase between the Street Name Pre Type and the Street Name. This element is defined in CLDXF (NENA-STA-004) [3] as a US specific extension of PIDF-LO per RFC 6848 [6]. Category NENA defined list,

19 St_Name The official name of the road, usually defined by the lowest jurisdictional authority (e.g., Baltimore City). The street name does not include any street types, directionals, or modifiers. For "Alley" street type centerline segments, an alley naming routine was employed in the legacy database to populate the street name field based on the names of the parallel streets, with the western or northern street listed first (e.g., HICKORY-ROLAND). Alleys that did not have a second parallel street (i.e., alleys that back up to woods, train tracks, etc.) were named with the parallel street name and post type followed by “Rear” (e.g. TUSCANY CT REAR) to prevent potential name duplication. If there were multiple alleys in a single block, they were named as above, then numbered from west to east or north to south (e.g., CHESTNUT-KESWICK 1, CHESTNUT-KESWICK 2). Free Text Entry % (any name) FAYETTE, EASTERN, HICKORY-ROLAND Yes

20 St_PosTyp A word or phrase that follows the Street Name element and identifies a type of thoroughfare in a complete street name. The field length is currently 50 for existing special cases, but new assignments should follow the domain for this field. Category NENA defined list,

21 St_PosDir A word following the Street Name element that indicates the direction taken by the road from an arbitrary starting point or line, or the sector where it is located. Category North, South, East, West, Northeast, Northwest, Southeast, Southwest,

22 St_PosMod A word or phrase that follows and modifies the Street Name element, but is separated from it by a Street Name Post Type or a Street Name Post Directional or both. Always follows and modifies the street name. Free Text Entry % (any name),

23 LSt_PreDir The leading street direction prefix as it previously existed prior to the adoption of the NG9-1-1 Data Model as assigned by the local addressing authority. Category N, S, E, W, NE, NW, SE, SW,

24 LSt_Name The street name field as it would appear in the MSAG and legacy database, as assigned by the local addressing authority. For "Alley" street type centerline segments, an alley naming routine was employed in the legacy database to

The NG9-1-1 GIS Guidelines and Best Practices Manual is a cooperative effort between the Arizona 9-1-1 Program, the AGIC 9-1-1 Committee and the Arizona 9-1-1 Program for the 9-1-1 System Administrators and GIS practitioners at different levels such as local government, tribal, County government, metropolitan planning organizations (MPO), whom support any of the 9-1-1 systems.Community. Initial Document created in 2017, Version 2 updated in 2020 based on new NENA standards and GIS platforms in Arizona.

The New Jersey Office of Information Technology, Office of GIS (NJOGIS), in partnership with several local GIS and public safety agencies, has built a comprehensive statewide NG9-1-1 database meeting and exceeding the requirements of the National Emergency Number Association (NENA) 2018 NG9-1-1 GIS Data Standard (NENA-STA-006.1-2018). The existing New Jersey Statewide Address Point data last published in 2016 has been transformed in the NENA data model to create this new address point data.The initial address points were processed from statewide parcel records joined with the statewide Tax Assessor's (MOD-IV) database in 2015. Address points supplied by Monmouth County, Sussex County, Morris County and Montgomery Township in Somerset County were incorporated into the statewide address points using customized Extract, Transform and Load (ETL) procedures.The previous version of the address points was loaded into New Jersey's version of the NENA NG9-1-1 data model using Extract, Transform and Load (ETL) procedures created with Esri's Data Interoperability Extension. Subsequent manual and bulk processing corrections and additions have been made, and are ongoing.

The New Jersey Office of Information Technology, Office of GIS (NJOGIS), in partnership with several local GIS and public safety agencies, as well as the NJ Department of Transportation, has built a comprehensive statewide NG9-1-1 database meeting and exceeding the requirements of the National Emergency Number Association (NENA) 2018 NG9-1-1 GIS Data Standard (NENA-STA-006.1-2018). The previous New Jersey statewide road segment data (Tran_road_centerline_NJ), which included the road name alias information, has been transformed into the NENA data model to create the street name alias table.The existing road centerlines were loaded into New Jersey's version of the NENA NG9-1-1 data model using Extract, Transform and Load (ETL) procedures created with Esri's Data Interoperability Extension. The data subsequently have been updated and corrected.The road centerlines no longer contain any linear referencing information. The linear referencing will only be maintained by the NJ Department of Transportation as part of the NJ Roadway Network.