This layer includes all parcels owned by Louisville Metro Government and its associated entities, the Commonwealth of Kentucky and its associated entities (including state educational institutions), the Jefferson County Public Schools, Louisville/Jefferson County Metropolitan Sewer District, United States Government, and small municipalities, fire districts, and independent school districts. The data was created by as a subset of the Jefferson County Property Valuation Administrator's Real Estate Master File, by reviewing parcel ownership information contained in this data. Feature attributes indicate specific owner, area of the parcel, and if applicable, the Jefferson County Property Valuation Administrator assessed values.

County tax assessors tax lots with associated property data, excluding ownership information. Selected items from each county assessor's file are included and standardized for all three counties. The tax lot spatial features and data associated with the tax lot are compiled by Metro from existing records created and maintained by the local county assessment and taxation offices. Taxlots with rights of way are available in RLIS Discovery under the name "Taxlots with Right of Way (Public)." Due to slow download speeds regular downloads are not recommended for this layer, instead use the downloadable file under the name "Taxlots (Public) - Download." This zip file includes the taxlots shapefile and layer files for visualizing taxlots with or without right of ways. Date of last data update: 2025-10-17 This is official RLIS data. Contact Person: Christine Rutan christine.rutan@oregonmetro.gov 503-797-1669 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3733 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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

Details of property standards requests reported to Metro Codes over a rolling three-year period.Source Link: https://epermits.nashville.govMetadata Document: Property Standards Requests Metadata.pdfContact Data Owner: opendata@nashville.gov

Tax Increment Financing (TIF) is a performance-based incentive that permits a portion of the new state and/or local taxes generated by a development to be rebated back to the developer to help support the development costs. These data are for the Local Only Tax Increment Financing Zones for Louisville, KY. Visit https://louisvilleky.gov/government/louisville-forward/legal-agreements for additional information on each TIF project.Note: The property data shown on this map was digitized from PVA block maps adjusted to LOJIC planimetric map data and has been updated from PVA records. The property data does not supersede deed records and should not be used for purposes other than general property reference and identification.Field NameField DescriptionNameName of TIFProject_LinkWeb link to the Projects websiteTermHow long the TIF will be activated forApprovedThe year the TIF was approvedActivatedThe year the TIF was activated if it has been activatedPDF_LinkLink to the PDF map for the TIF

Note: The property data shown on this map was digitized from PVA block maps adjusted to LOJIC planimetric map data and has been updated from PVA records. The property data does not supersede deed records and should not be used for purposes other than general property reference and identification.Field NameField DescriptionNameName of TIF

Contains regional building footprint data from local jurisdictions or created and compiled by Watershed Sciences from regional Lidar data with average building heights. In instances where Lidar point density was insufficient to establish a footprint, Watershed Sciences either 1) digitized footprint from 2008 Ortho photography or 2) used existing footprint data provided by the Jurisdiction. For areas where data is not maintained by local jurisdictions, DOGAMI's 2018 building footprint dataset has been included. Additional digitization is performed by Metro using the most recent regional aerial orthoimagery when changes are identified during the annual vacant land review. Date of last data update: 2025-11-03 This is official RLIS data. Contact Person: Franz Arend franz.arend@oregonmetro.gov 503-797-1742 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2406 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Historic Properties, data from the Metro Landmarks Commission, Kentucky Hertiage Council, and National Register of Historic Places about National Historic Landmarks in Jefferson County, Kentucky. Revision 2 January 2007. View detailed metadata.

Additional records for taxlots that have more than one record in the county Assessor's database, without ownership information. Shown as a point file that can be overlaid on the taxlot polygon shapefile. Date of last data update: 2025-10-17 This is official RLIS data. Contact Person: Christine Rutan christine.rutan@oregonmetro.gov 503-797-1669 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3734 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

This map depicts complete boundaries of the special districts located within Centennial.It is updated directly from our LGIM database and shared on Open Data portal. This is used on our interactive map on the Centennial web site. It has been adjusted to show the Foxridge, Antelope, and Cherry Park GID's as separate layers. Refer back to our map on our web page Centennial Maps

The parcels boundaries are not legal survey accurate and should be used for general representation only. They are maintained by the Jefferson County Property Administrator's Office. To get detailed parcel information, Contact the PVA. Use the LRSN field as the unique parcel identifier. The data is updated daily. View detailed metadata.

Metropolitan Water Reclamation Taxing Districts in Cook County

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

Public Parcels - Metro CTUsThis web map was created by Metro Transit's Transit Oriented Development (TOD) Office to showcase the newly expanded public parcel data in relation to existing and planned transit facilities across the Twin Cities Metropolitan Area. As of August, 2019, the parcels can also be viewed in relation to Federally approved Opportunity Zones. More information on the new US Department of Treasury Opportunity Zone Program can be found here. The purpose of the public parcel data is to increase awareness of the location and quantity of publicly owned lands at all levels of government. The Q-1 2020 dataset now includes more than 35,000 parcels from across 128 cities, townships, and unorganized territories (CTUs). These parcels are further classified and displayed by eight broad ownership or administrative categories. Users can view, analyze, share, and research publicly-owned lands that may be good candidates for TOD or some other higher/better use.The purpose of the original pilot project was to increase awareness of publicly owned parcel locations relative to Metro-area transit facilities and facilitate TOD analyses. While the current geographic extent of the data has been greatly expanded, the purpose remains the same; to raise awareness of publicly owned land for the highest & best use.For those with desktop GIS software, the Public Parcel shapefile and/or geodatabase can be downloaded here: https://gisdata.mn.gov/dataset/us-mn-state-metc-plan-public-parcels-metro-ctus

The Land Cover Layer was developed by updating and utilizing the 1992 land cover classification and updating areas of change or areas not previously classified. The two 1991 and 1998 Landsat TM scenes were first co-registered. Once co-registered, a multi-temporal image data set was produced by combining one band from each date of imagery into a single image data set. A simple classification of this merged data identified areas that had undergone land cover change between 1991 through 1998. Digital image processing techniques were used to digitally discriminate and map those areas of significant land cover change since 1991. Once the areas of change were identified, their current land cover and land use status was classified by manual photo-interpretation. The newly classified areas were manually edited or relabeled directly on the TM imagery. This task resulted in the digital capture of updated land cover and land use information in a GIS data layer that is co-registered to the original 1992 land cover classification. Once the updated areas of change were digitally captured and mapped, the GIS layer(s) containing the updates was integrated with the existing land cover map producing a new 1998-current land cover and land use classification for the previously mapped area. Classification of any new areas in the project study area that were not previously mapped in the 1992 classification was accomplished using a combination of the 1998 Landsat TM imagery, aerial photography, and digital orthophotos. A two-acre minimum mapping unit was utilized in the updating and development of the 1998 land cover classification. This phase of the project resulted in a digital raster GIS data layer in which the entire study area is classified according to a generalized classification scheme of the 1992 land cover map. Date of last data update: 1998 This is official RLIS data. Contact Person: Joe Gordon joe.gordon@oregonmetro.gov 503-797-1587 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/880 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

This data is not recommended for downloading. Use the "Affordable Housing - Download" item to download the feature class and related table in a zipped file geodatabase. An ongoing inventory of affordable housing for the Portland metropolitan area. Intended to assist in prioritizing investment and guiding regional policymaking. Date of last data update: 2020-12-31 This is official RLIS data. Contact Person: Clint Chiavarini clinton.chiavarini@oregonmetro.gov 503-797-1738 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3432 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Outdoor areas used for recreation and conservation including parks, natural areas, golf courses, cemeteries, homeowner association owned parcels, trail parcels, school land, etc. Date of last data update: 2025-10-31 This is official RLIS data. Contact Person: Max Woodbury max.woodbury@oregonmetro.gov 503-797-1563 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2811 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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

As a certain area under the authority of an administrative agency, it provides spatial information (map) of administrative district maps (metropolitan city/province, city/county/district, town/village/dong, village) as open API according to national administrative purposes. Metropolitan city/province: Boundary map divided into special metropolitan city units. WMS name: lt_c_adsido WFS name: lt_c_adsido_info Ri: Boundary map divided into village units. WMS name: lt_c_adri WFS name: lt_c_adri_info Si/gun/gu: Boundary map divided into city/county/district units. WMS name: lt_c_adsigg WFS name: lt_c_adsigg_info Eup/myeon/dong: Boundary map divided into town/village/dong units. WMS name: lt_c_ademd WFS name: lt_c_ademd_info

Points representing the locations of known active addresses in the Portland Metro Region. Addresses been culled from the City of Portland Master Address Repository, Multnomah County Assessor Records and the RLIS Master Address Points dataset.This dataset contains active addresses - those that are currently in use in the Portland Metro Region.The Schema of this dataset is built to match legacy address datasets to support existing applications and tools.--Additional Information: Category: Address Purpose: For mapping, geocoding, mailing, and analysis of addresses in the Portland Metro Region. Update Frequency: Weekly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52064