Geocode addresses for the Portland metropolitan region. The locator is based on RLIS data including the Master Address File and streets and supports finding an address in a single-line format. It is available both as a geocode service and as a downloadable locator package. This is the original geocode service, the original ArcMap-compatible downloadable locator package is available under the name "RLIS Address Locator - Download." The new ArcGIS Pro version of the geocode service with autosuggest functionality enabled is available under the name "RLIS Address Locator (Pro)." Date of last data update: 2025-07-28 This is official RLIS data. Contact Person: Alicia Wood alicia.wood@oregonmetro.gov 503-813-7561 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2751 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

The address-matching process derives spatial data points from input tabular address data. This geocoding package is constructed using road centerline and address point data published by the NJ Office of Information Technology, Office of GIS (NJOGIS.) The geocoder is refreshed monthly using updates of those datasets.For additional support or to download a copy of the geocoding package please visit https://njgin.nj.gov/njgin/edata/geocoding.The geocoder includes a multirole locator that references comprehensive statewide address point and road centerline datasets. These datasets are maintained and published by NJOGIS in cooperation with county and municipal GIS agencies. The data have been reprocessed from the published releases to accommodate optimization of the locators. The published source data can be found here: Address Points - https://njgin.nj.gov/njgin/edata/addresses; Road Centerlines - https://njgin.nj.gov/njgin/edata/roads

Geocode addresses for the Portland metropolitan region. This locator is an ArcGIS Pro version of the RLIS Address Locator, with autosuggestion capabilities enabled. It is based on RLIS data including the Master Address File and Streets and supports finding an address in a single-line format. It is available both as a geocode service and as a downloadable locator package. This is the ArcGIS Pro version of the downloadable locator package, the ArcMap-compatible version is available under the name "RLIS Address Locator - Download." The new ArcGIS Pro version of the geocode service with autosuggest functionality enabled is available under the name "RLIS Address Locator (Pro)." Date of last data update: 2025-11-04 This is official RLIS data. Contact Person: Alicia Wood alicia.wood@oregonmetro.gov 503-813-7561 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3736 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

The Advanced Address Locator for Dakota County is an ArcGIS for Server REST composite locator made up of 18 locators accessing four data layers(Dakota County Address Points, Streets, Parcel Points and NCompass Streets). Each locator has been assigned a unique name, and organized in a method to establish a hierarchy. Address data, which is our most comprehensive source of addresses, is at the top of the hierarchy, followed by parcel data, and street data. The hierarchy will allow the user to assess the level of accuracy and perform a detailed analysis of the results if desired. Data for locators are updated weekly.

This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address. Contact: Lynn Flaaen-Hanna, Development Services Specialist Contact E-mail Link: Map that Lets You Explore and Export Address Data Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.Data Source Type: ESRI ArcGIS Enterprise GeodatabasePreparation Method: N/APublish Frequency: WeeklyPublish Method: AutomaticData Dictionary

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

The Bedford County VA Composite Geocoding service is a composite locator built from geospatial data from NG911 Site Address Points, Road Centerlines, Common Places, Parcels (RPCs, PINs, Owners), Subdivisions, and Populated Places.

This composite locator is made up of three locators: a primary base locator, and two ancillary locators which provide results if supplying Parcel PINs (e.g., 214 A 197 T) and Parcel Owners.

Users can locate using the following search criteria:

• Address Point:
  • (e.g., ‘122 E Main St’)
• Interpolated Street Address:
  • (e.g., ‘125 E Main St’ — Doesn't exist, but the locator estimates where this address would exist)
• Street Name:
  • (e.g., ‘E Main St’)
• Street Intersections (uses ‘ & ’ operator):
  • (e.g., ‘E Main St & N Bridge St’)
• Common Places (i.e., Businesses or other colloquial names for a location):
  • (e.g., ‘Bedford County Animal Shelter’)
• Parcels - RPC:
  • (e.g., ‘80500241’)
• Parcels - PIN:
  • (e.g., ‘214 A 197 T’)
• Parcels - Owner
  • (e.g., ‘COUNTY OF BEDFORD VIRGINIA’, ‘[LAST NAME] [FIRST NAME]’)
• Subdivisions:
  • (e.g., ‘LAKEPOINTE’)
• Populated Places:
  • (e.g., ‘Bedford’, ‘Forest’)

The service can be consumed in ArcGIS Pro, ArcGIS Online, or other GIS applications.

Data is mostly limited to within Bedford County, Virginia, but some common places and populated places in close vicinity to the administrative boundary are still included.

Underlying data is updated regularly, typically weekly, by Bedford County GIS staff.

It is an ArcGIS multirole locator with two roles:

1. Point Address - Generally more accurate results from rooftop location points. Includes a Subaddress if a unit number is located.
   
2. Street Address - Less accurate results from an estimated distance along a street centerline address range if a Point Address was not found.

Instructions for using the Geocoder via ArcGIS Pro, ArcGIS Online, and REST Services are below:

ArcGIS Pro
Web Services
ArcGIS Online

The Address Points dataset shows Utah address points for all twenty-nine Utah counties. An address point represents a geographic location that has been assigned a US Postal Service (USPS) address by the local address authority (i.e., county or municipality) but does not necessarily receive mail. Address points may include several pieces of information about the structure or location that’s being mapped, such as:the full address (i.e., the USPS mailing address, if the address is for a physical location [rather than a PO box]);the landmark name; whether the location is a building;the type of unit;the city and ZIP code; unique code identifiers of the specific geographic location, including the Federal Information Processing Standard Publication (FIPS) county code and the US National Grid (USNG) spatial address;the address source; andthe date that the address point was loaded into the map layer.This dataset is mapping grade; it is a framework layer that receives regular updates. As with all our datasets, the Utah Geospatial Resource Center (UGRC) works to ensure the quality and accuracy of our data to the best of our abilities. Maintaining the dataset is now an ongoing effort between UGRC, counties, and municipalities. Specifically, UGRC works with each county or municipality’s Master Address List (MAL) authority to continually improve the address point data. Counties have been placed on an update schedule depending on the rate of new development and change within them. Populous counties, such as Weber, Davis, Salt Lake, Utah, and Washington, are more complete and are updated monthly, while rural or less populous counties may be updated quarterly or every six months.The information in the Address Points dataset was originally compiled by Utah counties and municipalities and was aggregated by UGRC for the MAL grant initiative in 2012. The purpose of this initiative was to make sure that all state entities were using the same verified, accurate county and municipal address information. Since 2012, more data has been added to the Address Points GIS data and is used for geocoding, 911 response, and analysis and planning purposes. The Address Point data is also used as reference data for the api.mapserv.utah.gov geocoding endpoint, and you can find the address points in many web mapping applications. This dataset is updated monthly and can also be found at: https://gis.utah.gov/data/location/address-data/.

This tutorial will teach you how to take time-series data from many field sites and create a shareable online map, where clicking on a field location brings you to a page with interactive graph(s).

The tutorial can be completed with a sample dataset (provided via a Google Drive link within the document) or with your own time-series data from multiple field sites.

Part 1 covers how to make interactive graphs in Google Data Studio and Part 2 covers how to link data pages to an interactive map with ArcGIS Online. The tutorial will take 1-2 hours to complete.

An example interactive map and data portal can be found at: https://temple.maps.arcgis.com/apps/View/index.html?appid=a259e4ec88c94ddfbf3528dc8a5d77e8

Street_NoNum_and_ZipCode_Composite uses the NYS Streets and Zipcode boundaries to return a match within the street segment. Any address that does not successfully geocode to the first composite can then be run through the second composite locator (Street_NoNum_and_ZipCode_Composite). Recognizing that hits from this locator will not be spatially accurate. This composite locator is made up of the following locators.Locator NameSource DataDescription4A_SS_NoNum_ZipNameNYS Street SegmentsNYS Street Segments dataset using the postal zip code name for the City name in the locator. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.4B_SS_NoNum_CTNameNYS Street SegmentsNYS Street Segments dataset using the city or town name is used for the city name in the locator. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.4C_SS_NoNum_PlaceNameNYS Street SegmentsNYS Street Segments dataset using the alternate place name is used for the city name in the locator. This field is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These areas do not exist everywhere so there will be a limited number of segments with this attribute. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.5_ZipCodePtsZip Code boundariesPoint placed at the centroid of the Zip Code boundaries. Currently, the geocoding service will return all of the results when using the Find Tool within ArcGIS. The user will then be responsible for choosing which of the results they want to keep. The SAM Address Points are the most accurate data available and should be picked anytime a result is returned from one of the SAM address point locators. If the geocoding service is used in the ESRI batch tool, the locator will return a Match from the first locator it comes to in the cascading order. If there are multiple locators with the same score or within the same locator the first result is returned and it is coded as a Tie.The locators will output a field named 'User_fld' which should be used in conjunction with the Loc_Name field. When the Loc_Name field contains one of the Address Point locators (1A, 1B or 1C) this field will contain either a 1,2,3,4 or a 5. When the Loc_Name field contains anything other than the Address Point locators, the 'User_fld' will either be NULL or "0". The numeric values correspond with the type of Address Point that was located:RooftopPrimary Structure EntranceDrivewayParcel CentroidMiscellaneous

This layer began as part of the Virginia.gov data development project in 2008-2009. VGIN was tasked to generate cartography and data for a specific application for location of Virginia state agency locations in relation to the project. In 2010, The State Broadband Data Development Program (SBDD) Community Anchor Institutions (CAI) dataset leveraged much of that data and catalogued broadband service to a specific feature. The points have since been checked and updated annually as part of the Virginia Landmark dataset. The data is matched to the Virginia Address Point dataset. There are numerous data sources associated to the point. The general development methodology is as follows: The facility data was extracted and geocoded to the VGIN Geocoding service. If results were positioned on the Road Centerline by the RCL locator, those features were subsequently updated and moved to match the address point in the data layer. Unmatched results were added to the map. Non-spatial address location data is harvested into a spreadsheet by the source agency and checked against the GIS data annually. Fields for Landmark Name, Place Type, Source, and Source Type can be used to differentiate specific data as stored in the dataset.Full VA Landmark Database: https://vgin.vdem.virginia.gov/datasets/VGIN::virginia-landmarks/explore

The data was created by geocoding a list of facility location addresses derived from the Florida Agency for Health Care Administration (ACHA) list and FPL premise list against a composite address locator. Some addresses were matched on address points, parcel centroids while others were placed according to the street centerline address range. Attributes include classification of critical and noncritical infrastructures, premise number, name and location address. The points representing the location of infrastructure in this data is approximate.

· Source: Florida Agency for Health Care Administration (ACHA), Florida Power and Light (FPL)

· Effective Date: 05/2018

· Last Update: 06/2021

· Update Cycle: Quarterly

This layer began as part of the Virginia.gov data development project in 2008-2009. VGIN was tasked to generate cartography and data for a specific application for location of Virginia state agency locations in relation to the project. In 2010, The State Broadband Data Development Program (SBDD) Community Anchor Institutions (CAI) dataset leveraged much of that data and catalogued broadband service to a specific feature. The points have since been checked and updated annually as part of the Virginia Landmark dataset. The data is matched to the Virginia Address Point dataset. There are numerous data sources associated to the point. The general development methodology is as follows: The facility data was extracted and geocoded to the VGIN Geocoding service. If results were positioned on the Road Centerline by the RCL locator, those features were subsequently updated and moved to match the address point in the data layer. Unmatched results were added to the map. Non-spatial address location data is harvested into a spreadsheet by the source agency and checked against the GIS data annually. Fields for Landmark Name, Place Type, Source, and Source Type can be used to differentiate specific data as stored in the dataset.Full VA Landmark Database: https://vgin.vdem.virginia.gov/datasets/VGIN::virginia-landmarks/explore

"Due to the size of this dataset, both Shapefile and Spreadsheet download options will not work as expected. The File Geodatabase is an alternative option for this data download"This is SCAG's 2019 Annual Land Use (ALU v. 2019.1) at the parcel-level, updated as of February 2021. This dataset has been modified to include additional attributes in order to feed SCAG's Housing Element Parcel Tool (HELPR), version 2.0. The dataset will be further reviewed and updated as additional information is released. Please refer to the tables below for data dictionary and SCAG’s land use classification.Field NameData TypeField DescriptionPID19Text2019 SCAG’s parcel unique IDAPN19Text2019 Assessor’s parcel numberCOUNTYTextCounty name (based on 2016 county boundary)COUNTY_IDDoubleCounty FIPS code (based on 2016 county boundary)CITYTextCity name (based on 2016 city boundary)CITY_IDDoubleCity FIPS code (based on 2016 city boundary)MULTIPARTShort IntegerMultipart feature (the number of multiple polygons; '1' = singlepart feature)STACKLong IntegerDuplicate geometry (the number of duplicate polygons; '0' = no duplicate polygons)ACRESDoubleParcel area (in acreage)GEOID20Text2020 Census Block Group GEOIDSLOPEShort IntegerSlope information1APN_DUPLong IntegerDuplicate APN (the number of multiple tax roll property records; '0' = no duplicate APN)IL_RATIODoubleRatio of improvement assessed value to land assessed valueLU19Text2019 existing land useLU19_SRCTextSource of 2019 existing land use2SCAGUID16Text2016 SCAG’s parcel unique IDAPNText2016 Assessor’s parcel numberCITY_GP_COText2016 Jurisdiction’s general plan land use designationSCAG_GP_COText2016 SCAG general plan land use codeSP_INDEXShort IntegerSpecific plan index ('0' = outside specific plan area; '1' = inside specific plan area)CITY_SP_COText2016 Jurisdiction’s specific plan land use designationSCAG_SP_COText2016 SCAG specific plan land use codeCITY_ZN_COText2016 Jurisdiction’s zoning codeSCAG_ZN_COText2016 SCAG zoning codeLU16Text2016 existing land useYEARLong IntegerDataset yearPUB_OWNShort IntegerPublic-owned land index ('1' = owned by public agency)PUB_NAMETextName of public agencyPUB_TYPETextType of public agency3BF_SQFTDoubleBuilding footprint area (in square feet)4BSF_NAMETextName of brownfield/superfund site5BSF_TYPETextType of brownfield/superfund site5FIREShort IntegerParcel intersects CalFire Very High Hazard Local Responsibility Areas or State Responsibility Areas (November 2020 version) (CalFIRE)SEARISE36Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)1 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)SEARISE72Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)2 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)FLOODShort IntegerParcel intersects with a FEMA 100 Year Flood Plain data from the Digital Flood Insurance Rate Map (DFIRM), obtained from Federal Emergency Management Agency (FEMA) in August 10, 2017EQUAKEShort IntegerParcel intersects with an Alquist-Priolo Earthquake Fault Zone (California Geological Survey; 2018)LIQUAFAShort IntegerParcel intersects with a Liquefaction Susceptibility Zone (California Geological Survey; 2016)LANDSLIDEShort IntegerParcel intersects with a Landslide Hazard Zone (California Geological Survey; 2016)CPADShort IntegerParcel intersects with a protected area from the California Protected Areas Database(CPAD) – www.calands.org (accessed April 2021)RIPARIANShort IntegerParcel centroid falls within Active River Areas(2010)or parcel intersects with a Wetland Area in the National Wetland Inventory(Version 2)WILDLIFEShort IntegerParcel intersects with wildlife habitat (US Fish & Wildlife ServiceCritical Habitat, Southern California Missing Linkages, Natural Lands & Habitat Corridors from Connect SoCal, CEHC Essential Connectivity Areas,Critical Coastal Habitats)CNDDBShort IntegerThe California Natural Diversity Database (CNDDB)includes the status and locations of rare plants and animals in California. Parcels that overlap locations of rare plants and animals in California from the California Natural Diversity Database (CNDDB)have a greater likelihood of encountering special status plants and animals on the property, potentially leading to further legal requirements to allow development (California Department of Fish and Wildlife). Data accessed in October 2020.HCPRAShort IntegerParcel intersects Natural Community & Habitat Conservation Plans Reserve Designs from the Western Riverside MHSCP, Coachella Valley MHSCP, and the Orange County Central Coastal NCCP/HCP, as accessed in October 2020WETLANDShort IntegerParcel intersects a wetland or deepwater habitat as defined by the US Fish & Wildlife Service National Wetlands Inventory, Version 2.UAZShort IntegerParcel centroid lies within a Caltrans Adjusted Urbanized AreasUNBUILT_SFDoubleDifference between parcel area and building footprint area expressed in square feet.6GRCRY_1MIShort IntegerThe number of grocery stores within a 1-mile drive7HEALTH_1MIShort IntegerThe number of healthcare facilities within a 1-mile drive7OPENSP_1MIShort IntegerQuantity of open space (roughly corresponding to city blocks’ worth) within a 1-mile drive7TCAC_2021TextThe opportunity level based on the 2021 CA HCD/TCAC opportunity scores.HQTA45Short IntegerField takes a value of 1 if parcel centroid lies within a 2045 High-Quality Transit Area (HQTA)JOB_CTRShort IntegerField takes a value of 1 if parcel centroid lies within a job centerNMAShort IntegerField takes a value of 1 if parcel centroid lies within a neighborhood mobility area.ABS_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within an absolute constraint area. See the Sustainable Communities Strategy Technical Reportfor details.VAR_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within a variable constraint area. See the Sustainable Communities Strategy Technical Reportfor details.EJAShort IntegerField takes a value of 1 if parcel centroid lies within an Environmental Justice Area. See the Environmental Justice Technical Reportfor details.SB535Short IntegerField takes a value of 1 if parcel centroid lies within an SB535 Disadvantaged Community area. See the Environmental Justice Technical Reportfor details.COCShort IntegerField takes a value of 1 if parcel centroid lies within a Community of Concern See the Environmental Justice Technical Reportfor details.STATEShort IntegerThis field is a rudimentary estimate of which parcels have adequate physical space to accommodate a typical detached Accessory Dwelling Unit (ADU)8.SBShort IntegerIndex of ADU eligibility according to the setback reduction policy scenario (from 4 to 2 feet) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SMShort IntegerIndex of ADU eligibility according to the small ADU policy scenario (from 800 to 600 square feet ADU) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)PKShort IntegerIndex of ADU eligibility according to parking space exemption (200 square feet) policy scenario (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SMShort IntegerIndex of ADU eligibility according to both the setback reduction and small ADU policy scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_PKShort IntegerIndex of ADU eligibility according to both the setback reduction and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SM_PKShort IntegerIndex of ADU eligibility according to both the small ADU policy and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SM_PKShort IntegerIndex of ADU eligibility according to the setback reduction, small ADU, and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)1. Slope: '0' - 0~4 percent; '5' - 5~9 percent; '10' - 10~14 percent; '15' = 15~19 percent; '20' - 20~24 percent; '25' = 25 percent or greater.2. Source of 2019 existing land use: SCAG_REF- SCAG's regional geospatial datasets;ASSESSOR- Assessor's 2019 tax roll records; CPAD- California Protected Areas Database (version 2020a; accessed in September 2020); CSCD- California School Campus Database (version 2018; accessed in September 2020); FMMP- Farmland Mapping and Monitoring Program's Important Farmland GIS data (accessed in September 2020); MIRTA- U.S. Department of Defense's Military Installations, Ranges, and Training Areas GIS data (accessed in September 2020)3. Type of public agency includes federal, state, county, city, special district, school district, college/university, military.4. Based on 2019 building footprint data obtained from BuildingFootprintUSA (except that 2014 building footprint data was used for Imperial County). Please note that 2019 building footprint data does not cover the entire SCAG region (overlapped with 83% of parcels in the SCAG Region).5. Includes brownfield/superfund site whose address information are matched by SCAG rooftop address locator. Brownfield data was obtained from EPA's Assessment, Cleanup and Redevelopment Exchange System (ACRES) database, Cleanups in my community (CIMC), DTSC brownfield Memorandum of Agreement (MOA). Superfund site data was obtained from EPA's Superfund Enterprise Management System (SEMS) database.6. Parcels with a zero value for building footprint area are marked as NULL to indicate this field is not reliable.7. These values are intended as a rudimentary indicator of accessibility developed by SCAG using 2016 InfoUSA business establishment data and 2017 California Protected Areas data. See documentation for details.8. A detailed study conducted by Cal Poly Pomona (CPP) and available hereconducted an extensive review of state and local requirements and development trends for ADUs in the SCAG region and developed a baseline set of assumptions for estimating how many of a jurisdiction’s parcels

AddressNC has been prioritized by the North Carolina Geographic Information Coordinating Council (GICC) as a critical framework dataset. The AddressNC Program runs parallel to and is derived from the North Carolina 911 Board Next Generation 911 (NG911) Program.  Address data has been identified as mission critical for validation and accurate call routing within NG911 and the AddressNC Program completes a full-circle approach of address maintenance and sustainability through applied enhancements and quality control beyond 911 requirements.  A primary goal of AddressNC is to continually develop and maintain quality address points on a continuous cycle through updates published in NG911. Various agencies in federal, state, and local government can benefit by applying practical applications of quality addressing in their own programs, negating the need to rely on outdated statewide addressing data and/or using paid address data sets from third party sources.

A map used in the Master Address Locator app to validate an address used to deliver public safety and other government services.

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

This layer began as part of the Virginia.gov data development project in 2008-2009. VGIN was tasked to generate cartography and data for a specific application for location of Virginia state agency locations in relation to the project. In 2010, The State Broadband Data Development Program (SBDD) Community Anchor Institutions (CAI) dataset leveraged much of that data and catalogued broadband service to a specific feature. The points have since been checked and updated annually as part of the Virginia Landmark dataset. The data is matched to the Virginia Address Point dataset. There are numerous data sources associated to the point. The general development methodology is as follows: The facility data was extracted and geocoded to the VGIN Geocoding service. If results were positioned on the Road Centerline by the RCL locator, those features were subsequently updated and moved to match the address point in the data layer. Unmatched results were added to the map. Non-spatial address location data is harvested into a spreadsheet by the source agency and checked against the GIS data annually. Fields for Landmark Name, Place Type, Source, and Source Type can be used to differentiate specific data as stored in the dataset.Full VA Landmark Database: https://vgin.vdem.virginia.gov/datasets/VGIN::virginia-landmarks/explore

These data include the individual responses for the City of Tempe Annual Business Survey conducted by ETC Institute. These data help determine priorities for the community as part of the City's on-going strategic planning process. Averaged Business Survey results are used as indicators for city performance measures. The performance measures with indicators from the Business Survey include the following (as of 2023):1. Financial Stability and Vitality5.01 Quality of Business ServicesThe location data in this dataset is generalized to the block level to protect privacy. This means that only the first two digits of an address are used to map the location. When they data are shared with the city only the latitude/longitude of the block level address points are provided. This results in points that overlap. In order to better visualize the data, overlapping points were randomly dispersed to remove overlap. The result of these two adjustments ensure that they are not related to a specific address, but are still close enough to allow insights about service delivery in different areas of the city.Additional InformationSource: Business SurveyContact (author): Adam SamuelsContact E-Mail (author): Adam_Samuels@tempe.govContact (maintainer): Contact E-Mail (maintainer): Data Source Type: Excel tablePreparation Method: Data received from vendor after report is completedPublish Frequency: AnnualPublish Method: ManualData DictionaryMethods:The survey is mailed to a random sample of businesses in the City of Tempe. Follow up emails and texts are also sent to encourage participation. A link to the survey is provided with each communication. To prevent people who do not live in Tempe or who were not selected as part of the random sample from completing the survey, everyone who completed the survey was required to provide their address. These addresses were then matched to those used for the random representative sample. If the respondent’s address did not match, the response was not used.To better understand how services are being delivered across the city, individual results were mapped to determine overall distribution across the city.Processing and Limitations:The location data in this dataset is generalized to the block level to protect privacy. This means that only the first two digits of an address are used to map the location. When they data are shared with the city only the latitude/longitude of the block level address points are provided. This results in points that overlap. In order to better visualize the data, overlapping points were randomly dispersed to remove overlap. The result of these two adjustments ensure that they are not related to a specific address, but are still close enough to allow insights about service delivery in different areas of the city.The data are used by the ETC Institute in the final published PDF report.