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.

TheFlorida Department of Revenue’s Property Tax Oversight(PTO) program collects parcel level Geographic Information System (GIS) data files every April from all of Florida’s 67 county property appraisers’ offices. This GIS data was exported from these file submissions between March 15 to April 1, 2023. The GIS parcel polygon features have been joined with thereal property roll (Name – Address – Legal, or NAL)file. No line work was adjusted between county boundaries.The polygon data set represents the information property appraisers gathered from the legal description on deeds, lot layout of recorded plats, declaration of condominium documents, recorded and unrecorded surveys.Individual parcel data is updated continually by each county property appraiser as needed. The GIS linework and related attributions for the statewide parcel map are updated annually by the Department every August. The dataset extends countywide and is attribute by Federal Information Processing Standards (FIPS) code.DOR reference with FIPS county codes and attribution definitions - https://fgio.maps.arcgis.com/home/item.html?id=ff7b985e139c4c7ba844500053e8e185If you discover the inadvertent release of a confidential record exempt from disclosure pursuant to Chapter 119, Florida Statutes, public records laws, immediately notify the Department of Revenue at 850-717-6570 and your local Florida Property Appraisers’ Office.Please contact the county property appraiser with any parcel specific questions: Florida Property Appraisers’ Offices:Alachua County Property Appraiser – https://www.acpafl.org/Baker County Property Appraiser – https://www.bakerpa.com/Bay County Property Appraiser – https://baypa.net/Bradford County Property Appraiser – https://www.bradfordappraiser.com/Brevard County Property Appraiser – https://www.bcpao.us/Broward County Property Appraiser – https://bcpa.net/Calhoun County Property Appraiser – https://calhounpa.net/Charlotte County Property Appraiser – https://www.ccappraiser.com/Citrus County Property Appraiser – https://www.citruspa.org/Clay County Property Appraiser – https://ccpao.com/Collier County Property Appraiser – https://www.collierappraiser.com/Columbia County Property Appraiser – https://columbia.floridapa.com/DeSoto County Property Appraiser – https://www.desotopa.com/Dixie County Property Appraiser – https://www.qpublic.net/fl/dixie/Duval County Property Appraiser – https://www.coj.net/departments/property-appraiser.aspxEscambia County Property Appraiser – https://www.escpa.org/Flagler County Property Appraiser – https://flaglerpa.com/Franklin County Property Appraiser – https://franklincountypa.net/Gadsden County Property Appraiser – https://gadsdenpa.com/Gilchrist County Property Appraiser – https://www.qpublic.net/fl/gilchrist/Glades County Property Appraiser – https://qpublic.net/fl/glades/Gulf County Property Appraiser – https://gulfpa.com/Hamilton County Property Appraiser – https://hamiltonpa.com/Hardee County Property Appraiser – https://hardeepa.com/Hendry County Property Appraiser – https://hendryprop.com/Hernando County Property Appraiser – https://www.hernandopa-fl.us/PAWEBSITE/Default.aspxHighlands County Property Appraiser – https://www.hcpao.org/Hillsborough County Property Appraiser – https://www.hcpafl.org/Holmes County Property Appraiser – https://www.qpublic.net/fl/holmes/Indian River County Property Appraiser – https://www.ircpa.org/Jackson County Property Appraiser – https://www.qpublic.net/fl/jackson/Jefferson County Property Appraiser – https://jeffersonpa.net/Lafayette County Property Appraiser – https://www.lafayettepa.com/Lake County Property Appraiser – https://www.lakecopropappr.com/Lee County Property Appraiser – https://www.leepa.org/Leon County Property Appraiser – https://www.leonpa.gov/Levy County Property Appraiser – https://www.qpublic.net/fl/levy/Liberty County Property Appraiser – https://libertypa.org/Madison County Property Appraiser – https://madisonpa.com/Manatee County Property Appraiser – https://www.manateepao.gov/Marion County Property Appraiser – https://www.pa.marion.fl.us/Martin County Property Appraiser – https://www.pa.martin.fl.us/Miami-Dade County Property Appraiser – https://www.miamidade.gov/pa/Monroe County Property Appraiser – https://mcpafl.org/Nassau County Property Appraiser – https://www.nassauflpa.com/Okaloosa County Property Appraiser – https://okaloosapa.com/Okeechobee County Property Appraiser – https://www.okeechobeepa.com/Orange County Property Appraiser – https://ocpaweb.ocpafl.org/Osceola County Property Appraiser – https://www.property-appraiser.org/Palm Beach County Property Appraiser – https://www.pbcgov.org/papa/index.htmPasco County Property Appraiser – https://pascopa.com/Pinellas County Property Appraiser – https://www.pcpao.org/Polk County Property Appraiser – https://www.polkpa.org/Putnam County Property Appraiser – https://pa.putnam-fl.com/Santa Rosa County Property Appraiser – https://srcpa.gov/Sarasota County Property Appraiser – https://www.sc-pa.com/Seminole County Property Appraiser – https://www.scpafl.org/St. Johns County Property Appraiser – https://www.sjcpa.gov/St. Lucie County Property Appraiser – https://www.paslc.gov/Sumter County Property Appraiser – https://www.sumterpa.com/Suwannee County Property Appraiser – https://suwannee.floridapa.com/Taylor County Property Appraiser – https://qpublic.net/fl/taylor/Union County Property Appraiser – https://union.floridapa.com/Volusia County Property Appraiser – https://vcpa.vcgov.org/Wakulla County Property Appraiser – https://mywakullapa.com/Walton County Property Appraiser – https://waltonpa.com/Washington County Property Appraiser – https://www.qpublic.net/fl/washington/Florida Department of Revenue Property Tax Oversight https://floridarevenue.com/property/Pages/Home.aspx

This dataset contains information about the status of Short Term Rental permits, locations of Short Term Rentals owners of the properties, and other relevant information. Short Term Rental permits within the Suburban Cities in Jefferson County are not included in this dataset.A short term rental is a dwelling unit that is rented, leased, or otherwise assigned for a tenancy of less than 30 consecutive days duration. All short term rental hosts must annually register each of their rentals with Louisville Metro's Office of Planning & Design Services; register with the Louisville Metro Revenue Commission (for tax purposes); and, if necessary, obtain Conditional Use Permits from the Louisville Metro Board of Zoning Adjustment. This data set contains information about the status of Short Term Rental permits, locations of Short Term Rentals owners of the properties, and other relevant information.For questions about this data, reach out to Planning & Design Services Amy.Brooks@louisvilleky.gov

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.

Download .zipThe B Law Coal Permit Maps county coverage sets were developed using the original mine maps for coal mining and reclamation permits issued under Ohio law from 1973 through 1976. Approximately 1285 B-Permits were issued during this time period, however, only approximately 414 records could be located and captured at this time. The Division of Mineral Resources Management will continue to search for missing B permit archival records as resources allow; additional B permit data may be added to this existing coverage in the future.

Ohio started issuing coal mining licenses in the 1940s. The earliest license and permit requirements were minimal and sometimes did not include submittal of a map or other delineation of the mined area. Significant changes to legal requirements are reflected by the alphabetical designation of each subsequent law revision, i.e., earlier A-law permits (circa 1966) through contemporary D-law permits. The ODNR-Division of Mineral Resources Management (DMRM) has attempted to create as complete a database as possible from available archive records, however, research has identified missing permit files. Thus, this GIS data is known to be incomplete due to the loss of archival records.

The B law permit maps were scanned at a density of 200 dots per inch (dpi). The scanned image was then heads-up digitized using Microstation computer aided design software (CAD) to create design files grouped by county location. Data captured within the design file includes permit boundary, affected boundary, test hole locations, and associated attributes. The design file was then "placed-to-ground" using ODNR Division of Geological Survey's "ODNR Land Subdivision Background Design Files" NAD83 State Plane coverages and DOQQ aerial images obtained through the Ohio Geographically Referenced Information Program (OGRIP)/Ohio Department of Administrative Services. The design file was then converted to ARC/INFO coverage and projected to State Plane Ohio Coordinates, NAD83:

Projected coordinate system name: NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet

Geographic coordinate system name: GCS_North_American_1983

A complete county coverage set consists of three data files for the permit area, affected area, and test hole locations. For example, the coverage for Belmont County includes:

belmont_b_permitted (Belmont County, B-permit area polygons) belmont_b _affected (Belmont County, B-permit affected area polygons) belmont_testholes_b (Belmont County, Test Hole points)

In addition to the ArcView shape files in the county data sets, the scanned TIF images for source documents are available at DMRM. The scanned mine map depicts information about the operations conducted, environmental resources, and extracted coal resources. If more detailed information is desired, the available archival record for each captured permit can be accessed at either the State Archives at the Ohio Historical Society or the ODNR-DMRM central office.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Mineral Resources ManagementAbandoned Mine Land Program2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Jefferson County 2021 FEMA Flood Zone Areas

Download .zipThe C, D Law Coal Permit Maps county coverage sets were developed using the original mine maps for over 2500 coal mining and reclamation permits issued under Ohio law and finalized (i.e. operations completed) between 1975 and December 2002.

Ohio started issuing coal mining licenses in the 1940s. The earliest license and permit requirements were minimal and did not include submittal of a map or other delineation of the mined area. Significant changes to legal requirements are reflected by the alphabetical designation of each subsequent law revision, i.e., earlier A-law permits (circa 1966) through contemporary D-law permits. The ODNR-Division of Mineral Resources Management (DMRM) has attempted to create as complete a database as possible from available archive records, however, research has identified missing permit files. Thus, this GIS data is known to be incomplete due to the loss of archival records.

The C and D law permit maps were scanned at a density of 200 dots per inch (dpi). The scanned image was then heads-up digitized using Microstation computer aided design software (CAD) to create design files grouped by county location. Data captured within the design file includes permit boundary, affected boundary, test hole locations, and associated attributes. The design file was then "placed-to-ground" using ODNR Division of Geological Survey's "ODNR Land Sub-division Background Design Files" NAD83 State Plane coverages and DOQQ aerial images obtained through the Ohio Geographically Referenced Information Program (OGRIP)/Ohio Department of Administrative Services. The design file was then converted to ARC/INFO coverage and projected to State Plane Ohio Coordinates, NAD83:

Projected coordinate system name: NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet

Geographic coordinate system name: GCS_North_American_1983

A complete county coverage set consists of five data files for the permit area, affected area, and test hole locations. For example, the coverage for Athens County includes:

athens_c_permitted (Athens County, C-permit area polygons) athens_c_affected (Athens County, C-permit affected area polygons) athens_d_permitted (Athens County, D- permit area polygons) athens_d_affected (Athens County, D-permit affected area polygons) athens_testholes (Athens County, Test Hole points)

In addition to the ArcView shape files in the county data sets, the scanned TIF images for source documents are available at DMRM. The scanned mine map depicts information about the operations conducted, environmental resources, and extracted coal resources. If more detailed information is desired, the available archival record for each captured permit can be accessed at either the State Archives at the Ohio Historical Society or the ODNR-DMRM central office.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Mineral Resources ManagementAbandoned Mine Land Program2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

City of Arvada Parcels which fall in Jefferson County and Adams County. A parcel is any division of land held under one ownership, regardless of size. County Assessor's offices maintain these land records according to the legally-defined ownership boundaries and assigns each parcel a unique parcel identification number, or PIN, for recording purposes. The PIN becomes the universal method of referencing that particular property for the purposes of taxation, zoning, mortgages, liens, etc.

TRIMARC (Traffic Response and Incident Management Assisting the River City) camera locations in Louisville Metro Kentucky. This feature layer was created from a TRIMARC JSON files of camera locations. This item includes description, direction, and videos links and is used in the Louisville Metro Snow Map. The cameras are used to monitor the roadways and verify incidents to assist in freeway and incident management This feature is a static extract and will be reviewed before each snow season for updates. For more information on this feature layer and it's use please contact Louisville Metro GIS or LOJIC. To learn more about TRIMARC please visit the following website http://www.trimarc.org.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme ( https://communities.geoplatform.gov/ngda-cadastre/ ). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all open space public and nonprofit lands and waters. Most are public lands owned in fee (the owner of the property has full and irrevocable ownership of the land); however, permanent and long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of U.S. public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas using thirty-six attributes and five separate feature classes representing the U.S. protected areas network: Fee (ownership parcels), Designation, Easement, Marine, Proclamation and Other Planning Boundaries. An additional Combined feature class includes the full PAD-US inventory to support data management, queries, web mapping services, and analyses. The Feature Class (FeatClass) field in the Combined layer allows users to extract data types as needed. A Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) facilitates the extraction of authoritative federal data provided or recommended by managing agencies from the Combined PAD-US inventory. This PAD-US Version 3.0 dataset includes a variety of updates from the previous Version 2.1 dataset (USGS, 2020, https://doi.org/10.5066/P92QM3NT ), achieving goals to: 1) Annually update and improve spatial data representing the federal estate for PAD-US applications; 2) Update state and local lands data as state data-steward and PAD-US Team resources allow; and 3) Automate data translation efforts to increase PAD-US update efficiency. The following list summarizes the integration of "best available" spatial data to ensure public lands and other protected areas from all jurisdictions are represented in the PAD-US (other data were transferred from PAD-US 2.1). Federal updates - The USGS remains committed to updating federal fee owned lands data and major designation changes in annual PAD-US updates, where authoritative data provided directly by managing agencies are available or alternative data sources are recommended. The following is a list of updates or revisions associated with the federal estate: 1) Major update of the Federal estate (fee ownership parcels, easement interest, and management designations where available), including authoritative data from 8 agencies: Bureau of Land Management (BLM), U.S. Census Bureau (Census Bureau), Department of Defense (DOD), U.S. Fish and Wildlife Service (FWS), National Park Service (NPS), Natural Resources Conservation Service (NRCS), U.S. Forest Service (USFS), and National Oceanic and Atmospheric Administration (NOAA). The federal theme in PAD-US is developed in close collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/ ). 2) Improved the representation (boundaries and attributes) of the National Park Service, U.S. Forest Service, Bureau of Land Management, and U.S. Fish and Wildlife Service lands, in collaboration with agency data-stewards, in response to feedback from the PAD-US Team and stakeholders. 3) Added a Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) to the PAD-US 3.0 geodatabase to facilitate the extraction (by Data Provider, Dataset Name, and/or Aggregator Source) of authoritative data provided directly (or recommended) by federal managing agencies from the full PAD-US inventory. A summary of the number of records (Frequency) and calculated GIS Acres (vs Documented Acres) associated with features provided by each Aggregator Source is included; however, the number of records may vary from source data as the "State Name" standard is applied to national files. The Feature Class (FeatClass) field in the table and geodatabase describe the data type to highlight overlapping features in the full inventory (e.g. Designation features often overlap Fee features) and to assist users in building queries for applications as needed. 4) Scripted the translation of the Department of Defense, Census Bureau, and Natural Resource Conservation Service source data into the PAD-US format to increase update efficiency. 5) Revised conservation measures (GAP Status Code, IUCN Category) to more accurately represent protected and conserved areas. For example, Fish and Wildlife Service (FWS) Waterfowl Production Area Wetland Easements changed from GAP Status Code 2 to 4 as spatial data currently represents the complete parcel (about 10.54 million acres primarily in North Dakota and South Dakota). Only aliquot parts of these parcels are documented under wetland easement (1.64 million acres). These acreages are provided by the U.S. Fish and Wildlife Service and are referenced in the PAD-US geodatabase Easement feature class 'Comments' field. State updates - The USGS is committed to building capacity in the state data-steward network and the PAD-US Team to increase the frequency of state land updates, as resources allow. The USGS supported efforts to significantly increase state inventory completeness with the integration of local parks data in the PAD-US 2.1, and developed a state-to-PAD-US data translation script during PAD-US 3.0 development to pilot in future updates. Additional efforts are in progress to support the technical and organizational strategies needed to increase the frequency of state updates. The PAD-US 3.0 included major updates to the following three states: 1) California - added or updated state, regional, local, and nonprofit lands data from the California Protected Areas Database (CPAD), managed by GreenInfo Network, and integrated conservation and recreation measure changes following review coordinated by the data-steward with state managing agencies. Developed a data translation Python script (see Process Step 2 Source Data Documentation) in collaboration with the data-steward to increase the accuracy and efficiency of future PAD-US updates from CPAD. 2) Virginia - added or updated state, local, and nonprofit protected areas data (and removed legacy data) from the Virginia Conservation Lands Database, provided by the Virginia Department of Conservation and Recreation's Natural Heritage Program, and integrated conservation and recreation measure changes following review by the data-steward. 3) West Virginia - added or updated state, local, and nonprofit protected areas data provided by the West Virginia University, GIS Technical Center. For more information regarding the PAD-US dataset please visit, https://www.usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the PAD-US Data Manual available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual . A version history of PAD-US updates is summarized below (See https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-history for more information): 1) First posted - April 2009 (Version 1.0 - available from the PAD-US: Team pad-us@usgs.gov). 2) Revised - May 2010 (Version 1.1 - available from the PAD-US: Team pad-us@usgs.gov). 3) Revised - April 2011 (Version 1.2 - available from the PAD-US: Team pad-us@usgs.gov). 4) Revised - November 2012 (Version 1.3) https://doi.org/10.5066/F79Z92XD 5) Revised - May 2016 (Version 1.4) https://doi.org/10.5066/F7G73BSZ 6) Revised - September 2018 (Version 2.0) https://doi.org/10.5066/P955KPLE 7) Revised - September 2020 (Version 2.1) https://doi.org/10.5066/P92QM3NT 8) Revised - January 2022 (Version 3.0) https://doi.org/10.5066/P9Q9LQ4B Comparing protected area trends between PAD-US versions is not recommended without consultation with USGS as many changes reflect improvements to agency and organization GIS systems, or conservation and recreation measure classification, rather than actual changes in protected area acquisition on the ground.

Per Engineering Regulation 1130-2-520, USACE’s NDC and WCSC are responsible for collecting, compiling, printing, and distributing all domestic waterborne commerce statistics for which the USACE has responsibility. Per a 1998 Office of Management and Budget (OMB) memorandum, the WCSC inherited the requirement to include foreign waterborne commerce formally executed by the U.S. Census Bureau. Performance of this work is in accordance with the Rivers and Harbors Appropriation Act of 1922 (33 USC 555).

Engineering Regulation 1130-2-520 defines a port as:

(1) Port limits defined by legislative enactments of state, county, or city governments.

(2) The corporate limits of a municipality.

At minimum, the feature class includes the following attribution:

Attribute Name

Definition

Data Type

Length

featureDescription

The narrative describing the feature. This attribute column will describe how the statistical port boundary was generated using GIS. It can include the legislative description, a note that the U.S. Census Bureau municipal limit was used, or other details.

String

Max

featureName

The common name of the feature. This will be the port name as defined by the legislative enactment or the municipality. Each name should include which State(s) the port is located (ex. Louisville-Jefferson County Riverport Authority, KY).

String

80

installationId

The codes assigned by the DoD Component used to identify the site or group of sites that make up an installation. This field will remain empty, as the project focus is not on military installations.

String

11

mediaId

Used to link the record to associated multimedia records the reference data. The number used in this column will reference a related “mediaId” table that will store the source document for appropriate legislation or municipality limit reference.

String

40

metadataId

Used to represent or link to feature level metadata. For this project, a common code for the port area geometry source will be employed.

L


Legislative
Enactment




M


Municipal
Limits




O


Other

String

80

portIdpk

Primary Key. A unique, user defined identifier for each record or instance of an entity. This will be the existing four-digit port code maintained by WCSC in TOWS. A crosswalk table will also be created by the PM that correlates legacy TOWS port codes to new UN LOCODE information.

String

40

sdsId

The unique identifier for all entities in the SDSFIE. This field will remain empty and will be populated by HQUSACE if sdsID identifiers become necessary to report.

GUID

This Zoning feature class is an element of the Oregon GIS Framework statewide, Zoning spatial data. This version is authorized for public use. Attributes include zoning districts that have been generalized to state classes. As of June 30, 2023, this feature class contains zoning data from 229 local jurisdictions. DLCD plans to continue adding to and updating this statewide zoning dataset as they receive zoning information from the local jurisdictions. Jurisdictions included in the latest version of the statewide zoning geodatabase:

Cities: Adams, Adrian, Albany, Amity, Antelope, Ashland, Astoria, Athena, Aurora, Banks, Barlow, Bay City, Beaverton, Bend, Boardman, Bonanza, Brookings, Brownsville, Burns, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Coos Bay, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Dayton, Detroit, Donald, Drain, Dufur, Dundee, Dunes City, Durham, Eagle Point, Echo, Enterprise, Estacada, Eugene, Fairview, Falls City, Florence, Forest Grove, Fossil, Garibaldi, Gaston, Gates, Gearhart, Gervais, Gladstone, Gold Beach, Gold Hill, Grants Pass, Grass Valley, Gresham, Halsey, Happy Valley, Harrisburg, Helix, Hermiston, Hillsboro, Hines, Hood River, Hubbard, Idanha, Independence, Jacksonville, Jefferson, Johnson City, Jordan Valley, Junction City, Keizer, King City, Klamath Falls, La Grande, La Pine, Lafayette, Lake Oswego, Lebanon, Lincoln City, Lowell, Lyons, Madras, Malin, Manzanita, Maupin, Maywood Park, McMinnville, Medford, Merrill, Metolius, Mill City, Millersburg, Milton-Freewater, Milwaukie, Mitchell, Molalla, Monmouth, Moro, Mosier, Mount Angel, Myrtle Creek, Myrtle Point, Nehalem, Newberg, Newport, North Bend, North Plains, Nyssa, Oakridge, Ontario, Oregon City, Pendleton, Philomath, Phoenix, Pilot Rock, Port Orford, Portland, Prescott, Prineville, Rainier, Redmond, Reedsport, Rivergrove, Rockaway Beach, Rogue River, Roseburg, Rufus, Saint Helens, Salem, Sandy, Scappoose, Scio, Scotts Mills, Seaside, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Spray, Springfield, Stanfield, Stayton, Sublimity, Sutherlin, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Toledo, Troutdale, Tualatin, Turner, Ukiah, Umatilla, Vale, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Weston, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill.

Counties: Baker County, Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Harney County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Malheur County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Umatilla County, Union County, Wasco County, Washington County, Wheeler County, Yamhill County.

R emaining jurisdictions either chose not to share data to incorporate into the public, statewide dataset or did not respond to DLCD’s request for data. These jurisdictions’ attributes are designated “not shared” in the orZDesc field and “NS” in the orZCode field.