Connecticut address point dataset used for locating 9-1-1 calls. The address point feature class format is derived from National Emergency Number Association (NENA) and Federal Geographic Data Committee (FGDC) addressing standards. All address components, like address number, streets name and unit number, are broken up into their individual components to enable maximum flexibility for use. Fields within feature class should be able to accommodate all addresses within the state of Connecticut. The source for the addresses is primarily derived from municipal parcel data and other municipal sources.

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.

Information cutoff 2026-02-18 15:32:51.057647 NG_Addresses show point locations for addressable structures and other landmark locations such as ballparks, cemetaries, boat launches, etc. The data is attributed with a physical address, site type, and other related information. NG_ROADS contains updated road centerline and road name data for Maine at 1to24,000 scale. NG_PSAP data was developed to implement the Next Generation 911 project in Maine. This data contains up-to-date public-safety answering point (PSAP), sometimes called public-safety access point, which is a call center responsible for answering calls to an emergency telephone number for police, firefighting, and ambulance services.

Address points for the state of Tennessee as part of the NG911data project, created and maintained by the TN ECB and the local 911 districts.Update FrequencyThis dataset is updated monthlyAbout [link]The Next Generation (NG) 9-1-1 GIS Data product is a comprehensive dataset that contains various geospatial data layers benefiting public safety agencies within state and local government. The core layers in this product are street centerlines, address points, and Public Safety Answering Point (PSAP) boundaries which form the backbone of the Next Generation 9-1-1 Call Routing System. This dataset facilitates Tennessee’s participation in the National Address Database and is also used to support many other mapping and geocoding requirements at the state and federal level.Project Information and Data StandardsTennessee Emergency Communications Board

This hosted feature layer has been published in RI State Plane Feet NAD 83.Representative locations of structures and sites throughout Rhode Island. These data include addressed and unaddressed locations as well as occupied and unoccupied structures. These data were originally designed and developed for Rhode Island E 9-1-1 Uniform Emergency Telephone System (RI E 9-1-1) purposes. This dataset continues to be maintained to provide an accurate spatial reference for RI E 9-1-1 telecommunicators. Portions of this dataset were collected as early as 2001. Inaccuracies do exist in these data and are therefore under constant revision. Any discrepancies, inaccuracies or inconsistencies recognized in these data should be reported to the pertinent municipality who should alert RI E-911. Users are also encouraged to email ri911gis@akassociates911.com with any suggested updates for this actively maintained dataset.

Download In State Plane Projection Here. These address points were developed for a myriad of uses including general public geocoding in Lake County web sites and NG-911 emergency dispatch. All addresses are reviewed on a monthly basis against the United States Post Office delivery database to ensure that they are still active. New addresses are added at this time or earlier if they are made known to Lake County GIS by local data partners. Attributes DiscrpAgID through Elev reflect the NENA NG-911 / State of Illinois GIS Data model. Additional local data fields have also been included. The fields LSt_PreDir, LSt_Name, LSt_Type and LSt_PosDir are formatted according to United States Postal Service standards.Update Frequency:This dataset is updated on a weekly basis.

911 Public Safety Answering Point (PSAP) service area boundaries in New Mexico According to the National Emergency Number Association (NENA), a Public Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1 calls. The service area is the geographic area within which a 911 call placed using a landline is answered at the associated PSAP. This dataset only includes primary PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive calls that have been transferred by a primary PSAP. Backup PSAPs provide service in cases where another PSAP is inoperable. Most military bases have their own emergency telephone systems. To connect to such system from within a military base it may be necessary to dial a number other than 9 1 1. Due to the sensitive nature of military installations, TGS did not actively research these systems. If civilian authorities in surrounding areas volunteered information about these systems or if adding a military PSAP was necessary to fill a hole in civilian provided data, TGS included it in this dataset. Otherwise military installations are depicted as being covered by one or more adjoining civilian emergency telephone systems. In some cases areas are covered by more than one PSAP boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where a specific call is routed may depend on how busy the applicable PSAPS are (i.e. load balancing), operational status (i.e. redundancy), or time of date / day of week. If an area does not have 911 service, TGS included that area in the dataset along with the address and phone number of their dispatch center. These are areas where someone must dial a 7 or 10 digit number to get emergency services. These records can be identified by a "Y" in the [NON911EMNO] field. This indicates that dialing 911 inside one of these areas does not connect one with emergency services. This dataset was constructed by gathering information about PSAPs from state level officials. In some cases this was geospatial information, in others it was tabular. This information was supplemented with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was researched to verify its tabular information. In cases where the source data was not geospatial, each PSAP was researched to determine its service area in terms of existing boundaries (e.g. city and county boundaries). In some cases existing boundaries had to be modified to reflect coverage areas (e.g. "entire county north of Country Road 30"). However, there may be cases where minor deviations from existing boundaries are not reflected in this dataset, such as the case where a particular PSAPs coverage area includes an entire county, and the homes and businesses along a road which is partly in another county. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.

This Dataset involves the frequency of 911 emergency calls made throughout the year and also for which common reasons or incidents 911 calls are usually made during which part of the year.

The data contains the following fields:

lat: Latitude of the Location lng: Longitude of the Location desc: Description of the Emergency Call
zip: Zipcode of the location title: Description of the reason for the call timeStamp: Time of the incident YYYY-MM-DD HH:MM:SS
twp: Township of the caller addr: Address of the caller e: Dummy variable

911 Public Safety Answering Point (PSAP) service area boundaries in the United States According to the National Emergency Number Association (NENA), a Public Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1 calls. The service area is the geographic area within which a 911 call placed using a landline is answered at the associated PSAP. This dataset only includes primary PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive calls that have been transferred by a primary PSAP. Backup PSAPs provide service in cases where another PSAP is inoperable. Most military bases have their own emergency telephone systems. To connect to such a system from within a military base, it may be necessary to dial a number other than 9 1 1. Due to the sensitive nature of military installations, TGS did not actively research these systems. If civilian authorities in surrounding areas volunteered information about these systems, or if adding a military PSAP was necessary to fill a hole in civilian provided data, TGS included it in this dataset. Otherwise, military installations are depicted as being covered by one or more adjoining civilian emergency telephone systems. In some cases, areas are covered by more than one PSAP boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where a specific call is routed may depend on how busy the applicable PSAPs are (i.e., load balancing), operational status (i.e., redundancy), or time of day / day of week. If an area does not have 911 service, TGS included that area in the dataset along with the address and phone number of their dispatch center. These are areas where someone must dial a 7 or 10 digit number to get emergency services. These records can be identified by a "Y" in the [NON911EMNO] field. This indicates that dialing 911 inside one of these areas does not connect one with emergency services. This dataset was constructed by gathering information about PSAPs from state level officials. In some cases, this was geospatial information; in other cases, it was tabular. This information was supplemented with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was researched to verify its tabular information. In cases where the source data was not geospatial, each PSAP was researched to determine its service area in terms of existing boundaries (e.g., city and county boundaries). In some cases, existing boundaries had to be modified to reflect coverage areas (e.g., "entire county north of Country Road 30"). However, there may be cases where minor deviations from existing boundaries are not reflected in this dataset, such as the case where a particular PSAPs coverage area includes an entire county plus the homes and businesses along a road which is partly in another county. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.

The data available here identifies and describes a sampling of publicly available datasets about the 911 emergency response system. This list of datasets is a resource for researchers, civic technologists, activists, and journalists seeking to learn more about the 911 emergency response system. The list helps to identify relevant datasets that could be used to understand various types of 911 activity.

During the first quarter of 2021, the R911 NAT created a list of priority cities including the top 100 cities by population, all state capitals, and the 82 cities that are home to Code for America Brigades. The team then conducted internet searches for each city using terms like “911 calls for service” and “open 911 data.” The dataset and a codebook defining each of these fields are provided as .csv files within a zip file.

Note: this file does not contain the actual 911 datasets, which often number in the millions of records. The data_link field contains the URL of the site where each dataset is publicly available.

See also: The Reimagine 911 knowledge base at: https://reimagine-911.gitbook.io/knowledge-base

Contributors: This open data review was performed by the Code for America Reimagine 911 National Action Team. Contributing team members include: Aleks Hatfield, Brandon Bolton, Chizo Nwagwu, Dan Stormont, Elaine Chow, Em Spalti, Erica Pauls, Gio Sce, Gregory Janesch, Iva Momcheva, Ivelina Momcheva, Jamie Klenetsky Fay, Jason Trout, Jaya Prasad Jayakumar, Jennifer Miller, Jim Grenadier, Joanna Smith, Jonathan Melvin, Katlyn McGraw, Margaret Fine, Mariah Lynch, Micah Mutrux, Michelle Hoogenhout, Patina Herring, Peter Zeglen, Sarah Graham, Sebastian Barajas

This statewide dataset contains next generation 9-1-1 address points for the State of Arizona, curated through the Arizona Department of Administrations (ADOA) Arizona 9-1-1 Program. The dataset is a vital resource for emergency services and public safety, providing accurate location information for emergency calls. The dataset includes geocoded address points and is a spatial dataset that can be used for various purposes such as analysis, mapping, and visualization. This dataset is a product of the ADOA Arizona 9-1-1 Program and is made available through ArcGIS Online. It is tagged with keywords such as Arizona, Next Generation 9-1-1, Address Points, ADOA, Arizona 9-1-1 Program, Emergency Services, Public Safety, Geocoding, Spatial Data, and Statewide Dataset. Spatial Reference: WGS 1984.

Data Description: Emergency Communications Center Calls are records captured for each call. The call data does not contain the nature of the emergency or dispatched resources. For dispatch data reference Police Calls for Service (CAD) or Cincinnati Fire Incidents (CAD).

Data Creation: This dataset includes both emergency (911) and administrative calls to the center. To obtain just emergency (911) calls filter for Call Type ID = 911 CALLS.

Data Created By: The source of this data is the City of Cincinnati's Call System provided by West Communications.

Refresh Frequency: This dataset updates weekly on Fridays.

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/snnn-n6ic

Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

A spatial data layer containing point geometry features for representing both the physical and mailing addresses for properties, buildings, and sub-address locations in Baltimore City, as documented in the City's real property and property location database sources. 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, point locations) will match the data in the other address point data layer on Open Baltimore (“Address Point (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 91715 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 Site_NGUID The NENA Globally Unique ID for each address point feature. Each record in this layer MUST have a globally unique ID and it must be unique across all NG911 datasets. Free Text Entry % (any name, per NG911 standard) SSAP435LionsSt23531@pgcpsc.pgc.md.us.msi911.net (example from PG County, MD) Yes

7 Country The name of a country represented by its two-letter ISO 3166-1 English country alpha-2 code elements in capital ASCII letters (all records will have the value “US”). Category United States (US) United States, US Yes

8 State The 2-letter abbreviation for the federal state area that contains the address point (all records will have the value Maryland). Category Maryland (MD) Maryland, MD Yes

9 County The administrative county area that contains the address point (all records will have the value Baltimore City). Category Baltimore City Baltimore City Yes

10 AddCode A code that specifies a geographic area. Used in Canada to hold a Standard Geographical Classification code; it differentiates two municipalities with the same name in a province that does not have counties. Category % (any code),

11 Inc_Muni The name of the Incorporated Municipality or other general-purpose local governmental unit (if any) where the address is located. However, use "Unincorporated" if the address is not within an incorporated local government (all records will have the value “Baltimore”). Category Baltimore Baltimore Yes

12 Uninc_Comm The name of an Unincorporated Community, either within an incorporated municipality or in an unincorporated portion of a county, or both, where the address is located. Free Text Entry

13 Nbrhd_Comm The name of an unincorporated neighborhood, subdivision, or area, either within an incorporated municipality or in an unincorporated portion of a county or both, where the address is located.The name of the subdivision this address participates in. Free Text Entry % (any name),

14 AddNum_Pre An extension of the Address Number that precedes it and further identifies a location along a thoroughfare or within a defined area. Free Text Entry % (any prefix),

15 Add_Number The numeric identifier of a location along a thoroughfare or within a defined community .Alpha-numeric field containing the structure number or value for the site address civic location assigned by the local addressing authority. Usually an integer which defines the individual address number for the structure. As this is the primary structure value, alphabetic characters should only appear in this field if they are part of the house number, not a secondary address (like an apartment, suite or unit). Duplex structures with no primary address can be populated in this field (i.e., ‘101A’ and ‘101B’). Number 1 -- 9999 401, 3232, “1600” in “1600 Pennsylvania Avenue” Yes

16 AddNum_Suf An extension of the Address number that follows it and further identifies a location along a thoroughfare or within a defined area. Free Text Entry 1/2-9999, A - Z,

17 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. Free Text Entry % (any name),

18 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,

19 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,

20 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,

21 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

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

23 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,

24 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. Free Text Entry % (any name),

25 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,

26 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 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

27 LSt_Type The valid

The 9-1-1 emergency response system is established in Huron County. Huron County GIS facilitates the management and maintenance of our established municipal addressing system. Each individual property in Huron County is identified with a distinctive property identification number. The addressing system consists of the municipality name, road name, and address (number). The assigned rural number represents the approximate distance from the baselines and bearing from our municipal baselines (Highway No. 4 and Highway No. 8). The address ranges for each rural block appear on the road sign at each intersection. North and east sides of roadways are even numbers and the west and south sides of the roadways are odd numbers. Rural numbers in Huron County have 5 digits. Urban addressing retained historical numerical addressing in most cases. Address numbers for each property in the County, with a structure, are clearly visible either on the front of the building or on a blade at the end of a driveway.

Please contact the County of Huron Corporate Services IT/GIS Department if you have any questions at (519)-524-8394 ext. 3278 or 911@huroncounty.ca.

This data set is part of the NENA Standard NG911 GIS Data Model and is referred to as the RoadCenterlineLine layer in the GIS Data Layers Registry in NENA-STA-010 [3] and in NENA documents. The Road Centerlines feature class represents the navigable roadway network used for Next Generation 911 (NG911) call routing and location validation in North Carolina. Each feature is a linear geometry depicting the centerline of a roadway segment and includes standardized attributes required for emergency response operations. These attributes include complete road name elements, left and right address ranges with parity, directionality, and jurisdictional information.The data set is structured according to the NG911 GIS Data Model and aligns with NENA NG911 data standards. The data is maintained by local GIS authorities and aggregated at the state level to ensure completeness, topological accuracy, and interoperability across jurisdictions. The RoadCenterlineLine layer is an integral part of any public safety GIS. Projected Coordinate System: NAD 1983 (2011) State Plane North Carolina FIPS 3200 (US Feet).

The City of Bend site address data plays a key role in many business processes. This point feature class represents all current and retired site address points within the City of Bend. Data is updated as building permits are issued or new development occurs. For more details regarding the City of Bend addressing authority and standards please see the Bend Code Chapter 3.90.Please note this data is not a point-of-delivery dataset and should not be used for mailing purposes. Data is updated nightly. Field Name DescriptionOBJECTIDFor internal useSITEADDIDFor internal useADDPTKEYFor internal useADDRNUMAddress NumberUNITTYPEUnity TypeUNITIDUnit IDALTUNITTYPEAlternative Unit TypeALTUNITIDAlternative Unity IDFULLNAMEFull road nameFULLADDRFull addressPLACENAMEPlace name description/typeMUNICIPALITYAssigned municipalityESNUnique 3 to 5 digit emergency service numberPSAPPublic safety answering pointMSAGE911 Managed Street Address Guide (MSAG)ADDRCLASSAddress descriptionPOINTTYPESite address point location typeCAPTUREMETHMethod used to determine site address point location. STATUSSite address point statusTAXLOTTax lot ID for address placementADDTYPESite address point typePLACEMENTCONFSite address point placement confidenceLATTITUDELatitude (decimal degrees)LONGITUDELongitude (decimal degrees)ZIPCODEFive-digit postal zip codeShapeFor internal usecreate_userFor internal usecreated_dateFor internal uselast_edited_userFor internal uselast_edited_dateFor internal useGlobalIDFor internal use

MassGIS is working very closely with the State 911 Department in the state’s Executive Office of Public Safety and Security on the Next Generation 911 Emergency Call System. MassGIS developed and is maintaining the map and address information that are at the heart of this new system. Statewide deployment of this new 9-1-1 call routing system was completed in 2018.Address sources include the Voter Registration List from the Secretary of the Commonwealth, site addresses from municipal departments (primarily assessors), and customer address lists from utilities. Addresses from utilities were “anonymized” to protect customer privacy. The MAD was also validated for completeness using the Emergency Service List (a list of telephone land line addresses) from Verizon.The MAD contains both tabular and spatial data, with addresses being mapped as point features. At present, the MAD contains 3.2 million address records and 2.2 million address points. As the database is very dynamic with changes being made daily, the data available for download will be refreshed weekly.A Statewide Addressing Standard for Municipalities is another useful asset that has been created as part of this ongoing project. It is a best practices guide for the creation and storage of addresses for Massachusetts Municipalities.Points features with each point having an address to the building/floor/unit level, when that information is available. Where more than one address is located at a single location multiple points are included (i.e. "stacked points"). The points for the most part represent building centroids. Other points are located as assessor parcel centroids.Points will display at scales 1:75,000 and closer.MassGIS' service does not contain points for Boston; they may be accessed at https://data.boston.gov/dataset/live-street-address-management-sam-addresses/resource/873a7659-68b6-4ac0-98b7-6d8af762b6f1.More details about the MAD and Master Address Points.Feature service also available.

Road centerlines for the state of Tennessee as part of the NG911data project, created and maintained by the TN ECB and the local 911 districts.Update FrequencyThis dataset is updated monthlyAbout [link]The Next Generation (NG) 9-1-1 GIS Data product is a comprehensive dataset that contains various geospatial data layers benefiting public safety agencies within state and local government. The core layers in this product are street centerlines, address points, and Public Safety Answering Point (PSAP) boundaries which form the backbone of the Next Generation 9-1-1 Call Routing System. This dataset facilitates Tennessee’s participation in the National Address Database and is also used to support many other mapping and geocoding requirements at the state and federal level.Project Information and Data StandardsTennessee Emergency Communications Board

Dataset

This dataset was created by MohamedKhalidMohamed

Released under Database: Open Database, Contents: Database Contents

Contents

GIS Address Points, Road Centerlines, and Building Footprints provide base data information for many purposes, including call routing and emergency response within the New River Valley 911 Authority.