The use of data from Washington County indicates the acceptance of and agreement to be legally bound by the terms of Washington County printed below. DisclaimerWashington County has provided these Geographic Information System maps and data as a public information service. Every reasonable effort has been made to assure the accuracy of these maps and associated data. However, the maps and data being provided herein are intended for informational purposes only. No guarantee is made as to the accuracy of the maps and data and they should not be relied upon for any purpose other than general information.No LiabilityWashingtonCounty assumes no liability arising from the use of these maps or data. The maps and data are provided without warranty of any kind,either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.Furthermore, Washington County assumes no liability for any errors, omissions, or inaccuracies in the information provided regardless of the cause of such or for any decision made, action taken, or action not taken by the userin reliance upon any maps or data provided herein. Please consult official County maps and records for official information.IndemnificationIf user disseminates saiddata in any form or fashion to a third party, the useragrees to indemnify and hold harmless Washington County and its officials and employees from any and all claims, liability, damages, injuries, and suits, including court costs and reasonable attorney’s fees, arising from the use of the Washington County data by the userand any third party.

General base map of Washington County, Oregon

Washington County, MN Tax Parcels. An independent manual check of the parcel data was made at the time of its initial development whereby all geo-coded parcel legal descriptions in a PLSS section were reinterpreted and examined for accuracy and completeness on the hard copy check plot. As each new plat or lot division occurs, a similar process is repeated for the new additions during the maintenance period. Multiple lines of ownership indicating ambiguity in property line location are merged into a single line if falling within 3 feet of each other. Gaps or overlaps in these situations are not shown. In some cases where two lines converge; e.g., where at one end the two lot lines are within 0.50 feet of each other and at the other end they are within 6.00 feet of each other they may be merged because the average discrepancy is 3 feet or less. Where gaps or overlaps exist in excess of approximately 3 feet in width, they are shown with text notation indicating APPARENT GAP or AREA OF DISCREPANCY.

The use of data from Washington County indicates the acceptance of and agreement to be legally bound by the terms of Washington County printed below. Disclaimer. Washington County has provided these Geographic Information System maps and data as a public information service. Every reasonable effort has been made to assure the accuracy of these maps and associated data. However, the maps and data being provided herein are intended for informational purposes only. No guarantee is made as to the accuracy of the maps and data and they should not be relied upon for any purpose other than general information. No LiabilityWashington County assumes no liability arising from the use of these maps or data. The maps and data are provided without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Furthermore, Washington County assumes no liability for any errors, omissions, or inaccuracies in the information provided regardless of the cause of such or for any decision made, action taken, or action not taken by the user in reliance upon any maps or data provided herein. Please consult official County maps and records for official information. IndemnificationIf user disseminates said data in any form or fashion to a third party, the user agrees to indemnify and hold harmless Washington County and its officials and employees from any and all claims, liability, damages, injuries, and suits, including court costs and reasonable attorney’s fees, arising from the use of the Washington County data by the user and any third party.

This layer contains data concerning the location and characteristics of bedrock, mappable geologic units, within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

Use this web map to link to other geospatial datasets available through county and city sites (Not comprehensive). May need to zoom in to see the participating cities. The county boundaries and city points were published by Washington State agencies and downloaded from geo.wa.gov. Locations are approximate, and no warranties are made regarding this data. The canvas basemap has been compiled by Esri and the ArcGIS user community from a variety of best available sources. Want to have your data site listed? Contact the Geospatial Program Office.

An official index map of tax maps by municipality for the County of Berks Assessment Department.

The use of data from Washington County indicates the acceptance of and agreement to be legally bound by the terms of Washington County printed below. Disclaimer. Washington County has provided these Geographic Information System maps and data as a public information service. Every reasonable effort has been made to assure the accuracy of these maps and associated data. However, the maps and data being provided herein are intended for informational purposes only. No guarantee is made as to the accuracy of the maps and data and they should not be relied upon for any purpose other than general information.No LiabilityWashington County assumes no liability arising from the use of these maps or data. The maps and data are provided without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Furthermore, Washington County assumes no liability for any errors, omissions, or inaccuracies in the information provided regardless of the cause of such or for any decision made, action taken, or action not taken by the user in reliance upon any maps or data provided herein. Please consult official County maps and records for official information. IndemnificationIf user disseminates said data in any form or fashion to a third party, the user agrees to indemnify and hold harmless Washington County and its officials and employees from any and all claims, liability, damages, injuries, and suits, including court costs and reasonable attorney’s fees, arising from the use of the Washington County data by the user and any third party.

This layer contains data concerning the location and characteristics of unconsolidated Quaternary deposits within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

The 2023 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. In MCD states where no MCD exists or no MCD is defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The generalized boundaries of legal MCDs are based on those as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CCDs, delineated in 21 states, are based on those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

Unincorporated Urban Growth Areas (UGA) as defined by the Growth Management Act (GMA). The annual update is conducted by collecting UGA polygons directly from each of Washington's 39 counties. As of 2025, there are 27 counties with UGAs.All UGA polygons are normalized against the Department of Revenue's (DOR) "City Boundaries" layer (shared to the Washington Geoportal a.k.a. the GIS Open Data site: geo.wa.gov). The City Boundaries layer was processed into this UGA layer such that any overlapping area of UGA polygons (from authoritative individual counties) was erased. Since DOR polygons and county-sourced UGA polygons do not have perfect topology, many slivers resulted after the erase operation. These are attempted to be irradicated by these processing steps. "Multipart To Singlepart" Esri tool; exploded all polygons to be individualSlivers were mathematically identified using a 4 acre area threshold and a 0.3 "thinness ratio" threshold as described by Esri's "Polygon Sliver" tool. These slivers are merged into the neighboring features using Esri's "Eliminate" tool.Polygons that are less than 5,000 sq. ft. and not part of a DOR city (CITY_NM = Null) were also merged via the "Eliminate" tool. (many very small slivers were manually found yet mathematically did not meet the thinness ratio threshold)The final 8 polygons less than 25 sq. ft. were manually deleted (also slivers but were not lined up against another feature and missed by the "Eliminate" tool runs)Dissolved all features back to multipart using all fieldsAll UGAs polygons remaining are unincorporated areas beyond the city limits. Any polygon with CITY_NM populated originated from the DOR "City Boundaries" layer. The DOR's City Boundaries are updated quarterly by DOR. For the purposes of this UGA layer, the city boundaries was downloaded one time (4/24/2025) and will not be updated quarterly. Therefore, if precise city limits are required by any user of UGA boundaries, please refer to the city boundaries layer and conduct any geoprocessing needed. The DOR's "City Boundaries" layer is available here:https://www.arcgis.com/home/item.html?id=69fcb668dc8d49ea8010b6e33e42a13aData is updated in conjunction with the annual statewide parcel layer update. Latest update completed April 2025.

This layer contains data concerning the location and characteristics of contacts and faults within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

This layer contains data concerning field measurements of inclined bedding, structure features like fracture, cleavage, and other field measurements within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The projection is NAD_1983_UTM_Zone_12N with the coordinate system name as Universal Transverse Mercator. The horizontal accuracy meets Guidelines and specifications for DFIRM production.

The use of data from Washington County indicates the acceptance of and agreement to be legally bound by the terms of Washington County printed below. Disclaimer. Washington County has provided these Geographic Information System maps and data as a public information service. Every reasonable effort has been made to assure the accuracy of these maps and associated data. However, the maps and data being provided herein are intended for informational purposes only. No guarantee is made as to the accuracy of the maps and data and they should not be relied upon for any purpose other than general information. No LiabilityWashington County assumes no liability arising from the use of these maps or data. The maps and data are provided without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Furthermore, Washington County assumes no liability for any errors, omissions, or inaccuracies in the information provided regardless of the cause of such or for any decision made, action taken, or action not taken by the user in reliance upon any maps or data provided herein. Please consult official County maps and records for official information. IndemnificationIf user disseminates said data in any form or fashion to a third party, the user agrees to indemnify and hold harmless Washington County and its officials and employees from any and all claims, liability, damages, injuries, and suits, including court costs and reasonable attorney’s fees, arising from the use of the Washington County data by the user and any third party.

Map of Washington County, Maryland, showing distribution of geological formations and structural features.

This is a 10 meter Hillshade file created by Metro from USGS DEM data provided by the BLM. It covers the 3-county area (Washington, Multnomah, and Clackamas Counties). Date of last data update: 2004 This is official RLIS data. Contact Person: Joe Gordon joe.gordon@oregonmetro.gov 503-797-1587 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2162 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

This map presents land cover and detailed topographic maps for the United States. It uses the USA Topographic Map service. The map includes the National Park Service (NPS) Natural Earth physical map at 1.24km per pixel for the world at small scales, i-cubed eTOPO 1:250,000-scale maps for the contiguous United States at medium scales, and National Geographic TOPO! 1:100,000 and 1:24,000-scale maps (1:250,000 and 1:63,000 in Alaska) for the United States at large scales. The TOPO! maps are seamless, scanned images of United States Geological Survey (USGS) paper topographic maps.

The maps provide a very useful basemap for a variety of applications, particularly in rural areas where the topographic maps provide unique detail and features from other basemaps.

To add this map service into a desktop application directly, go to the entry for the USA Topo Maps map service.

Tip: Here are some famous locations as they appear in this web map, accessed by including their location in the URL that launches the map:

Grand Canyon, Arizona

Golden Gate, California

The Statue of Liberty, New York

Washington DC

Canyon De Chelly, Arizona

Yellowstone National Park, Wyoming

Area 51, Nevada

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Water_Type/MapServer/4For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.It is intended that these data be only a first step in determining whether or not wetland issues have been or need to be addressed in an area. The DNR Forest Practices Division and the Department of Ecology strongly supports the additional use of hydric soils (from the GIS soils layer) to add weight to the call of 'wetland'. Reports from the Department of Ecology indicate that these data may substantially underestimate the extent of forested wetlands. Various studies show the NWI data is 25-80% accurate in forested areas. Most of these data were collected from stereopaired aerial photos at a scale of 1:58,000. The stated accuracy is that of a 1:24,000 map, or plus or minus 40 feet. In addition, some parts of the state have data that are 30 years old and only a small percentage have been field checked. Thus, for regulatory purposes, the user should not rely solely on these data. On-the-ground checking must accompany any regulatory call based on these data.The reclassification is based on the USFWS FWS_CODE. The FWS_CODE is a concatenation of three subcomponents: Wetland system, class, and water regime. Forest Practices further divided the components into system, subsystem, class, subclass, water regime, special modifiers, xclass, subxclass, and xsystem. The last three items (xsomething) are for wetland areas which do not easily lend themselves to one class alone. The resulting classification system uses two fields: WLND_CLASS and WLND_TYPE. WLND_CLASS indicates whether the polygon is a forested wetland (F), open water (O), or a vegetated wetland (W). WLND_TYPE, indicates whether the wetland is a type A (1), type B (2), or a generic wetland (3) that doesn't fit the categories for A or B type wetlands. WLND_TYPE = 0 (zero) is used where WLND_CLASS = O (letter "O").

The wetland polygon is classified as F, forested wetland; O, open water; or W, vegetated wetland depending on the following FWS_CODE categories: F O W --------------------------------------------------- Forested Open Vegetated Wetland Water Wetland --------------------------------------------PFO* POW PUB5 E2FO PRB* PML2 PUB1-4 PEM* PAB* L2US5 PUS1-4 L2EM2 PFL* PSS* L1RB* PML1 L1UB*
L1AB* L1OW L2RB* L2UB* L2AB* L2RS* L2US1-4 L2OW

• indicates inclusion of the subcategory (ie. PEM* includes PEM1F, PEM1FB, etc.).

DNR FOREST PRACTICES WETLANDS DATASET ON FPARS Internet Mapping Website: The FPARS Resource Map and Water Type Map display Forested, Type A, Type B, and "other" wetlands. Open water polygons are not displayed on the FPARS Resource Map and Water Type Map in an attempt to minimize clutter. The following code combinations are found in the DNR Forest Practices wetlands dataset:

WLND_CLASS WLND_TYPE wetland polygon classification F 3 Forested wetland as defined in WAC 222-16-035 O 0 *NWI open water (not displayed on FPARS Resource or Water Type Maps) W 1 Type A Wetland as defined in WAC 222-16-035 W 2 Type B Wetland as defined in WAC 222-16-035 W 3 other wetland

• NWI open water polygons are indicated by WLND_CLASS = O and WLND_TYPE = 0. Open water is used in the USFWS and WAC 222-16-035 classification system. These open water polygons are not included in the FPARS Resource Map and Water Type Map views of this dataset in an attempt to minimize clutter on the FPARS maps.