This layer contains address point features which are used for geocoding addresses and property identification numbers. Data attributes include property addresses and property identification numbers. Addresses are stored in both parsed and concatenated fields.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Address%20Points.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this data set, including errors, omissions, corrections and/or updates should be directed to the Hennepin County GIS Office at 612-596-9484.

© This data set was created by Hennepin County Resident and Real Estate Services Survey Division, and modified by the Hennepin County GIS office.

Field DefinitionsPIN13 digit tax ID for parcelANUMBERAddress numberANUMBERSUFAddress number suffixST_PRE_DIRStreet direction that comes before street nameST_NAMEStreet nameST_TYPEType of street (Ave, St, Ln etc.)ST_POST_DIRStreet direction that comes after the street nameAUNITUnit number of addressZIPCODEPostal codeFORMATTED_ADDRESSFull mailing addressOWNERNAMEName of property ownerTAXPAYER1Taxpayer nameTAXPAYER2Taxpayer name and addressTAXPAYER3Taxpayer name and address continuedTAXPAYER4Taxpayer name and address continuedASSESSMENT_YEARYear for which the property value is assessedTAX_YEARYear for which the property taxes are duePLATPlat numberPROPERTY_TYPEType of propertyMAIN_PTProperty type on primary use of parcelSUB_PT1Property type of secondary use of parcelSUB_PT2Property type of tertiary use of parcelSUB_PT3Property type of quaternary use of parcelMULTIPLE_USESIndicates whether parcel has multiple uses or notTAX_EXEMPTIndicates whether parcel is tax exemptEXEMPTCD1Exempt code for first tax exempt portionEXEMPTCD2Exempt code for second tax exempt portionEXEMPTCD3Exempt code for third tax exempt portionEXEMPTCD4Exempt code for fourth tax exempt portionPARCEL_AREA_SQFTLand area of parcel in square feetXX coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)YY coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)NEIGHBORHOODName of neighborhood the property is inCOMMUNITYName of community the property is inWARDName of ward the property is inZONINGName of zoning district the property is inLANDUSEProperty's land use designationLANDVALUEProperty's assessed land value as of January 2 of its assessment yearBUILDINGVALUEProperty's assessed building value as of January 2 of its assessment yearTOTALVALUEProperty's total assessed value as of January 2 of its assessment yearEXEMPTSTATUSIndicates the status of property (if exempt)HOMESTEADIndicates whether property is homesteadedBLDG_IDUnique identifier for buildingsBUILDINGUSEUse classification of buildingYEARBUILTYear that the building was constructedBELOWGROUNDAREATotal square footage below gradeABOVEGROUNDAREATotal square footage above gradeNUM_STORIESNumber of stories in buildingGARAGE_PRESENTIndicates whether property has a garagePRIMARYHEATINGPrimary type of heating in buildingCONSTRUCTIONTYPEStyle of constructionEXTERIORTYPEExterior finish of buildingROOFStyle of roofTOTAL_UNITSTotal number of unitsFIREPLACESNumber of fireplacesBATHROOMSNumber of bathroomsBEDROOMSNumber of bedrooms

2010 US Census block boundaries attributed with a subset of the PL94-171 demographic data released March 2011. Please contact the Hennepin GIS Office if you require additional PL94-171 fields. Downloaded the 2010 US Census block boundary shapefile from the US Census Bureau at the following address: http://www.census.gov/cgi-bin/geo/shapefiles2010/main Downloaded the PL94-171 demographic data from the following address: http://www.census.gov/rdo/data/2010_census_redistricting_data_pl_94-171_summary_files.html Post processed the demographic data per instructions. Stored in Access database. Set up SQL Query to create a subset of the data based on feedback from HSPHD and the GIS Office. Database documentation on file at the GIS Office. Imported the shapefile and demographic data into a File geodatabase. Joined and saved the data sets. Performed error checking by comparing against State and Maptitude versions. The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/2010%20Census%20Blocks.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© Hennepin County GIS Office This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

Field DefinitionsPIN13 digit tax ID for parcelANUMBERAddress numberANUMBERSUFAddress number suffixST_PRE_DIRStreet direction that comes before street nameST_NAMEStreet nameST_TYPEType of street (Ave, St, Ln etc.)ST_POST_DIRStreet direction that comes after the street nameAUNITUnit number of addressZIPCODEPostal codeFORMATTED_ADDRESSFull mailing addressOWNERNAMEName of property ownerTAXPAYER1Taxpayer nameTAXPAYER2Taxpayer name and addressTAXPAYER3Taxpayer name and address continuedTAXPAYER4Taxpayer name and address continuedASSESSMENT_YEARYear for which the property value is assessedTAX_YEARYear for which the property taxes are duePLATPlat numberPROPERTY_TYPEType of propertyMAIN_PTProperty type on primary use of parcelSUB_PT1Property type of secondary use of parcelSUB_PT2Property type of tertiary use of parcelSUB_PT3Property type of quaternary use of parcelMULTIPLE_USESIndicates whether parcel has multiple uses or notTAX_EXEMPTIndicates whether parcel is tax exemptEXEMPTCD1Exempt code for first tax exempt portionEXEMPTCD2Exempt code for second tax exempt portionEXEMPTCD3Exempt code for third tax exempt portionEXEMPTCD4Exempt code for fourth tax exempt portionPARCEL_AREA_SQFTLand area of parcel in square feetXX coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)YY coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)NEIGHBORHOODName of neighborhood the property is inCOMMUNITYName of community the property is inWARDName of ward the property is inZONINGName of zoning district the property is inLANDUSEProperty's land use designationLANDVALUEProperty's assessed land value as of January 2 of its assessment yearBUILDINGVALUEProperty's assessed building value as of January 2 of its assessment yearTOTALVALUEProperty's total assessed value as of January 2 of its assessment yearEXEMPTSTATUSIndicates the status of property (if exempt)HOMESTEADIndicates whether property is homesteadedBLDG_IDUnique identifier for buildingsBUILDINGUSEUse classification of buildingYEARBUILTYear that the building was constructedBELOWGROUNDAREATotal square footage below gradeABOVEGROUNDAREATotal square footage above gradeNUM_STORIESNumber of stories in buildingGARAGE_PRESENTIndicates whether property has a garagePRIMARYHEATINGPrimary type of heating in buildingCONSTRUCTIONTYPEStyle of constructionEXTERIORTYPEExterior finish of buildingROOFStyle of roofTOTAL_UNITSTotal number of unitsFIREPLACESNumber of fireplacesBATHROOMSNumber of bathroomsBEDROOMSNumber of bedrooms

Field DefinitionsPIN13 digit tax ID for parcelANUMBERAddress numberANUMBERSUFAddress number suffixST_PRE_DIRStreet direction that comes before street nameST_NAMEStreet nameST_TYPEType of street (Ave, St, Ln etc.)ST_POST_DIRStreet direction that comes after the street nameAUNITUnit number of addressZIPCODEPostal codeFORMATTED_ADDRESSFull mailing addressOWNERNAMEName of property ownerTAXPAYER1Taxpayer nameTAXPAYER2Taxpayer name and addressTAXPAYER3Taxpayer name and address continuedTAXPAYER4Taxpayer name and address continuedASSESSMENT_YEARYear for which the property value is assessedTAX_YEARYear for which the property taxes are duePLATPlat numberPROPERTY_TYPEType of propertyMAIN_PTProperty type on primary use of parcelSUB_PT1Property type of secondary use of parcelSUB_PT2Property type of tertiary use of parcelSUB_PT3Property type of quaternary use of parcelMULTIPLE_USESIndicates whether parcel has multiple uses or notTAX_EXEMPTIndicates whether parcel is tax exemptEXEMPTCD1Exempt code for first tax exempt portionEXEMPTCD2Exempt code for second tax exempt portionEXEMPTCD3Exempt code for third tax exempt portionEXEMPTCD4Exempt code for fourth tax exempt portionPARCEL_AREA_SQFTLand area of parcel in square feetXX coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)YY coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)NEIGHBORHOODName of neighborhood the property is inCOMMUNITYName of community the property is inWARDName of ward the property is inZONINGName of zoning district the property is inLANDUSEProperty's land use designationLANDVALUEProperty's assessed land value as of January 2 of its assessment yearBUILDINGVALUEProperty's assessed building value as of January 2 of its assessment yearTOTALVALUEProperty's total assessed value as of January 2 of its assessment yearEXEMPTSTATUSIndicates the status of property (if exempt)HOMESTEADIndicates whether property is homesteadedBLDG_IDUnique identifier for buildingsBUILDINGUSEUse classification of buildingYEARBUILTYear that the building was constructedBELOWGROUNDAREATotal square footage below gradeABOVEGROUNDAREATotal square footage above gradeNUM_STORIESNumber of stories in buildingGARAGE_PRESENTIndicates whether property has a garagePRIMARYHEATINGPrimary type of heating in buildingCONSTRUCTIONTYPEStyle of constructionEXTERIORTYPEExterior finish of buildingROOFStyle of roofTOTAL_UNITSTotal number of unitsFIREPLACESNumber of fireplacesBATHROOMSNumber of bathroomsBEDROOMSNumber of bedrooms

This dataset contains the planned and existing Hennepin County on and off-street bikeway system as defined by the 2040 Bicycle Transportation Plan. The current Hennepin County and Three rivers Park District bikeway system includes 594 miles of off-street bikeways and 285 miles of on-street bikeways. This dataset includes regional, municipal, state and county bikeways part of the Hennepin County bicycle network (as shown in the Bike Plan) but does not represent all on- and off-street bikeways in Hennepin County. Additionally, this dataset includes pedestrian facilities, and sidewalks located along county roadways. Link to attribute table information: http://gis.hennepin.us/OpenData/Metadata/Bikeways.pdf Filtering the dataset:Many facilities accommodate shared bicycle and pedestrian uses. Use the expressions below to filter the system based on facility type. To filter the dataset so it shows the entire county bikeway system, use the following expression: FACILITY = ������������������������������������������������������������������������������������������������������������������������������������������������������������������Bike' OR FACILITY = 'Shared' To filter the dataset so it shows the entire county pedestrian system, use the following expression: FACILITY = ������������������������������������������������������������������������������������������������������������������������������������������������������������������Sidewalk' OR FACILITY = 'Shared' To filter the dataset so it shows bike-only facilities, use the following expression: FACILITY = ������������������������������������������������������������������������������������������������������������������������������������������������������������������Bike' To filter the dataset so it shows sidewalks or other pedestrian-only facilities, use the following expression: FACILITY = ������������������������������������������������������������������������������������������������������������������������������������������������������������������Sidewalk' Data updated: monthlyUse Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.General questions about this data set, including errors, omissions, corrections and/or updates should be directed to the Hennepin County GIS Office at 612-596-9484.

This dataset contains the boundary area of Hennepin County municipalities as defined from Auditor legal descriptions and tax area boundaries. It includes any annexations that may affect the corporate boundary. The NAME_TXT attribute field contains the municipality text label.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Municipal%20Boundaries.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this dataset, including errors, omissions, corrections and/or updates should be directed to the Survey Division, Resident and Real Estate Services Department, Hennepin County at 612-348-3131.

© This data set was created by Hennepin County Resident and Real Estate Services Survey Division. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

This dataset is a compilation of address point data from Minnesota suppliers that have opted-in for their address point data to be included in this dataset.

It includes the following 44 suppliers that have opted-in to share their data openly as of the publication date of this dataset: Aitkin County, Anoka County, Benton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Cook County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Koochinching County, Lac qui Parle County, Lake County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County, Otter Tail County, Pipestone County, Polk County, Pope County, Ramsey County, Renville County, Rock County, Saint Louis County, Scott County, Sherburne County, Stearns, Stevens County, Waseca County, Washington County, Wright County, and Yellow Medicine County.

The two sources of address point data are the Minnesota Next Generation 9-1-1 (NG9-1-1) Program, in collaboration with local data suppliers, and the MetroGIS Metro Address Points Dataset which is on the Minnesota Geospatial Commons:

The Minnesota NG9-1-1 Program enterprise database provides the data outside of the Metro Region which is provide by the suppliers. The data have been aggregated into a single dataset which implements the MN NG9-1-1 GIS Data Model (https://ng911gis-minnesota.hub.arcgis.com/documents/79beb1f9bde84e84a0fa9b74950f7589/about ).

Only data which have meet the requirements for supporting NG9-1-1 are in the statewide aggregate GIS data. MnGeo extracts the available data, applies domain translations, and transforms it to UTM Zone 15 to comply with the GAC Address Point attribute schema: https://www.mngeo.state.mn.us/committee/address/address_standard.html.

The MetroGIS Metro Address Points Dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne, and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. The data are pulled in from the Minnesota Geospatial Commons: https://gisdata.mn.gov/dataset/us-mn-state-metrogis-loc-address-points

‘Supplier’ is a term used throughout this document. A supplier will typically be a county, but it could also be a public safety answering point (PSAP), region, or tribal nation. The supplier is the agency which provides the individual datasets for the aggregated dataset. The loc_addresses_open_metadata feature layer will contain the geometry/shape of the supplier boundaries, supplier name, supplier type, and feature count.

Aggregation Process:
1. Transfer NG9-1-1 data from the DPS Enterprise database.
2. Download the latest data from the Geospatial Commons for MetroGIS.
3. Extract, Translate, and Load (ETL) the data to the GAC Address Point Standard schema.
4. Combine NG9-1-1 data with MetroGIS data.
5. Filter the data for the Opt-In suppliers

Dataset contains the ZIP code boundaries inside of Hennepin County. Non-taxing polygons for Zip code areas are defined using parcel attributes of property mailing address. The field NAME_TXT contains the ZIP Code number for each polygon.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Zipcodes.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this dataset, including errors, omissions, corrections and/or updates should be directed to the Survey Division, Resident and Real Estate Services Department, Hennepin County at 612-348-3131.

© This data set is maintained by Hennepin County Resident and Real Estate Services Survey Division. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

Land cover data set based on the Minnesota Land Cover Classification System (MLCCS) coding scheme. This data was produced using a combination of aerial photograph interpretation and field surveys. There is a minimum mapping unit of 1 acre for natural vegetation and 2 acres for artificial cover types.Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/MLCCS.pdf Data updated: dailyUse Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this data set, including errors, omissions, corrections and/or updates should be directed to the Hennepin County Department of Environment & Energy (612-348-3777).

Locations classified as bikeway gaps are short (1/2 mile or less) connections that are needed to ensure continuity in the bikeway system. This data corresponds with Appendix E of the Hennepin County 2040 bike plan, and shows the gap ID, initial gap score, and general planned facility type.

Link to Attribute Table Information: https://gis.hennepin.us/OpenData/Metadata/BikewayGaps.pdf

This dataset records modifications made to the MN address point data, capturing both attribute and geometry changes. Each modification, whether it involves an attribute or geometry change, is represented by a separate row/feature in the feature class. In cases where multiple attribute changes occur, each change is documented with its own entry.

- Address points
- Address geocoding;
- Next Generation 911 call routing and location validation;
- Emergency services dispatching;

For specific questions regarding centerline alignments or attributes, please contact the county below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gis@co.chisago.mn.us
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Sherburne: gis@co.sherburne.mn.us
Scott: gis@co.scott.mn.us
Washington: surveyor@co.washington.mn.us

This dataset contains City Hall locations in Hennepin County.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/City%20Halls.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© Hennepin County Emergency Management, Hennepin County GIS Office This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data.

This is a polygon dataset for county boundaries as well as for city, township and unorganized territory (CTU) boundaries in the Twin Cities 7-county metropolitan area. The linework for this dataset comes from individual counties and is assembled by the Metropolitan Council for the MetroGIS community. This is a MetroGIS Regionally Endorsed dataset https://metrogis.org/.

The County CTU Lookup Table here https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-counties-and-ctus-lookup
is also included in this dataset and contains various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them is also included in the dataset.

This dataset is updated quarterly. This dataset is composed of three shape files and one dbf table.
- Counties.shp = county boundaries
- CTUs.shp = city, township and unorganized territory boundaries
- CountiesAndCTUs.shp = combined county and CTU boundaries
- CountyCTULookupTable.dbf = various data related to CTUs and any divisions created by county boundaries splitting them is also included in the dataset, described here: https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-counties-and-ctus-lookup

NOTES:

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lake St. Croix Beach was incorrect. It was changed from 2394379 to 2395599 to match GNIS.

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lilydale was incorrect. It was changed from 2394457 to 2395708 to match GNIS.

- On 11/9/2010 it was discovered that the CTU ID used for the City of Crystal was incorrect. It was changed from 2393541 to 2393683 to match GNIS.

- Effective April 2008, a change was made in GNIS to match the FIPS place codes to the "civil" feature for each city instead of the "populated place" feature. Both cities and townships are now "civil" features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed.

- The five digit CTU codes in this dataset are identical to the Federal Information Processing Standard (FIPS) ''Place'' codes. They are also used by the Census Bureau and many other organizations and are proposed as a MN state data coding standard.

- Cities and townships have also been referred to as ''MCDs'' (a census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity.

- The boundary line data for this dataset comes from each county.

- A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport).

- Some cities are split between two counties. Only those parts of cities within the 7-county area are included.

- Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change.

This dataset is a compilation of road centerline data from Minnesota suppliers that have opted-in for their road centerline data to be included in this dataset.

It includes the following 43 suppliers that have opted-in to share their data openly as of the publication date of this dataset: Aitkin County, Anoka County, Benton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Cook County, Dakota County, Douglas County, Fillmore County, Hennepin County, Houston County, Isanti County, Itasca County, Koochinching County, Lac qui Parle County, Lake County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County, Otter Tail County, Pipestone County, Pope County, Polk County, Ramsey County, Renville County, Rock County, Saint Louis County, Scott County, Sherburne County, Stearns, Stevens County, Waseca County, Washington County, Wright County, and Yellow Medicine County.

The two sources of road centerline data are the Minnesota Next Generation 9-1-1 (NG9-1-1) Program, in collaboration with local data suppliers, and the MetroGIS Road Centerlines (Geospatial Advisory Council Schema) which is on the Minnesota Geospatial Commons:

The Minnesota NG9-1-1 Program enterprise database provides the data outside of the Metro Region which is provide by the suppliers. The data have been aggregated into a single dataset which implements the MN NG9-1-1 GIS Data Model (https://ng911gis-minnesota.hub.arcgis.com/documents/79beb1f9bde84e84a0fa9b74950f7589/about ).

Only data which have meet the requirements for supporting NG9-1-1 are in the statewide aggregate GIS data. MnGeo extracts the available data, applies domain translations, and transforms it to UTM Zone 15 to comply with the GAC road centerline attribute schema: https://www.mngeo.state.mn.us/committee/standards/roadcenterline/index.html.

The MetroGIS Road Centerlines data was created by a joint collaborative project involving the technical and managerial GIS staff from the the Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne, and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. The data are pulled from the Minnesota Geospatial Commons: https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-road-centerlines-gac

‘Supplier’ is a term used throughout this document. A supplier will typically be a county, but it could also be a public safety answering point (PSAP), region, or tribal nation. The supplier is the agency which provides the individual datasets for the aggregated dataset. The trans_road_centerlines_open_metadata feature layer will contain the geometry/shape of the supplier boundaries, supplier name, supplier type, and feature count.

Aggregation Process:
1. Extract NG9-1-1 data from the Department of Public Safety (DPS) Enterprise database.
2. Download the latest MetroGIS data from the Geospatial Commons.
3. Extract, Translate, and Load (ETL) the DPS data to the GAC schema.
4. Combine NG9-1-1 data with MetroGIS data.
5. Filter the data for the Opt-In Open data counties

Priority Natural Resource Corridors is a subset of the Hennepin County Open Space Corridors feature class. Data set illustrates the general locations of priority natural resource corridors in Hennepin County.Criteria for Priority Corridor:Natural Community Quality - Potential for Rare Species - Good to High Quality Natural AreasOther Unique and/or Ecologically Significant Areas - Moderate to High Quality Natural AreasLarge publicly and privately owned and protected open spaces (e.g. Regional Parks, Scientific and Natural Areas, Wildlife Management Areas, Waterfowl Production Areas, The Nature Conservancy, Wildlife Refuges, Conservation Easements)Connectivity - Natural corridors with natural/semi-natural areas that would serve as logical links between Ecologically Significant Areas (e.g. lakes, streams, wetland complexes, drainage ways, floodplains, steep slopes)Data Creation:The data was developed from the analyses of high resolution aerial photography and several GIS datasets, including but not limited to:Ecologically Significant Areas - a subset of the Hennepin County Minnesota Land Cover Classification SystemNational Wetland Inventory Hennepin County Wetland InventoryPublic Waters InventoryRegional ParksPermanent Conservation EasementsSoilsFEMA FloodplainsMinnesota Department of Natural Resources Scientific Natural AreasMinnesota Department of Natural Resources County Biological Survey SitesRegional Parks and other protected open spacesU.S. Fish and Wildlife Service National Wildlife Refuge System, Wildlife Management Areas and Waterfowl Protection AreasLink to Attribute Table Information: https://gis.hennepin.us/OpenData/Metadata/Priority%20Natural%20Resource%20Corridors.pdf

2010 US Census Block Groups for Hennepin County with subset of PL94-171 demographic data. The Hennepin County GIS Office downloaded US Census data from the following sites:Shapefiles:http://www.census.gov/cgi-bin/geo/shapefiles2010/main PL94-171:http://www.census.gov/rdo/data/2010_census_redistricting_data_pl_94-171_summary_files.html PL94-171 tabular data was post processed per instructions and stored in an Access database. Records and a subset of the 290 plus fields were extracted from the master tables using SQL statements. A copy of the statement has been included in the Lineage section of metadata. Tables were registered as a geodatabase and copied to a File Geodatabase. Shapefiles were imported into the File Geodatabase and projected to UTM Zone 15 N. The feature classes were joined to the tabular data and saved as the final US Census layer.The feature classes underwent visual inspection. The number of records were compared and checked. The attribute values were compared to existing Maptitude US Census data. Please contact the Hennepin GIS Office if you require additional PL94-171 fields. Hennepin County GIS Office A-705 Government Center Minneapolis, Minnesota 55487-075 GIS.Info@co.hennepin.mn.us Phone: 612-596-9484 FAX: 612-348-2837 The original metadata is contained below. The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/2010%20Census%20Block%20Groups.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© US Census Bureau. See additional information in Abstract and Use Limitations. This data was modified by the Hennepin County GIS Office. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

This dataset contains the Soil and Water District Boundaries in Hennepin County for local elections. Current boundaries are as of the 2002 redistricting for Soil and Water election districts. The field NAME_TXT contains the district identifier for each Soil and Water District.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Soil%20Water%20Districts.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this dataset, including errors, omissions, corrections and/or updates should be directed to the Survey Division, Resident and Real Estate Services Department, Hennepin County at 612-348-3131.

© This data set is maintained by Hennepin County Resident and Real Estate Services Survey Division.

The original Hennepin County Wetland Inventory (HCWI) was developed from the remote sensing of multiple years of orthophotograpy in combination with the analysis of related GIS layers and 10 years of Natural Resources Conservation Service slide reviews to identify and include farmed wetlands. The HCWI does not classify wetlands but merely locates them, whereas the NWI classifies wetlands based on the Cowardin methodology utilizing remotely gathered data and photo signature. For more information concerning detail on procedures followed to develop the HCWI contact Hennepin County Dept. of Environmental Services.National Wetland Inventory Metadata:The National Wetland Inventory (NWI) for east-central Minnesota were updated through multi-agency collaborative effort under leadership from the Minnesota DNR. Operational support for wetland mapping and classification was provided by Ducks Unlimited and support for methods development and field validation were provided by the Remote Sensing and Geospatial Analysis Laboratory at the University of Minnesota. Major funding was provided by the Environmental and Natural Resources Trust Fund. The project area consists of 13 counties in east-central Minnesota including: Anoka, Carver, Chisago, Dakota, Goodhue, Hennepin, Isanti, Ramsey, Rice, Scott, Sherburne, Washington, and Wright Counties. The updated wetland inventory area included complete coverage for all USGS quarter quadrangles that intersect any of these counties (about 7,150 square mile). The NWI classification process for east-central Minnesota consisted of three basic steps: 1) creation of image segments (polygons), 2) RandomForest classification of the segments, and 3) photo-interpretation of the classified image segments. The updated NWI also contains a Simplified Plant Community Classification and a Simplified Hydrogemorphic Classification. Quality assurance of the data included a 100% visual inspection, automated checks for attribute validity and topologic consistency, as well as a formal accuracy assessment based on an independent field verified data set. Further details on the methods employed can be found in the technical procedures document for this project (provide URL). The updated NWI data are primarily based on aerial imagery acquired in 2010 and 2011 as well as other modern ancillary data. This data is intended to replace the original NWI data which was based on imagery acquired in the early 1980s. NWI data support effective wetland management, protection, and restoration. The data provide a baseline for assessing the effectiveness of wetland policies and management actions. These data are used at all levels of government, as well as by private industry and non-profit organizations for wetland regulation and management, land use and conservation planning, environmental impact assessment, and natural resource inventories.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Wetland%20Inventory.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this data set, including errors, omissions, corrections and/or updates should be directed to the Hennepin County Department of Environment & Energy (612-348-3777).

© Hennepin County Department of Environment & Energy, Minnesota Department of Natural Resources, MN Legislative-Citizen Commission on Minnesota Resources (LCCMR), US Fish & Wildlife Service, Board of Water and Soil Resources This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

This dataset includes areas within Hennepin County that likely experienced landslide activity in historic or pre-historic times. The specific ages of the landslide activity are unknown, but likely range in the hundreds to thousands of years ago. The areas were digitized by analyzing digital elevation, hillshade and land cover data sources. The digital elevation and hillshade datasets are sourced from the metro's 2011 light detection and ranging (LIDAR) bare earth dataset. This dataset will be updated when newer LIDAR data becomes available.

Undated Landslide Types

Small slide: Areas of active erosion and multiple small slides; shallow-seated, estimated plane of failure is less than 4.5m (15ft); includes ravine sides that are subject to failure; common throughout the Lake Minnetonka region and interior of the county and along first order stream valleys and ravines.Scarp and flank: Steep head and side slopes where slide originated; deep-seated, estimated failure plane depth is greater than 4.5 m (15ft); may also include ravine heads, sapping basins, and human modified slopes; not always paired with a clear deposit.River slope: Intermediary between the large landslide and small slides and found along major rivers.Deposit: Lobe or fan-shaped area with smooth, hummocky or blocky surface expression; may include debris fans or colluvial fans; includes large historic landslides; primarily located along the major rivers and tributaries.Modified slope: Non-natural terrain in steep slope zone that may have been modified or repaired subsequent to a landslide: does not include areas of steep slopes that were clearly modified but had no indication of past landslides (e.g. highway slopes). This dataset supports the Hennepin County Landslide Atlas: Click here to visit the Hennepin County Landslide Atlas website