This file geodatabase contains parcel data including plat boundaries, tax parcels, easements and road right of ways. Attributed Parcel Point and Polygon data represent property descriptions (legal descriptions) and land ownership in Ramsey County joined to tax parcels.

The following links can be used to obtain individual metadata pages:

Attributed Parcel Point: plan_attributedparcelpoint.html
Attributed Parcel Poly: plan_attributedparcelpoly.html
Common Interest: plan_commoninterest.html
Subdivision: plan_subdivision.html
Tax Parcels: plan_taxparcel.html
Manufactured Home: plan_manufacturedhome.html
Personal Property: plan_personalproperty.html
Real Property: plan_realproperty.html
State Assessed Property: plan_stateassessedproperty.html
Conveyance Division: plan_conveyancedivision.html
Special Survey: plan_specialsurvey.html
Parcel Info: plan_parcelinfo.html
Easement: plan_easement.html
Landtie: plan_landtie.html
Right of Way: plan_rightofway.html
Historic Right of Way: plan_historicrightofway.html

This dataset contains miscellaneous linework that assists with map creation and clarification. Examples of graphical features represented in this database are: old or vacated lot lines, lines, right of way and plat boundary extension lines.The parcel information data layer represents various parcel related graphical elements, which aid in the understanding and interpretation of map features. It is not intended to be inclusive. It is intended to act as a visual aid to help with map interpretation.

This dataset contains linework that represents landties. These are lines with hooked ends that help define parcel ownership on maps. The landtie data represents graphical elements, which aid in the understanding and interpretation of map features. It is not intended to be inclusive. It is intended to act as a visual aid to help with map interpretation.

This dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

This is an annual version of the MetroGIS Regional Parcel Dataset that can be used with other annual versions to do change analysis and time series investigations. This dataset is intended to contain all updates to each county's parcel data through the end of 2004. It was originally published as the 'January 1, 2005' version of the dataset. See the Currentness Reference below and the Entity and Attribute information in Section 5 for more information about the dates for specific aspects of the dataset.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

Polygon and point counts for each county are as follows (based on the January, 2005 dataset):

Anoka = 124,042 polygons, 124,042 points
Carver = 32,910 polygons, 32,910 points
Dakota = 130,989 polygons, 141,444 points
Hennepin = 353,759 polygons, 399,184 points
Ramsey = 148,266 polygons, 163,376 points
Scott = 49,958 polygons, 49,958 points
Washington = 93,794 polygons, 96,570 points

This is a MetroGIS Regionally Endorsed dataset.

Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2004 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

UPDATED As of Sept 13, 2022 we have changed some of our attributes. The most significant changes involve fields that began with Primary Tax Payer and Alternate Tax Payer now start with Owner and Tax Payer, respectively.Attributed Parcel Polygons have boundaries that represent property descriptions (legal descriptions) and land ownership. The attribute fields are based on ones provided in Ramsey County Users Group shapefiles, ParPts and OnLineCore, and MetroGIS Parcel Datasets. These fields are populated from a compilation of records and information from various state, county and city offices, and other sources. This data is joined to Ramsey County's Parcel data using a property identification number (PIN) which is assigned to both polygons and points and is the primary link to county tax and assessment data. In 1986, parcels were digitized from hand drawn 1:2400 half and 1:1200 quarter section maps. In 1995, the parcel data layer was converted to ArcINFO format and held in the ArcStorm data base. Parcels were converted in 2005 to an ESRI ArcGIS GeoDatabase. In 2013, Attributes, which were previously joined only to Parcel Points, were added to Parcel Polygons. Parcel Points are used to represent the one-to-many relationship that Common Interest Communities (CIC), Apartment Ownerships or Condominiums, as well as Manufactured Homes and Apartment Units have with the Parcel Polygons. Polygons associated with CICs, Apartment Ownerships and Condominiums use the smallest Parcel Point PIN as their PIN and have attribute data limited information that is not unit specific (e.g., tax payer name and address information, tax and estimated market values are omitted). There are a few cases where polygons exist but there is no associated point, these include common areas associated with a CIC, parks or water; no official PIN exists for these polygons and there is no attribute data.

Common Interest boundaries support many functions including automated half and quarter section map production, thematic mapping, land records and property assessment, and surveying and engineering projects.

This dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

Polygon and point counts for each county are as follows (based on the January, 2007 dataset):

Anoka = 129,392 polygons, 129,392 points
Carver = 37,021 polygons, 37,021 points
Dakota = 135,586 polygons, 148,952 points
Hennepin = 358,064 polygons, 419,736 points
Ramsey = 148,967 polygons, 166,280 points
Scott = 54,741 polygons, 54,741 points
Washington = 97,922 polygons, 102,309 points

This is a MetroGIS Regionally Endorsed dataset.

Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2006 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

In 1986, parcel polygons [PARPOLY] were digitized from hand drawn 1:2400 half and 1:1200 quarter section maps. In 1995, the parcel data layer was converted to an ArcINFO format and held in an ArcStorm database. Parcel polygons were converted in 2005 to an ESRI ArcGIS SDE GeoDatabase; the name was changed to Parcel Components. In 2014, Ramsey County migrated to ESRI's Parcel Fabric; Conveyance Divisions were created from the Parcel Components.

Surficial geology map.

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate systems from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties. Summary attribute information is in the Attributes Overview. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

Polygon and point counts for each county are as follows (Updated annually, current as of 12/31/2016):

polygons / points
Anoka - 131708 / 131708
Carver - 41204 / 41203
Dakota - 142121 / 154945
Hennepin - 430449 / 430449
Ramsey - 158207 / 166343
Scott - 56533 / 56533
Washington - 106849 / 106849

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = http://www.hennepin.us/gisopendata
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

Address points represent individual addressed locations as determined by the Local Addressing Authority. This authority rest in the municipal government in Ramsey County, and the municipalities assist in the maintenance of this information. The original source of many of these points came from the centroid of tax parcels with known situs addresses. In some locations this data has been enhanced to cases where a tax parcel may have multiple addresses (such as in some apartment units).

This data shows the rough location of all historic sites in the City of Saint Paul, along with basic information about each site. Importantly, these sites are drawn with boundaries that often follow parcel boundaries, but if true to the original nomination they would follow a dfferent geography that has not been taken into account here. To be certain about the exact boundaries for any one historic sites, one would need to refer to the appropriate documentation, which usually is included in the original designation materials. Attributes (Fields) Defined:Inventory ID: A unique identifier used by the Minnesota State Historic Preservation Office for each historic site.Related Inventory IDs: See Inventory ID above for a general description; this field captures any related sites under other Inventory IDs.PIN: The key Property Identification Number (PIN) used by Ramsey County Property Records and Revenue for the site (this field only last updated in about 2015).Name: The common name for the site.Address: The street address for the site, or if none is available, a general description of its geographic location.Historic Listing: This is the level on which the property is listed (local, state, national, or some combination of those).Year added as National Historic Landmark: The year that the property was added as a National Historic Landmark.Year added to National Register of Historic Places: The year that the property was added to the National Register of Historic Places.Year added to the State Register of Historic Places: The year that the property was added to the State Register of Historic Places.Year added as a Local Heritage Preservation Site: The year that the property was added as a Local Heritage Preservation Site.Maintenance and Update Frequency: In the case of local sites, this data would be updated as new historic sites are added. In the case of state or national designations, as new historic sites are made known to the City of Saint Paul, or as details about these sites change.

Easement boundaries support many functions including automated half and quarter section map production, thematic mapping, land records and property assessment and surveying and engineering projects.

Tax Parcel boundaries represent property descriptions (legal descriptions) and land ownership boundaries. A twelve character property identification number (PIN) is assigned to these parcels. The ParcelID is used as a primary link to county tax and assessment data. An attributed version of Tax Parcels is called AttributedParcelPoly.

Fugro Horizons Inc. acquired highly accurate Light Detection and Ranging (lidar) elevation data for the Twin Cities metropolitan region in east-central Minnesota in Spring and Fall 2011, with some reflights in Spring 2012. The data cover Anoka, Benton, Carver, Dakota, Goodhue, Hennepin, Isanti, Kanabec, Meeker, Mille Lacs, Morrison, Ramsey, Scott, Sherburne and Washington counties.

Most of the data was collected at 1.5 points/square meter. Smaller areas were collected with 2 points/square meter and with 8 points/square meter:
1. 1.5 points/square meter covers Morrison, Mille Lacs, Benton, Isanti, Sherburne, Anoka, Meeker, Hennepin, Washington, Carver, Scott, and Goodhue counties.
2. 2 points/square meter covers the Dakota Block (southern 2/3 of Dakota County)
3. 8 points/square meter covers portions of Minneapolis/St. Paul and the City of Maple Grove
See map of block boundaries: https://www.mngeo.state.mn.us/chouse/elevation/metro_data_delivery_dates.pdf

Data are in the UTM Zone 15 coordinate system, NAD83 (HARN), NAVD88 Geoid09, meters. The tiling scheme is 16th USGS 1:24,000 quadrangle tiles.

The vendor delivered the data to the Minnesota Department of Natural Resources (DNR) in several formats:

1. One-meter digital elevation model
2. Edge-of-water breaklines
3. Classified LAS formatted point cloud data

DNR staff quality-checked the data and created three additional products: two-foot contours, building outlines and hillshades.

This metadata record was created at the Minnesota Geospatial Information Office using information supplied by the vendor and by DNR.

In 1986, parcel polygons [PARPOLY] were digitized from hand drawn 1:2400 half and 1:1200 quarter section maps. 1995, the parcel data layer was converted to an ArcINFO format and held in an ArcStorm database. Parcels polygons were converted in 2005 to an ESRI ArcGIS SDE GeoDatabase. In 2014, Ramsey County migrated to ESRI's Parcel Fabric; Government Lots were created from the Parcel Components.

This data set contains polygons that represent Municipal boundaries. The Municipal boundaries were originally digitized from MNDOT municipality maps. Over time, these boundaries have been edited to better match Ramsey County parcel data.

UPDATED As of Sept 13, 2022 we have changed some of our attributes. The most significant changes involve fields that began with Primary Tax Payer and Alternate Tax Payer now start with Owner and Tax Payer, respectively.Attributed Parcel Point contains data fields previously contained in Ramsey County Users Group shapefiles, ParPts and OnLineCore, and MetroGIS Parcel Datasets. These fields are populated from a compilation of records and information from various state, county and city offices, and other sources. This data is joined to Ramsey County's Parcel Point data using a property identification number (PIN) which is assigned to both polygons and points and is the primary link to county tax and assessment data. In 1986, parcels were digitized from hand drawn 1:2400 half and 1:1200 quarter section maps. In 1995, the parcel data layer was converted to ArcINFO format and held in the ArcStorm data base. Parcel Points were created from parcel centroids. Parcel Points were converted in 2005 to an ESRI ArcGIS GeoDatabase. When Parcel Points were originally created, there was a one-to-one relationship with identical PINs on both Parcel Polygons and Parcel Points with additional Parcel Points added for Common Interest Communities, Apartment Ownerships or Condominiums, where there is a one-to-many relationship with the Parcel Polygon having the smallest PIN for all associated Parcel Points. Parcel Points were also added for Manufactured Homes and are being added for Apartment Units. The PIN for Manufactured Homes contains a number for the Manufactured Home Park followed by an M then a unique number. The PIN for Apartments Units begins with a U and is followed by the PIN for the Parcel Polygon; attribute data for Apartment Units consists primarily of site address information. The Attributed Parcel Point field, TaxParcelID, can be used to identify the associated Parcel Polygon based on its PIN, and ParcelCode can be used to identify if there is a one-to-many relationship between the point & polygon features.

Feature layer generated from running the Merge Layers solution.

This data set contains polygons that represent sections. In 1985, Ramsey County began a 5 year project to modernize it's land records mapping system to create a computerized Land Information System. As part of the project, the County developed an accurate coordinate control base for this mapping system. The 27 existing State and Federal first order accuracy positions in Ramsey County were densified by a GPS (Global Positioning System) Network of 171 second order accuracy positions. These positions were established and recorded on existing public land survey corner monuments and accessory monuments through out the county.