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.

Vermont E911 Site locations (ESITEs) including buildings, facilities, and development sites; locations are represented by points. Points are attributed with addresses--composing an address points layer. Dataset is updated weekly.Field Descriptions:OBJECTID: Internal feature number. Auto-generated by Esri software.SEGMENTID: Unique segment ID.ESITEID: Unique ESITE ID.GEONAMEID: Ties ESITE to GEONAMEID (unique ID for each road name) in VT E911 Road Centerlines.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East etc.PRIMARYNAME: A concatenation of the street-name parts (PD, PT, SN, ST, SD).ALIAS1: Alternate road name.ALIAS2: Alternate road name.ALIAS3: Alternate road name.ALIAS4: Alternate road name.ALIAS5: Alternate road name.PRIMARYADDRESS: A concatenation of house number and street-name parts (PD, PT, SN, ST, SD).SITETYPE: Type of site. Uses SiteTypes domain*.TOWNNAME: Town name.MCODE: Municpal code.ESN: Emergency Service Number. Developed for each town that indicates a unique town code for each law, fire, and EMS provider. These providers are compared against the master list to determine if they are already present. If they are, the existing state code is used. If the provider is new, they are added to the state master list with the next unique provider number.ZIP: Zip code.PARCELNUM: Parcel number.GPSX: GPS X coordinate.GPSY: GPS Y coordinate.MAPYEAR: Date added to E911 data.UPDATEDATE: Update date.STATE: US State.FIPS8: Federal information processing standards codes.SPAN: Pulled from the VCGI parcel dataset via spatial join 1-3 times per year; NOT MAINTAINED DAILY.SUBTYPE: Field not in use.GlobalID_1: System-generated ID.UNITCOUNT: For commercial and residential, number of units in the site.PRIMARYADD1: Concatenation of house number, full street name, and E911 town. E911 TOWN (AKA E911 JBOUND) IS NOT ALWAYS THE SAME AS POSTAL TOWN NOR IS IT ALWAYS THE SAME AS TOWN DEFINED BY MUNICIPAL BOUNDARY. E911 TOWN (E911 JBOUND) was originally defined for the Master Street Address Guide (MSAG) Community; E911 JBOUND contains names chosen by towns for representing town names for 911 purposes.PRIMARYADD2: Concatenation of PRIMARYADD1 plus zip code.SITETYPE_MULTI1: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI2: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI3: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI4: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.SITETYPE_MULTI5: Additional SITETYPE--if applicable. For development sites, contains the main use the site is to become. Uses SiteTypes domain*.COUNTY: County.COUNTRY: Country.SOURCEOFDATA: Source of data.DRIVEWAYID: Field not in use.ESZ: Emergency Service Zone--a defined area covered by four primary-response agencies.HOUSE_NUMBER: House number.HOUSE_NUMBERSUFFIX: For addresses not in compliance with standards (typically in urbanized areas where otherwise renumbering needs to occur). For example, a new house between 8 and 10 is built and the town calls it 8 1/2 or 8A instead of renumbering; the 1/2 or A would be in this field; there are approximately less than 300-400 of these cases.HOUSE_NUMBERPREFIX: For the three streets where alpha characters come before the house number (e.g., A20 or B12).FIPS: County FIPS number.Shape: Feature geometry.*SiteTypes Domain:ABANDONEDACCESS POINTACCESSORY BUILDINGAIR SUPPORT / MAINTENANCE FACILITYAIR TRAFFIC CONTROL CENTER / COMMAND CENTERAIRPORT TERMINALAMBULANCE SERVICEAUDITORIUM / CONCERT HALL / THEATER / OPERA HOUSEBANKBOAT RAMP / DOCKBORDER CROSSINGBORDER PATROLBUS STATION / DISPATCH FACILITYCAMPCAMPGROUNDCEMETERYCITY / TOWN HALLCOAST GUARDCOLLEGE / UNIVERSITYCOMMERCIALCOMMERCIAL CONSTRUCTION SERVICECOMMERCIAL FARMCOMMERCIAL GARAGECOMMERCIAL W/RESIDENCECOMMUNICATION BOXCOMMUNICATION TOWERCOMMUNITY / RECREATION FACILITYCOURT HOUSECULTURALCUSTOMS SERVICEDAY CARE FACILITYDEVELOPMENT SITEEBS TOWEREDUCATIONALEMERGENCY PHONE / CALLBOXFAIR / EXHIBITION/ RODEO GROUNDSFERRY TERMINAL / DISPATCH FACILITYFIRE STATIONFISH FARM / HATCHERYFITNESS FACILITYFOOD DISTRIBUTION CENTERGAS STATIONGATED W/BUILDINGGATED W/O BUILDINGGOLF COURSEGOVERNMENTGRAVEL PITGREENHOUSE / NURSERYGROCERY STOREHARBOR / MARINAHAZARDOUS MATERIALS FACILITYHAZARDOUS STORAGE FACILITYHEALTH CLINICHELIPAD / HELIPORT / HELISPOTHISTORIC SITE / POINT OF INTERESTHOSPITAL / MEDICAL CENTERHOUSE OF WORSHIPHYDROELECTRIC FACILITYICE ARENAINDUSTRIALINSTITUTIONAL RESIDENCE / DORM / BARRACKSLANDFILLLAW ENFORCEMENTLIBRARYLODGINGLOOKOUT TOWERLUMBER MILL / SAW MILLMANUFACTURING FACILITYMINEMOBILE HOMEMORGUEMULTI-FAMILY DWELLINGMUSEUMNATIONAL GUARD / ARMORYNUCLEAR FACILITYNURSING HOME / LONG TERM CAREOFFICE BUILDINGOFFICE OF EMERGENCY MANAGEMENTOIL / GAS FACILITYOTHEROTHER COMMERCIALOTHER RESIDENTIALOUTPATIENT CLINICPARK AND RIDE / COMMUTER LOTPHARMACYPICNIC AREAPOST OFFICEPRISON / CORRECTIONAL FACILITYPRIVATE AND EXPRESS SHIPPING FACILITYPSAPPUBLIC BEACHPUBLIC GATHERINGPUBLIC TELEPHONEPUBLIC WATER SUPPLY INTAKEPUBLIC WATER SUPPLY WELLPUMP STATIONRACE TRACK / DRAGSTRIPRADIO / TV BROADCAST FACILITYRAILROAD STATIONRESIDENTIAL FARMREST STOP / ROADSIDE PARKRESTAURANTRETAIL FACILITYRV HOOKUPSCHOOLSEASONAL HOMESINGLE FAMILY DWELLINGSKI AREA / ALPINE RESORTSOLAR FACILITYSPORTS ARENA / STADIUMSTATE CAPITOLSTATE GARAGESTATE GOVERNMENT FACILITYSTATE PARKSTORAGE UNITSSUBSTATIONSUGARHOUSETEMPORARY STRUCTURETOWN GARAGETOWN OFFICETRAILHEADTRANSFER STATIONUNKNOWNUS FOREST FACILITYUS GOVERNMENT FACILITYUTILITYUTILITY POLE W/PHONEVETERINARY HOSPITAL / CLINICVISITOR / INFORMATION CENTERWAREHOUSEWASTE / BIOMASS FACILITYWASTEWATER TREATMENT PLANTWATER TANKWATER TOWERWIND FACILITY / WIND TOWERYOUTH CAMP

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.

Updated Continually

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.

VT E911 Composite geocoder - uses ESITE, RDSNAME, and RDSRANGE. REFRESHED WEEKLY. VCGI, in collaboration with the VT E911 Board, has created a suite of geocoding services that can be used to batch geocode addresses using ArcGIS Desktop 10.x. This service can also be integrated into ESRI ArcGIS web-based mapping applications.Input Address Requirements Must use valid E911 addresses (street style addressing...no P.O. box addresses!) and E911 town names. Limitations Don't attempt to geocode more than 50000 records or so. You must have an Internet connection to use the services. A DSL, cable, or other high bandwidth connection is the best option. Addresses other than E911 addresses are not supported. ArcGIS Pro - How To:Startup ArcGIS ProUnder the "Insert" ribbon select Connections --> New ArcGIS Server. Server URL = https://maps.vcgi.vermont.gov/arcgis/servicesBrowse to the ./EGC_services folder and select GEOCODE_COMPOSITE (or GEOCODE_ESITE).Add the table you want to geocode to project, then right-click and select "Geocode Table". Choose the “Go to Tool” option at the bottom of the dialogue box.Make selections and run geocoder.ArcGIS Desktop (ArcMap) - How To: Startup ArcMap 10+ Add a table containing VT addresses to geocode. ?Click the "Add Data" button.Navigate to your table, choose to add your tableRight-click on the table in the table of contentsSelect "Geocode Addresses...".Select "Add" in the dialog box.Browse to the "GIS Servers" icon in your catalog, then double click "Add ArcGIS Server".Select "Use GIS Services", then Next.ServerURL = https://maps.vcgi.vermont.gov/arcgis/services then click finish.Browse to "arcgis on maps.vcgi.org (user)". Browse to .\EGC_services folder.Select GECODE_ESITE (or GEOCODE_COMPOSITE). Click OK.Select whatever options you want in the geocode dialog box, including output, then click ok.The output will be automatically added to your ArcMap session.

EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. http://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfm

This data is part of Santa Fe County's Rural Addressing program.

(Link to Metadata) Polygon data that is unique to the Town boundary. These polygons define the primary coverage areas of the three primary responders; Law, Fire, and EMS.

Description: This feature layer contains currently available 911 Site Structure Address Points as submitted by the Commonwealth's Public Safety Answering Posts (PSAPs) to the Kentucky 911 Services Board. Data from additional PSAPs will be added as it becomes available. All address point data provided by the PSAPs has undergone a thorough QA/QC and aggregation process which ensures that it meets or exceeds NENA NG911 GIS data standards. Mapping of the point features has been done in accordance with Kentucky NG911 Mapping Guide.Note: Data from this service will be submitted on a quarterly basis to the National Address Database (NAD). More information about the NAD can be found here.Bulk Data Download: https://ky.box.com/v/kymartian-E911 or https://ky.box.com/v/kymartian-911-address-points

This hosted feature layer has been published in RI State Plane Feet NAD 83.Estimated centerlines of real world roadways. Includes street names, address ranges, and other attributes especially useful for geocoding. 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.

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.

This data is part of Harding County's Rural Addressing program.

E911 Site locations including buildings, hydrants, public phones. All Towns as of 2003 have been mapped. There are no unmapped towns.

This dataset contains locations and attributes of Address Points as created and maintaned by the Enhanced 911 (E911) Addressing Office in the Lexington-Fayette Urban County Government (LFUCG) Department of Public Safety. It contains addresses in Lexington-Fayette County, Kentucky utilized for 911 response and internal business processes.. The types of addresses available in the dataset include:Publicly Available Address Types"R" (Residential) - Apartment units, retirement communities/buildings, duplexes, single family residential, mobile home trailers, and dormitories."O" (Other) - Everything that cannot be coded as one of the other categories. This includes all commercial properties, schools, parks, libraries, barns, farms, hotels, swimming pools, etc."V" (Vacant) - Represent a business suite that is unused due to expansion of neighboring suite or an individual suite that has no occupancy. "X" (Address no longer exists) - Addresses completely deleted from the database for various reasons."P" (Parcel based) – Represents the address of parcel of land that has a record in the Fayette PVA office."S" (Structure) - Represents the overall address for a structure that has secondary unit numbers such as apartment or business suite numbers.Not Publicly Available Address Types"5G" - (5G type cell sites) - Represent the new 5G type transmitters that are installed on existing streetlights newly installed utility poles. In some cases, these types of sites could be installed on any structure including billboards, commercial signs, etc. Notation in the COMMIT filed to note type of structure. "C" - (Cell site) - Represents regular Cell Sites on standalone towers or on existing structures.“U” (Utility) - Alltel exchange buildings, KU substations, Sanitary Sewer pump stations, etc. Buildings that serve as offices for utility companies shall be coded as "O".

The points in this dataset represent the location of a site or structure in Lee County, Florida to which an address has been assigned by Lee County Department of Public Safety/E911 Addressing Division. Parcel STRAP is added by Lee County GIS

The Rural Addressing Line File can be used to differentiate road feature types, address ranges and ZIP Codes, and jurisdictional transfers.

(Link to Metadata) Landmarks captured for E911 used as common place point names.

This data is part of Quay County's Rural Addressing program.

The Rural Addressing Line File can be used to differentiate road feature types, address ranges and ZIP Codes, and jurisdictional transfers.