Metro Address Points Dataset

This dataset is a compilation of address point data from metro area address authorities, which are predominantly cities. The dataset is intended to contain a point location and the official address (as defined by the address authority) for all occupiable units and any other official addresses within the jurisdictional boundary of each address authority. A number of other attributes are available in the dataset, but may not be populated by some address authorities. <br/><br/>Metro area counties are playing a coordinative role to work with cities to create, maintain and aggregate address points. Currently this dataset contains points for all Seven Metropolitan Counties as well as participating bordering counties. <br/><br/>Some jurisdictions in this dataset contain parcel points and not complete address points. See Completeness in Section 2 of this metadata for more information.<br/><br/>The data used in this aggregated dataset are compliant with the Address Point Data Standard for Minnesota.<br/><br/><br/><br/>For specific questions regarding centerline alignments or attributes, please contact the county below <br/>Anoka: <br/>Carver: <br/>Chisago:<br/>Dakota: <br/>Hennepin: <br/>Isanti: <br/>Ramsey: <br/>Scott:<br/>Sherburne: <br/>Washington:

Additional Info

Field Value
dsAccessConst None. This dataset is public domain under the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). If the dataset is not available from the Online Linkage in Section 6, please contact the Distribution Contact Person.
dsCurrentRef This dataset is collected and aggregated nightly although Counties submit data to the aggregate at different intervals depending on their internal workflows.

Users may refer to the EDITED_DT (Edited Date) field to view the date of initial entry or last record change for each record.

Change Log:
-LST_.. fields are being ignored in the schema check within used in the address points validation workflow. The Council is dynamically populating these fields during aggregation and therefore will be ignored when validating. Those not participating in metro aggregation workflow can remove LST_.. fields from the defaultFields list variable within the def CheckSchema module 3/29/2021

dsModifiedDate 2024-02-29 00:18:24
dsOriginator Municipalities and Counties in the Twin Cities metropolitan area.
dsPurpose To view, query and analyze address point data anywhere it is available in the seven county metro area and Chisago county as well as to have a single, authoritative source of the official address for any location
gdrsDsGuid {c30593a3-2960-4d25-beea-fd4a1f1c3436}
spatial {"type":"Polygon","coordinates":[[[-94.012, 44.471],[-94.012, 45.415], [-92.732, 45.415], [-92.732, 44.471], [-94.012, 44.471]]]}

Dataset extent

Tiles © Esri — Esri, DeLorme, NAVTEQ, TomTom, Intermap, iPC, USGS, FAO, NPS, NRCAN, GeoBase, Kadaster NL, Ordnance Survey, Esri Japan, METI, Esri China (Hong Kong), and the GIS User Community