A web map used to access tax parcel, boundary, ownership, acreage, survey, zoning and tax information. Errors and Omissions Do Exist.The information provided is for reference only and subject to independent verification. User assumes all responsibility for its use.https://www.fayette-co-oh.com/Fayette County ProfileFayette County is a county located in the U.S. state of Ohio. Its county seat is Washington Court House. Fayette County was formed on March 1, 1810 from portions of Highland County and Ross County. It was named after Marie-Joseph Motier, Marquis de La Fayette, a French general and politician who took the side of the Colonials during the American Revolutionary War and who played an important role in the French Revolution.Fayette County is a part of the Virginia Military survey, which was reserved in 1783, to be allotted to Virginia soldiers. This district includes the entire counties of Adams, Brown, Clermont, Clinton, Highland, Fayette, Madison and Union; and a portion of the counties of Scioto, Pike, Ross, Pickaway, Franklin, Delaware, Marion, Hardin, Logan, Champaign, Clarke, Greene, Warren and Hamilton.Fayette County was formed January 19, 1810 (took effect March 1st) from Ross and Highland counties. Beginning at the southwest corner of Pickaway, running north “with the line of said county to the corner of Madison; thence west with the line of said Madison county to the line of Greene county; thence south with the line of Greene county to the southeast corner thereof; thence east five miles; thence south to the line of Highland county; thence east with said line to Paint Creek; thence in a straight line to the beginning.” All the lower portion was taken from Highland and the upper from Ross.The first portion of land entered within the territory of what is now Fayette county, was a part of original surveys Nos. 243 and 772, lying partly in Clinton county. The first survey lying wholly within Fayette county was No. 463, in what is now Madison township, surveyed for Thomas Overton by John O’Bannon June 30, 1776.The original townships were Jefferson, Greene, Wayne, Madison, Paint and Union. Concord township was formed in April 1818, from Greene. Marion township was formed in June, 1840 from Madison. Perry township was formed June 4, 1845, from Wayne and Greene. Jasper township was formed from Jefferson and Concord December 2, 1845.Washington C.H. was laid out originally on a part of entry 757, which contained 1200 acres and belonged to Benjamin Temple, of Logan county, Kentucky, who donated 150 acres to Fayette county, on condition that it be used as the site of the county seat. The deed of conveyance was made December 1, 1810, by Thomas S. Hind, attorney for Temple, to Robert Stewart, who was appointed by the legislature as director for the town of Washington. The town was laid off some time between December 1, 1810, and February 26, 1811, the latter being the date of the record of the town plat.Bloomingburg (originally called New Lexington) was laid out in 1815, by Solomon Bowers, and originally contained 34 and ¾ acres. On March 4, 1816, Bowers laid out and added twenty more lots. The name of the town was later changed to Bloomingburg by act of the legislature. The town was incorporated by act of the legislature, February 5, 1847.Jeffersonville was laid out March 1, 1831, by Walter B. Write and Chipman Robinson, on 100 acres of land belonging to them, they started selling the lots at $5 each. The town incorporated March 17, 1838. The first house was erected by Robert Wyley.The first railroad, now the C. & M. V., was completed in 1852; the second, now the Detroit Southern, in 1875; the third, now the C.H. & D. in 1879; and the fourth, now the B. & O. S. W., in 1884.The first permanent settler (probably) was a Mr. Wolf who settled in what is now Wayne township, in about the year 1796. - Circa 1886 - Map of Fayette County, Ohio. Issued by the Fayette County Record.

DCGIS is an interactive map that provides increased functionality for advanced users as well as access to about 150 layers of GIS data, including parcel information, contour lines, aerial photography, county park amenities, park trails, bikeways, county road construction, roundabouts, floodplains and more. It allows you to create a map at any scale you wish.
The Interactive GIS Map is intended for use on any device - mobile or desktop - with high speed access.

This map shows the free and open data status of county public geospatial (GIS) data across Minnesota. The accompanying data set can be used to make similar maps using GIS software.

Counties shown in this dataset as having free and open public geospatial data (with or without a policy) are: Aitkin, Anoka, Becker, Beltrami, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Grant, Hennepin, Hubbard, Isanti, Itasca, Kittson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Meeker, Mille Lacs, Morrison, Mower, Norman, Olmsted, Otter Tail, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Scott, Sherburne, St. Louis, Stearns, Steele, Stevens, Traverse, Wabasha, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.

To see if a county's data is distributed via the Minnesota Geospatial Commons, check the Commons organizations page: https://gisdata.mn.gov/organization

To see if a county distributes data via its website, check the link(s) on the Minnesota County GIS Contacts webpage: https://www.mngeo.state.mn.us/county_contacts.html

Map containing all Porter County GIS feature layers publicly available. Dynamic data sets are updated daily. Individual copies of this data are available in the Porter County GIS Office.

This parcels dataset is a spatial representation of tax lots for Cape May County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.This GIS parcel data set was created by using scanned county tax maps. The scanned images were georeferenced to the 2002 color digitial orthophotos for the State of New Jersey. Software customization was developed to standardize data capture as well as processing. Quality control/quality assurance methods were developed and used throughout the entire data capture and processing. GIS processing was done using ESRI's ArcInfo and topology rules were applied to ensure proper connectivity between polygons.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

This dataset contains model-based county-level estimates for the PLACES 2022 release in GIS-friendly format. PLACES covers the entire United States—50 states and the District of Columbia (DC)—at county, place, census tract, and ZIP Code Tabulation Area levels. It provides information uniformly on this large scale for local areas at 4 geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. Project was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates include Behavioral Risk Factor Surveillance System (BRFSS) 2020 or 2019 data, Census Bureau 2020 or 2019 county population estimates, and American Community Survey (ACS) 2016–2020 or 2015–2019 estimates. The 2022 release uses 2020 BRFSS data for 25 measures and 2019 BRFSS data for 4 measures (high blood pressure, taking high blood pressure medication, high cholesterol, and cholesterol screening) that the survey collects data on every other year. These data can be joined with the census 2020 county boundary file in a GIS system to produce maps for 29 measures at the county level. An ArcGIS Online feature service is also available for users to make maps online or to add data to desktop GIS software. https://cdcarcgis.maps.arcgis.com/home/item.html?id=3b7221d4e47740cab9235b839fa55cd7

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.

Publication Date: April 2025 2024 Parcel Data. Updated annually, or as needed. The data can be downloaded here: https://gis.ny.gov/parcels#data-download. This feature service has two layers: 1) NYS Tax Parcels Public, and 2) NYS Tax Parcels Public Footprint which contains polygons representing counties for which tax parcel polygons are available in the NYS Tax Parcels Public layer. County footprint polygons display when zoomed out beyond 1:37,050-scale. Tax parcel polygons display when zoomed in below 1:37,051-scale. The NYS Tax Parcels Public layer contains 2024 parcel data only for NY State counties which gave NYS ITS Geospatial Services permission to share this data with the public. Work to obtain parcel data from additional counties, as well as permission to share the data, is ongoing. To date, 36 counties have provided Geospatial Services permission to share their parcel data with the public. Parcel data for counties which do not allow Geospatial Services to redistribute their data must be obtained directly from those counties. Geospatial Services' goal is to eventually include parcel data for all counties in New York State. Parcel geometry was incorporated as received from County Real Property Departments. No attempt was made to edge-match parcels along adjacent counties. County attribute values were populated using 2024 Assessment Roll tabular data the NYS ITS Geospatial Services obtained from the NYS Department of Tax and Finance’s Office of Real Property Tax Services (ORPTS). Tabular assessment data was joined to the county provided parcel geometry using the SWIS & SBL or SWIS & PRINT KEY unique identifier for each parcel. Detailed information about assessment attributes can be found in the ORPTS Assessor’s Manuals available here: https://www.tax.ny.gov/research/property/assess/manuals/assersmanual.htm. New York City data comes from NYC MapPluto which can be found here: https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page. Thanks to the following counties that specifically authorized Geospatial Services to share their GIS tax parcel data with the public: Albany, Cayuga, Chautauqua, Cortland, Erie, Genesee, Greene, Hamilton, Lewis, Livingston, Montgomery, NYC- Bronx, NYC- Kings (Brooklyn), NYC- New York (Manhattan), NYC- Queens, NYC- Richmond (Staten Island), Oneida, Onondaga, Ontario, Orange, Oswego, Otsego, Putnam, Rensselaer, Rockland, Schuyler, St Lawrence, Steuben, Suffolk, Sullivan, Tioga, Tompkins, Ulster, Warren, Wayne, and Westchester. Geometry accuracy varies by contributing county. This map service is available to the public. The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

The Digital Geologic-GIS Map of Fayette County, Pennsylvania is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (faco_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (faco_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (faco_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (fone_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (fone_frhi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (faco_geology_metadata_faq.pdf). Please read the fone_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Pennsylvania Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (faco_geology_metadata.txt or faco_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:50,000 and United States National Map Accuracy Standards features are within (horizontally) 25.4 meters or 83.3 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Tax Parcel shape files, metadata, and geodatabases by town and city available to download: https://gisdata.ny.gov/GISData/County/Greene/Parcel_Data/Greene_County_Tax_Parcels.zip Database was prepared for assessment administration purposes only. It is not intended for use in the conveyance of land. Absolutely no accuracy or completeness is implied or intended. All the information is subject to such variations and corrections that may result from an accurate instrument survey and or abstract of title Spatial Reference of Source Data: NAD 83 State Plane – New York East.Spatial Reference of Web Service: WGS 1984 Web Mercator Auxiliary Sphere. Data current as of July 2025. Contact Information:Greene County Real Property Tax Service411 Main Street Suite 447Catskill, New York 12414PH: 518-719-3525FAX: 518-719-3791rpts@greenecountyny.gov

GIS Map view look up parcel information including owner, taxes, market value and more.Important Mailing Label Information:The "Mailing Labels" button is is copy of the Parcels Layer and is intended to be turned OFF on the map, and is there just for the "Public Notification" Widget. This widget obtains information on the pop-up of a selected layer to create "Mailing Labels." This said, this layer contains the Owners Mailing Address information. Below is Arcaded used to customize the pop-up:Made three custom Arcade Lines below: Proper($feature["OWNER_NAM1"]) + Proper($feature["OWNER_NAM2"])Proper($feature["OWNER_ADDR"])Proper($feature["OWNER_CITY"]) + ',' + $feature["OWNER_STAT"] + ',' + $feature["OWNER_ZIP"]Below is the custom pop-up:{expression/expr0}{expression/expr1}{expression/expr2}

Webmap of Allegheny municipalities and parcel data. Zoom for a clickable parcel map with owner name, property photograph, and link to the County Real Estate website for property sales information.

This dataset contains model-based county-level estimates for the PLACES project 2020 release in GIS-friendly format. The PLACES project is the expansion of the original 500 Cities project and covers the entire United States—50 states and the District of Columbia (DC)—at county, place, census tract, and ZIP Code tabulation Areas (ZCTA) levels. It represents a first-of-its kind effort to release information uniformly on this large scale for local areas at 4 geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. The project was funded by the Robert Wood Johnson Foundation (RWJF) in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates include Behavioral Risk Factor Surveillance System (BRFSS) 2018 or 2017 data, Census Bureau 2018 or 2017 county population estimates, and American Community Survey (ACS) 2014-2018 or 2013-2017 estimates. The 2020 release uses 2018 BRFSS data for 23 measures and 2017 BRFSS data for 4 measures (high blood pressure, taking high blood pressure medication, high cholesterol, and cholesterol screening). Four measures are based on the 2017 BRFSS data because the relevant questions are only asked every other year in the BRFSS. These data can be joined with the census 2015 county boundary file in a GIS system to produce maps for 27 measures at the county level. An ArcGIS Online feature service is also available at https://www.arcgis.com/home/item.html?id=8eca985039464f4d83467b8f6aeb1320 for users to make maps online or to add data to desktop GIS software.

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

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.

The Digital Glacial and Surficial Geologic-GIS Map of Summit County and Parts of Cuyahoga County, Ohio is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (cuva_glacial_surficial_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (cuva_glacial_surficial_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (cuva_geology.gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (cuva_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (cuva_glacial_surficial_geology_metadata_faq.pdf). Please read the cuva_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: http://www.google.com/earth/index.html. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Ohio Division of Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (cuva_glacial_surficial_geology_metadata.txt or cuva_glacial_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

US Census Bureau Cartographic Boundary File of county boundaries for each state in the Unites States.

From the US Census Bureau: "The cartographic boundary files are simplified representations of selected geographic areas from the Census Bureau’s MAF/TIGER geographic database. These boundary files are specifically designed for small scale thematic mapping."

Lake County's most comprehensive interactive web mapping application and GIS data viewer. View data, run analysis tools, and create PDF documents all inside Maps Online!

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.

Parcel Hubsite