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.

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 2010 dataset unless otherwise noted):

polygons / points
Anoka - 129271 / 129271
Carver - 38205 / 38205
Dakota - 136067 / 150436
Hennepin - 424182 / 424182
Ramsey - 149101 / 168152
Scott - 55213 / 55213
Washington - 98933 / 104100 (October 2009)

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 2009 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

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-01-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

Codes and Regulations issues and inspects Development Permits (building, electrical, HVAC), enforces Property Maintenance Code (housing) and Land Development Code (zoning), issues ABC, taxi cab, vendor and other licenses and administers the Code Enforcement Board.

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

Develop Louisville Focuses on the full range of land development activities, including planning and design, vacant property initiatives, advanced planning, housing & community development programs, permits and licensing, land acquisition, public art and clean and green sustainable development partnerships.Data Dictionary:"Parcel ID" is an identification code assigned to a piece of real estate by the Jefferson County Property Valuation Administration. The Parcel ID is used for record keeping and tax purposes.The “status” of a real estate donation is defined by the Office of Community Development as follows:Approved - The donation of real estate is approved and is awaiting the execution of a deed to change its ownership.Closed Compl - The donation of real estate yields a recorded deed giving ownership to the Louisville and Jefferson County Landbank Authority, Inc..Closed Incompl - The accepted donation has stalled due to an unresponsive property owner.Cond Apvl - The donation of real estate is approved, but "small" title issues need to be resolved.Denied - The donation of real estate is denied due to title issues listed in a Title Search Report.Lien Waiver Inquiry - An inquiry was made by the property owner as to whether or not property maintenance liens could be waived.Pending - The donation is awaiting the results of a title search review by a license title abstractor.Pending OMB - The Office of Management & Budget must waive Metro property maintenance liens before the donation is approved.Withdrawn - The donation was withdrawn by the property owner or the title changed hands before the donation was denied/completed."Status Date" is the date on which the status of the real estate donation was set by the Office of Community Development.Contact:Connie Suttonconnie.sutton@louisvilleky.gov

Codes and Regulations inspects and enforces Property Maintenance Code (housing) , Land Development Code (zoning), and administers the Code Enforcement Board. The following data provides a list of property maintenance violations over the last 30 days.

Field Name

Field Description

SERV_PROV_CODE

Field that is used for linking the data with Accela and identifies the agency

B1_PER_ID1

Identifies the specific record for joining the data in Accela

B1_PER_ID2

B1_PER_ID3

B1_SPECIAL_TEXT

Identifies the inspection visit number

B1_ALT_ID

Record ID

FullAdress

Location of the site visit including city, state and zip

PartialAddress

Location of the site visit excluding the city, state and zip

Longitude

Point location of the site visit

Latitude

EXT_ADDRESS_UID

Identifier for joining the address to LOJIC address data

PARCEL_ID

Parcel Identifier

CouncilDist

Council District

G6A_G6_COMPL_T1

Identifies whether the inspection was completed AM or PM

G6A_G6_COMPL_T2

Identifies the time of the inspection on a 12 hour clock

G6A_G6_COMPL_DD

Is the date/time of the inspection

G6A_G6_STATUS

Inspection result of the site visit

G6A_G6_STATUS_DD

The Date when the inspection result was issued

GA_USERID

Unique identifier of the inspector

GAFML

Full Name of the inspector

OccupancyStatus

Occupancy Status of the property observed by the inspector at the time of the inspection

GUIDE_ITEM_TEXT

Description of the violation

VIOLATION_CODE

Violation Code

GUIDE_ITEM_STATUS

Individual violation status

CitationAmount

The fine levied against the property owner for violations on that inspection

ColumnCounts

Sequential Number of violations on a site visit

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-01-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

For 30 years Metro311 has been the city's customer service center.Metro311 is YOUR connection to YOUR government!Data Standards Fields: service_request_id, requested_datetime, updated_datetime, source, service_name, description, agency_responsible, address, council_district, status_description, lat, long Sample: 5088887, 2018-07-01 16:47:00, , UNKNOWN, ZONING CONCERNS, ILLEGAL BUSINESS OR SIGNS ON PRIVATE PROPERTY, IPL-PROPERTY MAINTENANCE DIV., 4708 ANDALUSIA LN LOUISVILLE KY 40272, 25, CLOSED, 38.1158171552, -85.8500655525

The Louisville Division of Fire, commonly known as the Louisville Fire Department or Louisville Fire & Rescue (abbreviated LFD or LFR), is the sole fire suppression agency for the former city of Louisville, Kentucky and is one of nineteen fire departments within the Louisville-Jefferson County, Kentucky metropolitan area. The Louisville Division of Fire is the second largest fire department in Kentucky.This data is presented in a publicly available report located HERE

Field Name

Field Description

inci_no

Incident Number

alm_date

Incident date

address

Incident address

latitude

Latitude

longtitude

Longtitude

inci_type

Incident Type

content_loss

value of items lost

property_loss

value of Fixed Property Loss

total_loss

sum value of content and property loss

pre_inci_value

fixed property preincident value

saved

differnce between fixed property preincident value and total loss

Area appearing unimproved on 2021 aerial photography, without regard to developability and accessibility. On partially developed parcels, only undeveloped areas 1/2 acre or larger are included. Metro's Vacant Land Definition: Every tax lot is determined to be vacant, partially vacant, or developed. Vacant tax lots are those that have no building, improvements or identifiable land use. Developed lots must have improvements and specific land uses. For example, a paved parking lot is developed but an unpaved lot where trucks are parked is vacant. Lots under site development are only considered developed if structure is evident. For example, earthwork and grading are considered vacant but buildings under construction (foundation or more) are considered developed. If a developed tax lot has 1/2 acre (20,000-sq. ft.) or greater portion that is vacant, the lot is considered to be partially vacant and partially developed. A polygon is delineated around the occupied portion, which includes buildings, landscaped yards, etc. The remaining portion (greater than 1/2 acre) is coded vacant (vac = 1). Parks and open spaces are treated as developed. During the assessment of each tax lot, no consideration is given to constrained land, suitability for building, or to redevelopment potential. Date of last data update: 2022-01-19 This is official RLIS data. Contact Person: Al Mowbray al.mowbray@oregonmetro.gov 503-797-1843 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3722 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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

Washington Metropolitan Area Transit Authority (WMATA) Metrorail track route for the part of the Red Line that runs through Montgomery County. For more information, contact: GIS Manager Information Technology & Innovation (ITI) Montgomery County Planning Department, MNCPPC T: 301-650-5620

Comprehensive address point file for the region. The normalized address data is a composition of imported data from regional counties and cities. Addresses are represented as individual points and are positioned inside or adjacent to taxlot parcels or on buildings within a parcel. Date of last data update: 2025-02-03 This is official RLIS data. Contact Person: Alicia Wood alicia.wood@oregonmetro.gov 503-813-7561 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/656 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

This dataset has been created to meet the needs of the research community of Arizona State University. Apart from purely vizualization purposes (i.e. displaying the data on various maps) it can potentially be used for spatial modeling. The data consist of engineering-quality contours, also known as isolines, created from the NED 10-meter Digital Elevation Model subset to the extent somewhat exceeding Cetral Arizona - Phoenix LTER. Contours ( lines connecting points of equal height above sea level) are drawn at 15 meter intervals with the base set at 145 m of elevation. Contours are an exact interpretation of the grid surface model and may sometimes appear blocky looking, may cross, appear to intersect, or form an unclosed branching line. All these are valid engineering-quality interpretations of the elevation surface that cartographers typically modify (smooth) for aesthetic purposes.

Metropolitan DivisionsThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays Metropolitan Divisions within the United States. According to the USCB, "Metropolitan Divisions subdivide a Metropolitan Statistical Area (MSA) containing a single core urban area that has a population of at least 2.5 million to form smaller groupings of counties or equivalent entities. Not all MSAs with urban areas of this size will contain Metropolitan Divisions. Not all MSAs with urban areas of this size will contain Metropolitan Divisions. Metropolitan Division are defined by the Office of Management and Budget (OMB) and consist of one or more main counties or equivalent entities that represent an employment center or centers, plus adjacent counties associated with the main county or counties through commuting ties."Nassau County-Suffolk County, NY Metro Division & New Brunswick-Lakewood, NJ Metro DivisionData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Metropolitan Divisions) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 83 (Series Information for Metropolitan Division National TIGER/Line Shapefiles, Current)OGC API Features Link: (Metropolitan Divisions - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Geographic LevelsFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

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

A shapefile was generated from ArcINFO coverages, which were in turn created by digitizing a 1968 paper map of land use in the Twin Cities Metropolitan Area. The map was originally published by the Twin Cities Metropolitan Planning Commission.

Cross sections as approved by the Federal Emergency management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM)