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.

Attributes (Fields) Defined:Site Name: A name for the site. Each parcel is part of a site. Sites are an assemblage of one or more parcels that generally share geographic proximity and are marketed together as a unit. Many sites are just one parcel, but when they are more than one parcel, the parcel name (above) reflects this. Parcels within a site will share the same basic name, but be differentiated by a "#1", "#2", "#3", etc. appended to the end of the parcel name. The site name is the parcel name without the numbering at the end. In this way, in ArcGIS, a dissolve on the site name field can be run to produce an analysis by site, instead of by parcel.Alternate Site Names: Names that have been commonly used for the site, beyond the name specified in the "Site Name" field.Address: An address for a site shared by all parcels that comprise a site. This is derived from one of the parcel addresses for parcels that comprise the site, or from the addresses assigned by Public Works within a parcel, as can be seen in AMANDA or the PED Staff Map. If all parcel addresses have a street number of "0" because they are vacant, this field is to include a rough description of where the site is located in the city.Alternate Site Addresses: Additional addresses used to describe the site. This is derived from one of the parcel addresses for parcels that comprise the site. Ward: The Ward in which the site is located. This field is updated every ten years to reflect changes to Ward boundaries due to redistricting. CHOICES: 1 • 2 • 3 • 4 • 5 • 6 • 7Planning District: The number of the Planning District in which the Site is located. The City is divided into seventeen planning districts, each served by a city-funded and city-recognized District Council. CHOICES: 1 • 2 • 3 • 4 • 5 • 6 • 7 • 8 • 9 • 10 • 11 • 12 • 13 • 14 • 15 • 16 • 17General Description: A general description of the site, its history, current circumstances, and anything else of a summary nature that would not easily fit in other fields.Classification: This is the core means of classifying HRA-owned properties, the way the sites are marketed or not marketed, and the HRA's intended destiny for the parcels. CHOICES: Commercial - Pending Sale: Properties that are generally zoned to allow a range of commercial uses, and currently have an active offer, option, or tentative developer status.Commercial - Sold: Properties that were generally zoned to allow a range of commercial uses when last owned by the HRA, were previously owned by the HRA but that have been sold, and where the HRA retains no ownership interest.Commercial - Vacant Land: Properties that are generally zoned to allow a range of commerical uses, and have no known building or other structure.Commercial - with Building(s): Properties that are generally zoned to allow a range of commercial uses, and contain a building or other structure.Long-Term Hold: Properties that, per contractual obligations, or for other reasons, are expected to be held by the City of Saint Paul for many years, and not generally available for purchase.Long-Term Hold - Parking: Properties that are expected to be held by the City of Saint Paul for many years as parking facilities, and are not generally available for purchaseResidential - Pending Sale: Properties that are generally zoned to allow mainly residential uses, and currently have an active offer, option, or tentative developer status.Residential - Sold: Properties that were generally zoned to allow mainly residential uses when last owned by the HRA, that were previously owned by the HRA but that have been sold, and where the HRA retains no ownership interest.Residential - Vacant Land: Properties that are generally zoned to allow mainly residential uses, and have no known building or other structure.Residential - With Building(s): Properties that are generally zoned to allow mainly residential uses, and contain a building or other structure.Transfer to Other Ownership: Properties that are intended for conveyance to other ownership, such as parkland that is ultimately intended to be conveyed to the Department of Parks & Recreation, or right-of-way that most appropriately would be held by the Department of Public Works.Current Project Manager: The name of the staff responsible for managing the parcel and its future. CHOICES: Names of PED staff.SharePoint Link: A link to SharePoint storage for files related to this specific site.CharacteristicsCharacteristics - Land Assembly Considerations: Are there special considerations that apply to this site around land assembly? CHOICES: Yes • No.Characteristics - Land Assembly Considerations - Challenges & Resolutions: A description of challenges and potential resolutions around land assembly.Characteristics - Title Type: A description of the type of legal title document(s) that apply to the site. A site may have multiple title documents because it can be comprised of multiple parcels. CHOICES: Abstract • Abstract & Unknown • Torrens • Torrens & Unknown • UnknownCharacteristics - Title Issues: Are there concerns with establishing appropriate title to the project? CHOICES: Yes • NoCharacteristics - Title Challenges and Resolutions: A description of the challenges and potential resolutions around title issues.Characteristics - Estimated Market Value - Tax Year: The year for which the estimated market values (EMVs) shown in subsequent fields is used to calculate the site's total tax liability.Characteristics - Estimated Market Value - EMV Year: The year to which the estimated market values (EMVs) shown in subsequent fields applied as a representation of the site's value.Characteristics - Estimated Market Value - Land: The estimated market value (EMV) of the site's land, as determined by the Ramsey County Assessor's office, and derived from the Ramsey County Parcel Service. The Site EMV Land is obtained by adding together the individual EMV Land values for each parcel within the site. This is updated at least once per year in order to stay reasonably current with any data updates.Characteristics - Estimated Market Value - Building: The estimated market value (EMV) of the site's built structure(s), as determined by the Ramsey County Assessor's office, and derived from the Ramsey County Parcel Service. The Site EMV Building is obtained by adding together the individual EMV Building values for each parcel within the site. This is updated at least once per year in order to stay reasonably current with any data updates.Characteristics - Estimated Market Value - Total: The estimated market value (EMV) of the site's land and built structure(s), added together, as determined by the Ramsey County Assessor's office and derived from the Ramsey County Parcel Service. The Site EMV Total is obtained by adding together the individual EMV Total values for each parcel within the site. This is updated at least once per year in order to stay reasonably current with any data updates.Characteristics - Estimated Market Value - Challenges & Resolutions: A description of challenges and potential resolutions around the site's estimated market value.Characteristics - Access to Site - Support for Redevelopment: Are there issues with site accessibility? CHOICES: Yes • NoCharacteristics - Access to Site - Challenges & Resolutions: A description of challenges and potential resolutions around how site access inhibits redevelopment.Characteristics - Dimensions - Acres: The acreage of the site, as derived from the parcel geometry in GIS.Characteristics - Dimensions - Maximum Depth: The maximum depth of the site(generally measured back perpendicular from the primary street frontage).Characteristics - Dimensions - Maximum Width: The maximum width of the site (generally measured as the distance parallel to the primary street frontage).Characteristics - Dimensions - Rectangular: Is the site generally rectangular in shape? CHOICES: Yes • NoCharacteristics - Dimensions - Challenges and Resolutions: A description of challenges and potential resolutions around how site dimensions may inhibit redevelopment.Characteristics - Existing Buildings - Total Square Feet: The total square footage of the existing building(s) on the site.Characteristics - Existing Buildings - Footprint Square Feet: The building footprint square footage of the existing building(s) on the site.Characteristics - Existing Buildings - Challenges & Resolutions: A description of challenges and potential resolutions around existing buildings on the site.Characteristics - Uses - Current Use: A description of the current use on the site's parcel(s) pulled from the "LandUseCodeDescription" in the parcel feature class of the parcels that are part of the site.Characteristics - Uses - Neighboring Uses: A description of the current use directly adjacent to the site's parcel(s) pulled from the "LandUseCodeDescription" in the parcel feature class of the parcels that are part of the site.Characteristics - Uses - Restrictions: A description of any use restrictions applicable to the site upon sale.Characteristics - Uses - Funds Used: A description of the funds used and amounts on the site for acquisition and other purposes. The date on which this analysis is valid is to be denoted within the narrative description. This field is a stopgap measure until we develop better reporting mechanisms from Quickbooks and/or Infor that would more optimally pull live data from these systems of record.Characteristics - Amount of CDBG Used: The total amount of CDBG funding that has been used by the HRA on the site(which should also be accounted for in the prior field). This field is a stopgap measure until we develop better reporting mechanisms from Quickbooks and/or Infor that would more optimally pull live data from these systems of record.Characteristics - Uses - Challenges & Resolutions: A description of challenges and potential resolutions related to the existing use of the

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.

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.

We collected open and publicly available data resources from the web from administrative, county- or state-level institutions in the United States and integrated and harmonized cadastral parcel data, tax assessment data, and building footprint data for 33 counties, where building footprint data and building construction year information was available. The result of this effort is a unique dataset which we call the Multi-Temporal Building Footprint Dataset for 33 U.S. Counties (MTBF-33). MTBF-33 contains over 6.2 million building footprints including their construction year, and is available in ESRI Shapefile format (Spatial reference system: SR-ORG:7480), organized per county. We compared the MTBF-33 dataset quantitatively to other building footprint data sources, achieving an overall F-1 score of 0.93. Moreover, we compared the MTBF-33 dataset qualitatively to urban extents from historical maps and find high levels of agreement. The MTBF-33 dataset can be used to support historical building stock assessments, to derive retrospective depictions of built-up areas from 1900 to 2015, at fine spatial and temporal grain and can be used for data validation purposes, or to train statistical learning approaches aiming to extract historical information on human settlements from remote sensing data, historical maps, or similar data sources.

Data sources: Boulder County (Colorado) Open Data Catalog / Florida Geographic Data Library / Hillsborough County, Florida / City of Tampa / Manatee County, Florida / Sarasota County, Florida / City of Evansville, Vanderburgh County, Indiana / Baltimore County Government, Maryland / Bureau of Geographic Information (MassGIS), Commonwealth of Massachusetts, Executive Office of Technology and Security Services / City of Boston / MetroGIS, Minnesota Geospatial Commons, Minnesota Geospatial Information Office, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, and Washington County, Minnesota / Monmouth County, New Jersey / City of New York / Mecklenburg County, North Carolina. Data scraping was performed in 2016.

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.

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.

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.

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.

This dataset contains federal, state, county & municipal platted right of ways.Right of Way boundaries support many functions including automated half and quarter section map production, thematic mapping, land records and property assessment, and surveying and engineering projects.

Water lines in this dataset support many functions including thematic mapping, land records, property assessment, and surveying and engineering projects. Additional attributes are included to aid in linking to non-County resources.