This data set provides a generalized outline of the 72 counties in Wisconsin. The data is derived from 1:24,000-scale sources.

Connecticut County Index is a general purpose index map of Connecticut counties based on information compiled at 1:125,000 scale (1 inch equals approximately 2 miles). The layer is designed to be used to depict Connecticut counties at small scales or on small maps printed on regular size (8.5 x 11 inch) paper, for example. This County Index layer does not accurately represent Connecticut county boundaries because it was digitized at 1:125,000 scale. Do not display, map or analyze the County Index layer with information collected at larger scales. To depict more accurate 1:24,000-scale Connecticut state, county, and town boundaries on a map, use the layer named Town, which is also published by the State of Connecticut Department of Energy & Environmental Protection.

Download In State Plane Projection Here. These address points were developed for a myriad of uses including general public geocoding in Lake County web sites and NG-911 emergency dispatch. All addresses are reviewed on a monthly basis against the United States Post Office delivery database to ensure that they are still active. New addresses are added at this time or earlier if they are made known to Lake County GIS by local data partners. Attributes DiscrpAgID through Elev reflect the NENA NG-911 / State of Illinois GIS Data model. Additional local data fields have also been included. The fields LSt_PreDir, LSt_Name, LSt_Type and LSt_PosDir are formatted according to United States Postal Service standards.Update Frequency:This dataset is updated on a weekly basis.

This dataset demarcates the zip code boundaries that lie within Allegheny County.If viewing this description on the Western Pennsylvania Regional Data Center’s open data portal (http://www.wprdc.org), this dataset is harvested on a weekly basis from Allegheny County’s GIS data portal (http://openac.alcogis.opendata.arcgis.com/). The full metadata record for this dataset can also be found on Allegheny County’s GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the “Explore” button (and choosing the “Go to resource” option) to the right of the “ArcGIS Open Dataset” text below.Category: Civic Vitality and GovernanceOrganization: Allegheny CountyDepartment: Geographic Information Systems Group; Department of Administrative ServicesTemporal Coverage: currentData Notes: Coordinate System: Pennsylvania State Plane South Zone 3702; U.S. Survey FootDevelopment Notes: noneOther: noneRelated Document(s): Data Dictionary (none)Frequency - Data Change: As neededFrequency - Publishing: As neededData Steward Name: Eli ThomasData Steward Email: gishelp@alleghenycounty.us

NOTE: To download parcels by county DO NOT use the map. Instead:click the Download buttonclick Download parcels by county or all counties at oncescroll to the Direct Data Downloads section and download your dataThis digital geospatial dataset represents parcel boundaries with standard core attributes for a collection of parcel data from North Carolina county data producers and the Eastern Band of Cherokee Indians. The Integrated Cadastral Data Exchange project transformed source datasets from county data producers to create a standardized dataset with consistent attributes (fields). The individual standardized county datasets were aggregated into a single dataset. The aggregated parcel dataset includes all 100 counties in North Carolina plus lands of the Eastern Band of Cherokee Indians. The source geometry is retained as published by individual county data producers. This dataset includes attributes such as ownership, area in acres, assessed value, and other core cadastral attributes. Web services have both polygons (parcel boundaries) and points representing each property, placed at or near the geometric center, with the same set of attributes.See the NC OneMap parcels page for more information.

Contained here is the inventory of all Sacramento County warrants (excluding those warrants that are considered private, such as welfare payments, child support, and employee payroll) that have been issued and mailed, but which remain uncashed six months after their issue date. Uncashed County warrants that are lost can be reissued up to two and a half years from the original issue date.Department of Finance - Auditor Controller - Unclaimed County Warrants (Checks) -- This data was last updated on Oct 15, 2025 at 09:40 AM.

This dataset contains soil type and soil classification, by area.

This dataset is harvested on a weekly basis from Allegheny County’s GIS data portal. The full metadata record for this dataset can also be found on Allegheny County's GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the "Explore button (and choosing the "Go to resource" option) to the right of the "ArcGIS Open Dataset" text below.

Category: Environment

Department: Geographic Information Systems Group; Department of Administrative Services

Development Notes: This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a planimetric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a soil survey area extent format and include a detailed, field verified inventory of soils and miscellaneous areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties. The soil map and data used in the SSURGO product were prepared by soil scientists as part of the National Cooperative Soil Survey.

Related Documents: Data Dictionary for SOIL_CODE, https://www.nrcs.usda.gov/Internet/FSE_MANUSCRIPTS/pennsylvania/PA003/0/legends.pdf (the last page includes the soil legend for this dataset)

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. Created for the January 2016 Map of the Month. Data researched by OC-GIS team and hosted in ArcGIS Online.

Basemap polygon features for Pierce County including the county, city and some federal boundaries, the Puget Sound, and major lakes. This layer is intended for cartographic purposes only and should not be used as official boundaries. Please read metadata for additional information (https://matterhorn.piercecountywa.gov/GISmetadata/pdbis_basemap.html). Any use or data download constitutes acceptance of the Terms of Use (https://matterhorn.piercecountywa.gov/disclaimer/PierceCountyGISDataTermsofUse.pdf).

The Counties dataset was updated on October 31, 2023 from the United States Census Bureau (USCB) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are mostly as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529015

This dataset contains miscellaneous linework that assists with map creation and clarification. Examples of graphical features represented in this database are: old or vacated lot lines, lines, right of way and plat boundary extension lines.The parcel information data layer represents various parcel related graphical elements, which aid in the understanding and interpretation of map features. It is not intended to be inclusive. It is intended to act as a visual aid to help with map interpretation.

This dataset demarcates the Pennsylvania Senate district boundaries within Allegheny County.

If viewing this description on the Western Pennsylvania Regional Data Center’s open data portal (http://www.wprdc.org), this dataset is harvested on a weekly basis from Allegheny County’s GIS data portal (http://openac.alcogis.opendata.arcgis.com/). The full metadata record for this dataset can also be found on Allegheny County’s GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the “Explore” button (and choosing the “Go to resource” option) to the right of the “ArcGIS Open Dataset” text below.

Category: Civic Vitality and Governance

Organization: Allegheny County

Department: Geographic Information Systems Group; Department of Administrative Services

Temporal Coverage: 2015

Data Notes:

Coordinate System: Pennsylvania State Plane South Zone 3702; U.S. Survey Foot

Development Notes: none

Other: none

Related Document(s): Data Dictionary (none)

Frequency - Data Change: As needed

Frequency - Publishing: As needed

Data Steward Name: Eli Thomas

Data Steward Email: gishelp@alleghenycounty.us

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.

Connecticut and Vicinity Town Boundary data are intended for geographic display of state, county and town (municipal) boundaries at statewide and regional levels. Use it to map and label towns on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

Description: The neighborhoods shown in this dataset are derived from a larger dataset drawn and maintained by the Data Desk, a team of Times reporters and Web developers in downtown L.A. The boundaries have expanded and shifted over time and now cover all of Los Angeles County broken down into 272 neighborhoods.This version of the LA Times boundaries only includes neighborhoods fully or partially within the City of Los Angeles. Neighborhoods that extend into other cities have been clipped to only show the portion(s) of the neighborhoods that are within the City of Los Angeles.Data Source: Los Angeles Times' Mapping LA project.Last Updated: October 7, 2016Refresh Rate: Never - Historical data (Note: should the LA Times update their Mapping LA project with new boundaries in the future, a new LA-specific layer will be added to the GeoHub as well.)

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)

This layer shows housing costs as a percentage of household income. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. Income is based on earnings in past 12 months of survey. This layer is symbolized to show the percent of renter households that spend 30.0% or more of their household income on gross rent (contract rent plus tenant-paid utilities). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B25070, B25091 Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

The geographic extent of a County, this file represents 3 counties (Dallas, Collin, Denton) clipped from a statewide 2010 Census dataset that are in the Tx N. Central 4202 State Plane projection. The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most States are termed counties. The 2010 Census boundaries for counties and equivalent entities are as of January 1, 2010, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).Metadata edited 01/2021

Throughout the state, CAL FIRE has 21 operational units that are designed to address fire suppression over a certain geographic area. Each unit operates within their local jurisdiction and strives to fulfill the department's mission whether it be responding to all-risk emergencies, participating in fire safety education and educating homeowners on how to keep their property fire safe. In addition, CAL FIRE provides funding to six 'Contract Counties' (Kern, Los Angeles, Marin, Orange, Santa Barbara and Ventura) for fire protection services, including wages of suppression crews, lookouts, maintenance of fire fighting facilities, fire prevention assistants, pre-fire management positions, dispatch, special repairs, and administrative services. The Department's budget also provides for infrastructure improvements, and expanded fire fighting needs when fires grow beyond initial attack. Contract Counties are responsible for providing initial response to fires on SRA. When a wildland fire escapes this initial attack, CAL FIRE responds with fire fighting resources to assist the county.This service represents the latest official version of the CAL FIRE Administrative Units dataset, and is updated whenever a new version is released. As of May 2023, it represents cdfadmin23_1.

Download In State Plane Projection Here The Lake County Wetland Inventory (LCWI) maps natural and artificial wetlands meeting definitions established by the federal agencies who work with the Lake County Geographic Information System staff to periodically review and update it. These agencies include the United States Environmental Protection Agency, the U.S. Fish and Wildlife Service, the USDA Natural Resources Conservation Service and the United States Army Corps of Engineers. The 1989 federal wetland delineation standards for offsite wetland mapping are used. This data was last published in March of 1993. This update includes changes to the previous version of LCWI including: adjust current wetland boundaries to omit development, including roads; to fine tune boundary placement where that was intended by the original delineation, in some cases, adjust the wetland to photographic features / signature; delete wetlands which the committee decided were mapped in error - for example, trees which were mistaken for wet areas; create polygons for newly delineated artificial wetlands; and newly delineated wetlands or farmed wetlands caused by the continued deterioration of the agricultural drain tile system and increased runoff due to urbanization. The LCWI is a useful tool for general planning and review purposes, but it does not take the place of an on-site delineation by a certified wetland specialist. High resolution (1" = 100') orthorectified aerial imagery captured in April 2002 was used as the base for this update. Other data used as reference for this update include: 2004 SOIL SURVEY GEOGRAPHIC (SSURGO) DATABASE FOR LAKE COUNTY, IL - U.S. Department of Agriculture, Natural Resources Conservation Service; HYDROLOGY2002 - Lake County GIS/Map Division; 2' topography (CONTOURS) - Lake County GIS/Map Division; and various years of historical aerial photography for clarification. By using the more recent higher resolution photography, the resulting updated wetland boundaries are more accurate then the original boundaries published in 1993.