Map showing public lands in Jackson County. The map document is 34 inches by 44 inches.

Part of a set of digitized microfilm of manuscript maps of Iowa townships. Individual maps in the set may include: Native American villages and fields; the first farmsteads, town sites and fields established by settlers; networks of trails; distribution of rivers, woods, prairies, wetlands and springs; and survey data such as creator, date created, and date accepted.

This dataset includes tax lots in Jackson County, Oregon.

Jackson County Community Fire Plan Map 5 showing the Wildland Urban Interface and Public Lands. The map document is 11 inches by 17 inches.

On November 23, 2011 the Jackson County Board of Commissioners adopted the Greater Bear Creek Valley Regional Plan ("Regional Plan") as an amendment to its comprehensive plan which establishes Urban Reserve Areas (URA) for Central Point, Eagle Point, Medford, Phoenix, and Talent. This amendment establishes URAs to accommodate planned residential, commercial and industrial growth to accommodate a doubling of the current population. In reaching this decision, Jackson County updated its population forecast in the acknowledged comprehensive plan, analyzed buildable land in the Bear Creek Valley, and revised comprehensive plan policies about future urban development.

This dataset represents deer and elk Winter Range Areas. Key winter range habitat areas, as well as transition ranges, for deer and elk herds are composed of diverse, forage vegetation and a protective, insulating forest cover. Land development and land uses adversely affect these wildlife species when these integral habitats are lost. Lands within these areas are subject to specific development standards under the Jackson County Land Development Ordinance.

This data is created by using the Assessor's tax-code polygons, which are updated by approved annexations, ordinances, and resolutions on a regular basis. All tax-code boundary changes are subject to Department of Revenue boundary change ORS #308.225. In some cases, a property may have an annexation approved but is not yet reflected in current tax-code data. For historic, current, and pending annexation boundaries, please see the Annexation layer.Generally, a fire district boundary is the same a city limit boundary, however, properties may petition a fire department to be added to/removed from the district.

The Florida 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 in August 2025. 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=55e830fd6c8948baae1601fbfc33a3b2If 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://hernandocountypa-florida.us/Highlands 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://ncpafl.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

2012 6" orthophotography for Jackson County, MO. DISCLAIMER: These maps are NOT SURVEY ACCURATE. Information is used for tax purposes only. DISCLAIMER OF ACCURACY AND WARRANTIES: Requestor shall and hereby does knowingly accept the data and Information "as-is" and the County expressly disclaims any representation or warranty as to the completeness or accuracy of the data or information. Further, the County expressly disclaims any representation or warranty as to the suitability of the data or information for any specific use intended by requestor. The Jackson County GIS Department maintains maps of ownership parcels for tax purposes. Maps are intended to show as accurately as possible the relationship of neighboring ownership parcels, but are not survey accurate. They reflect the status of the parcel map at the time of printing. RELEASE: Requestor expressly releases and agrees to hold the County, its officials, and its employees, harmless from any and all claims or damages arising out of the use of the data or information, the accuracy of the data or information, or any reliance on the data or information. Requestor expressly agrees to assume all risk for use and reliance on the data and information. Please contact (816) 881-4561 or gis@jacksongov.org for further information.

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 59 counties that have opted-in as of the publication date of this dataset: Aitkin County, Anoka County, Becker County, Benton County, Big Stone County, Carlton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Clearwater County, Cook County, Crow Wing County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Lyon County, Marshall County, McLeod County, Mille Lacs County, Morrison County, Mower County, Murray County, Norman County, Olmsted County, Otter Tail County, Pennington County, Pipestone County, Polk County, Pope County, Ramsey County, Red Lake County, Renville County, Rice County, Scott County, Sherburne County, St. Louis County, Stearns County, Steele County, Stevens County, Traverse County, Wabasha County, Waseca County, Washington County, Wilkin County, Winona County, Wright County, and Yellow Medicine County.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

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 Data Update Frequency: As Needed

• See Oregon Department of State Lands : Inventories and Maps : Projects In Wetlands and Waters : State of Oregon for more information regarding protecting wetlands.This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.

The DSL SWI Soils dataset represents two selected subsets of the USDA NRCS gNATSGO dataset for Oregon. The “SWI Predominantly Hydric Soil Map Units” layer represents soil map units that are comprised of greater than 50 percent hydric soil components. The Agate-Winlo Soil Map Units layer is associated with vernal pools in Jackson County. These two subsets indicate areas where unmapped wetlands may be present for the purpose of planning, scoping projects, and coordination with DSL.The gridded National Soil Survey Geographic Database (gNATSGO) is a USDA-NRCS-SPSD composite database that provides complete coverage of the best available soils information for all areas of the United States and Island Territories. It was created by combining data from the Soil Survey Geographic Database (SSURGO), State Soil Geographic Database (STATSGO2), and Raster Soil Survey Databases (RSS) into a single seamless ESRI file geodatabase.Consult the gNATSGO home page for more information: https://www.nrcs.usda.gov/resources/data-and-reports/gridded-national-soil-survey-geographic-database-gnatsgo and the web soil survey: http://websoilsurvey.sc.egov.usda.gov/App/HomePage.htm.NRCS description of SSURGO Database:The SSURGO database contains information about soil as collected by the National Cooperative Soil Survey over the course of a century. The information can be displayed in tables or as maps and is available for most areas in the United States and the Territories, Commonwealths, and Island Nations served by the USDA-NRCS. The information was gathered by walking over the land and observing the soil. Many soil samples were analyzed in laboratories. The maps outline areas called map units. The map units describe soils and other components that have unique properties, interpretations, and productivity. The information was collected at scales ranging from 1:12,000 to 1:63,360. More details were gathered at a scale of 1:12,000 than at a scale of 1:63,360. The mapping is intended for natural resource planning and management by landowners, townships, and counties. Some knowledge of soils data and map scale is necessary to avoid misunderstandings.The maps are linked in the database to information about the component soils and their properties for each map unit. Each map unit may contain one to three major components and some minor components. The map units are typically named for the major components. Examples of information available from the database include available water capacity, soil reaction, electrical conductivity, and frequency of flooding; yields for cropland, woodland, rangeland, and pastureland; and limitations affecting recreational development, building site development, and other engineering uses.SSURGO datasets consist of map data, tabular data, and information about how the maps and tables were created. The extent of a SSURGO dataset is a soil survey area, which may consist of a single county, multiple counties, or parts of multiple counties. SSURGO map data can be viewed in the Web Soil Survey or downloaded in ESRI® Shapefile format. The coordinate systems are Geographic. Attribute data can be downloaded in text format that can be imported into a Microsoft® Access® database.https://www.nrcs.usda.gov/resources/data-and-reports/soil-survey-geographic-database-ssurgoNRCS description of STATSGO2 Database:The Digital General Soil Map of the United States or STATSGO2 is a broad-based inventory of soils and non-soil areas that occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped of 1:250,000 in the continental U.S., Hawaii, Puerto Rico, and the Virgin Islands and 1:1,000,000 in Alaska. The level of mapping is designed for broad planning and management uses covering state, regional, and multi-state areas. The U.S. General Soil Map is comprised of general soil association units and is maintained and distributed as a spatial and tabular dataset.The U.S. General Soil Map was developed by the National Cooperative Soil Survey and supersedes the State Soil Geographic (STATSGO) dataset. The dataset was created by generalizing more detailed soil survey maps. Where more detailed soil survey maps were not available, data on geology, topography, vegetation, and climate were assembled and related to Land Remote Sensing Satellite (LANDSAT) images. Soils of similar areas were studied, and the probable classification and extent of the soils were determined.Map unit composition was determined by transecting or sampling areas on the more detailed maps and then statistically expanding the data to characterize the whole map unit.The dataset consists of georeferenced, vector and tabular data. The map data were collected in 1- by 2-degree topographic quadrangle units and merged into a seamless national dataset. The dataset is distributed in state, territorial, and national extents. The spatial units are linked to attributes in the tabular data, which give the proportionate extent of the component soils and their properties.The tabular data contains estimates of physical and chemical soil properties, soil interpretations, and static and dynamic metadata. Most of the tabular data exists in the database as a range of values for soil properties. The values depict the range for the geographic extent of the map unit. For most properties, the data include high, low, and representative values.Spatial data are available in ESRI® shapefile format. Spatial reference is decimal degrees, World Geodetic System 1984 (WGS84). Tabular data are available as ASCII text files (.txt). Fields are pipe delimited, and text is double-quote delimited. A Microsoft® Access® template database is available for use with the tabular data.https://www.nrcs.usda.gov/resources/data-and-reports/description-of-statsgo2-databaseCitation: Soil Survey Staff, Natural Resources Conservation Service, United States Department of Agriculture. Web Soil Survey. Available online at. http://websoilsurvey.nrcs.usda.gov/

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.

Hurricane Harvey made landfall near Rockport, Texas on August 25 as a category 4 hurricane with wind gusts exceeding 150 miles per hour. As Harvey moved inland the forward motion of the storm slowed down and produced tremendous rainfall amounts to southeastern Texas and southwestern Louisiana. Historic flooding occurred in Texas and Louisiana as a result of the widespread, heavy rainfall over an 8-day period in Louisiana in August and September 2017. Following the storm event, U.S. Geological Survey (USGS) hydrographers recovered and documented 2,123 high-water marks in Texas, noting location and height of the water above land surface. Many of these high-water marks were used to create flood-inundation maps for selected communities of Texas that experienced flooding in August and September, 2017.
The mapped area boundary, flood inundation extents, depth rasters, and coastal surge layer were created to provide an estimated extent of flood inundation in Coastal basins including East and West Matagorda Bay Subbasins, East and West San Antonio Bay Subbasins, and Aransas Bay Subbasin, Texas. The mapped area of the Coastal basins were separated into three sections based on the availability and location of high-water marks. The maps of the eastern part of the East Matagorda Bay Subbasin include a 17-mi reach of Peyton Creek and a 16-mi reach of Big Boggy Creek, and flood-inundation map for 6-mi reach of Little Boggy Creek in Matagorda County. The maps of the western part of East Matagorda Bay Subbasin include a 13.5-mi reach of West Carancahua Creek, 14.5-mi reach of East Carancahua Creek, and 9.6-mi reach of Keller Creek within Matagorda, Jackson, and Calhoun Counties. The maps of the middle part of the East Matagorda Bay Subbasin are for a 21-mi reach of the Tres Palacios River within Matagorda County. These geospatial data include the following items: 1. bnd_emb1, bnd_emb2, and bnd_tres_palacios; shapefiles containing the polygon showing the mapped area boundary for the Coastal basins flood maps, 2. hwm_emb_1, hwm_emb2, and hwm_tres_palacios; shapefiles containing high-water mark points used for inundation maps, 3. polygon_emb1, polygon_emb_2, and polygon_tres_palacios; shapefiles containing mapped extent of flood inundation for the Coastal basins, derived from the water-surface elevation surveyed at high-water marks, 4. depth_emb1, depth_emb2, and depth_tres; raster files for the flood depths derived from the water-surface elevation surveyed at high-water marks, and 5. coastal_surge.lyr; a layer file generated from the depth raster depicting water height above ground recorded at the high-water marks. The upstream and downstream mapped area extent is limited to the upstream-most and downstream-most high-water mark locations. In areas of uncertainty of flood extent, the mapped area boundary is lined up with the flood inundation polygon extent. The mapped area boundary polygon was used to extract the final flood inundation polygon and depth raster from the water-surface elevation raster file. Depth raster files were created using the "Topo to Raster" tool in ArcMap (ESRI, 2012). The HWM elevation data from the USGS Short-tern Network (STN) was used to create the flood water-surface raster file (U.S. Geological Survey [USGS], 2018, Short-Term Network Data Portal: USGS flood information web page, accessed February 13, 2018, at https://water.usgs.gov/floods/FEV.). The water-surface raster was the basis for the creation of the final flood inundation polygon and depth layer to support the development of flood inundation map for the Federal Emergency Management Agency's (FEMA) response and recovery operations.

Legislative district boundaries in Jackson County, MO. This data is updated each week on Saturdays.

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 Data Update Frequency: As Needed

Jackson County Tax Codes

This data set is intended for use as a reference map layer for GIS maps and applications. Tax codes are used to calculate the assessor's taxing rate on a specific parcel based on the taxing districts that represent it. In GIS, this dataset is used to create Fire District boundaries, School District boundaries, and City Limits. These data are continually being updated by County Cartography.

Use the app to find the downloadable area within Jackson County - 2 Foot Contour MapThe 2-foot Contour Map shows contours that were derived from several different LiDAR projects in the Rogue Valley over the last 10 years. The map can be used to both download and view the contour data. To use the map, search or zoom in to an address. When zoomed in to a specific scale, the map will change from the downloadable areas layer to 2-foot interval contour lines. The LiDAR Project Dates layer can be used to identify the date when the elevation was collected in an area. Please note that data is available only for the valley floor areas at this time.The 2ft contours were created from 1-meter pixel DEM and then cleaned to remove very small elevation changes and to create a smooth contour line. This information should not be used to create topographic surveys or other applications where the precise elevation of a location is required. For additional information on LiDAR in Oregon or to download the source data, please visit the DOGAMI Lidar Viewer.The downloadable data is a zipped ESRI Shapefile and is projected to Oregon State Plane South (Intl Feet) with NAD 1983 datum.