Facebook
TwitterUnincorporated 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.
Facebook
TwitterDisplays outlines depicting the current boundaries of WA State Parks lands. This KML file contains a network link to another KML file that is stored on the WA State Parks website. In this way, using this KML file will always display up-to-date boundaries, eliminating the need to download updated KML files.This data layer depicts the current boundaries for WA State Parks, and properties owned by WSPRC (Washington State Parks and Recreation Commission). Property types include State Park, State Park Conservation Area, State Park Heritage Site, State Park Property, State Park Trail, Historical State Park, and Marine State Park. Data is revised monthly or more frequently; however, errors and inaccuracies may exist in the data. This layer is for informational purposes only and is not intended to be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries.For attribute descriptions, see the metadata for the GIS data layer "ParkBoundaries", available online at http://geo.wa.gov/datasets/wa-stateparks::parks-park-boundaries .To download this and other data from Washington State Parks, go to geo.wa.gov and search for "wsprc" (Washington State Parks and Recreation Commission).
Facebook
TwitterClick to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site3/rest/services/Public_Boundaries/WADNR_PUBLIC_Cadastre_OpenData/FeatureServer/10Official Washington State boundary
Facebook
TwitterWashington Legislative Districts 2024, also known as Remedial Map 3B, created in CASE NO. 3:22-cv-05035-RSL at the United States District Court for the Western District of Washinton at Seattle, presided over by judge Robert. S Lasnik.https://www.documentcloud.org/documents/24483664-redistricting-orderThese districts replace the 2022 Legislative districts and will be used in the 2024 elections pending US Supreme Court action.Please note that there are four split Census Blocks due to annexations in Yakima County. Portions of blocks 530770018013012, 530770018012077, 530770020042004, and 530770018011075 transferred from LD 15 to LD 14. This feature layer contains 49 features representing each of Washington State's 49 legislative districts and is projected to NAD 1983 HARN Washington State Plane South US Feet.For questions, please contact Nicholas Pharris at the Secretary of State. nicholas.pharris@sos.wa.gov
Facebook
TwitterFor 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 Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata
Facebook
TwitterMapping of Visible Surface Water (VSW), or water features not concealed by other objects (i.e., tree canopy, bridges, etc.), is an important component of landcover models. VSW is not intended to represent a full hydrography or show connectivity, like other available water datasets – like NHD – whose boundaries may include other landcover types (i.e., shrubs, trees, etc.). Each feature has been visually verified and given attributes by an analyst. This dataset is also unique in that it reflects surface water for a single year - 2017. A variety of funding sources acquired between 2019 and 2023 aided the completion of the dataset for the entire state of Washington. More information on the dataset, current data coverage, and applications can be found on our website: https://hrcd-wdfw.hub.arcgis.com/.
Tip: Try using the filter options on the data tab to limit your download to a single County or WRIA. The filtered download can take a substantial amount of time to initiate, so it may be necessary to download the full dataset if the filter option does not work.
Facebook
TwitterThe 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. State Legislative Districts (SLDs) are the areas from which members are elected to State legislatures. The SLDs embody the upper (senate) and lower (house) chambers of the state legislature. Nebraska has a unicameral legislature and the District of Columbia has a single council, both of which the Census Bureau treats as upper-chamber legislative areas for the purpose of data presentation; there are no data by SLDL for either Nebraska or the District of Columbia. A unique three-character census code, identified by state participants, is assigned to each SLD within a state. In Connecticut, Illinois, Louisiana, New Hampshire, Wisconsin, and Puerto Rico, the Redistricting Data Program (RDP) participant did not define the SLDs to cover all of the state or state equivalent area. In these areas with no SLDs defined, the code "ZZZ" has been assigned, which is treated as a single SLD for purposes of data presentation. The most recent state legislative district boundaries collected by the Census Bureau are for the 2022 election year and were provided by state-level participants through the RDP.
Facebook
TwitterNOTE: This feature Supersedes All Previous EditionsData is in WGS84 CoordinatesThis data was compiled by the Washington Office of Superintendent of Public Instruction (OSPI) to provide location and attribute information regarding currently active public schools in the State of Washington. This layer should match the current School Directory published by OSPI from the Education Data System (EDS). This layer includes Charter Schools, Tribal Compact Schools, and Vocational/Technical Skills Centers previously published separately.
Facebook
TwitterThe Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" “Standard” (http://pubs.usgs.gov/tm/11/a3/). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit (6th level) for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries are being developed where partners and data exist and will be incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications.
Facebook
TwitterIn 2007, Washington State legislators requested a trails database, but funding to complete that statewide project was not made available at the time.
In 2009, the Federal Government outlined the need for trails database schema in their Data Standards Review Committee, stressing the efficiency in management decisions that a streamlined database can provide.
“The collection, storage and management of trail related data are important components of everyday business activities in many federal and state land-managing agencies, trail organizations and businesses. From a management perspective, trails data must often mesh closely with other types of infrastructure, resource and facility enterprise data.”
In 2014, the Washington State Office of the Chief Information Officer's (OCIO) Geospatial Program Office acquired a Nonhighway and Off-Road Vehicle Activities (NOVA) Program grant through the Washington State Recreation and Conservation Office (RCO) giving the OCIO initial funding to develop a statewide trails database based on Federal Geographic Data Committee standards. Using the same standard for all trails data will allow land managers and recreational users throughout the state to access and use the data regardless of administrative boundary.
"Data standards will make it easier for trail information to be accessed and exchanged and used by more than one individual agency or group…Ease in sharing data increases the capability for enhanced and consistent mapping, inventory, monitoring, conditions assessment, maintenance, costing, budgeting, information retrieval, and summary reporting for internal and external needs.”
Along with streamlining data and facilitating efficiency in management practices across agencies, the database will provide a source of trails information that is open and free to the public.The 2016 State Legislature provided additional funding from the Nonhighway and Off-road Vehicle Activities Account to the Office of the Chief Information Officer to continue work on the database.
Additional details about the project can be found here:
Washington State Trails Map
Please note that this map and its component services have been designed to work together as part of the web application.
Facebook
TwitterThis map displays the most recent summary streamflow values within the state of Washington from gages maintained by the Washington State Department of Ecology and the United States Geological Survey (USGS). The streamflow symbols reflect the magnitude of the most recent estimated flows relative to historic flows that occurred in past years on the current date at that particular stream gaging station. Generally, streamflows greater than the 75th percentile are considered above normal. Flows between the 25th and 75th percentiles are considered normal, and flow less than the 25th percentile are considered low.Differences exist in Ecology’s and USGS’ presentation of their respective flow information. The flow data displayed for the Ecology gaging stations are calculated overnight from statistics measured from the previous day’s flow so that all streamflow data displayed for the Ecology gaging stations are relative to the previous day’s flow.USGS reports flow in near real-time meaning the reported flow estimates are updated several times a day and are no more than 6 hours old. The flow data displayed for the USGS gaging stations reflects the near real-time flows relative to the historic record of flows on the current date.For more information on the Department of Ecology River and Stream Flow Monitoring program, visit http://www.ecy.wa.gov/programs/eap/flow/index.html.For more information on the USGS Water Watch program, visit http://waterwatch.usgs.gov/.Questions or concerns about the map and data displayed should be directed to gis@ecy.wa.gov.All data displayed are provisional and subject to significant change.
Facebook
TwitterThe Geographic Names Information System (GNIS) is the Federal standard for geographic nomenclature. The U.S. Geological Survey developed the GNIS for the U.S. Board on Geographic Names, a Federal inter-agency body chartered by public law to maintain uniform feature name usage throughout the Government and to promulgate standard names to the public. The GNIS is the official repository of domestic geographic names data; the official vehicle for geographic names use by all departments of the Federal Government; and the source for applying geographic names to Federal electronic and printed products of all types. See http://geonames.usgs.gov for additional information.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
State Routes are depicted as lines with State Route identifiers. Each SR is symbolized with a single line whether or not the highway is divided. Entrance, exit and collector/distributor ramps are not included, but spurs, couplets and reversible lanes are. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.
Facebook
TwitterThis image service shows historical floating kelp locations along the Washington Coast and Puget Sound. It combines nine map sheets that were originally published in 1912. They summarize field surveys from 1911-1912. The Puget Sound surveys were conducted by Rigg. The maps were scanned and georeferenced, and the image service is hosted by the Washington Department of Natural Resources.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
The NHD is a national framework for assigning reach addresses to water-related entities, such as industrial discharges, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network, much like addresses on streets. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities--and any associated information about them--can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, land use and population, to help understand and display their respective effects upon one another. Furthermore, because the NHD provides a nationally consistent framework for addressing and analysis, water-related information linked to reach addresses by one organization (national, state, local) can be shared with other organizations and easily integrated into many different types of applications to the benefit of all.The WA State National Hydrography Dataset (NHD) is the standard hydrography for Washington. NHD Waterbody along with WA NHD Area represent the polygon water features. NHD Flowline contains the linear watercourses. NHDWaterbody types and their corresponding FType Codes are Estuary(493), LakePond(390), SwampMarsh(466), Constructed Reservoir(436), Ice Mass(378), and Playa(361). The WA State National Hydrography Dataset (NHD) is the standard hydrography for Washington. NHD Lines represent linear NHD hydrographic landmark features used for cartographic representation. Some of these are: Bridge, Dam, Flume, Gate, Levee, Sounding Datum Line. NHD Lines should not be confused with NHD Flowlines which are the major blue line data. NHD Line data for Washington are developed at a resolution of 1:4,800 to 1:24,000. This dataset was extracted from and projected into WA State Plane Coordinates South. The National Hydrography Dataset (NHD) is a feature-based database that as a whole interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. This high-resolution NHD, generally is developed at 1:24,000/1:12,000 scale, but many areas of Washington State have been improved to 1:4800 scale. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee. A detailed data dictionary is available at https://nhd.usgs.gov/userguide.html?url=NHD_User_Guide/Feature_Catalog/NHD_Feature_Catalog.htm
Facebook
TwitterClick 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
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
Facebook
TwitterPublic Land Survey (PLS) Township Subdivision. The primary subdivision of a PLSS Township. It may be a PLSS Section Area, a Donation Land Claim, a PLSS Tract, or a Protracted Block.WA Public Land Survey Sections Metadata
Facebook
TwitterThis web map contains datasets representing the National Hydrography Dataset (NHD) of Washington State, labels for NHD features, and the Watershed Boundary Dataset (WBD) basins for Hydrologic Unit Code (HUC) levels 4, 8, and 12. The NHD dataset has been adopted as the Washington State hydrography standard. The NHD is a national framework for assigning reach addresses to water-related entities, such as industrial discharges, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network, much like addresses on streets. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities--and any associated information about them--can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, land use and population, to help understand and display their respective effects upon one another. Furthermore, because the NHD provides a nationally consistent framework for addressing and analysis, water-related information linked to reach addresses by one organization (national, state, local) can be shared with other organizations and easily integrated into many different types of applications to the benefit of all.This high-resolution NHD, generally developed at 1:24,000/1:4,800 scale. Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.This map contains a BETA version of WaterType attached to the Skagit River Basin NHDflowlines. This Beta version of the Watertype is the result of a pilot project and will be refined over the next six months. The field is for users of NHD who want access to Water Type and who are not under Forest Practices rules. The WaterType uses Shorelines Master Program type S streams and Fish Presence Data from both WA Dept Natural Resources and WA Dept Fish and Wildlife.
Facebook
TwitterWater Resource Inventory Areas (WRIA) for Washington State at 1:24,000 scale. WRIAs were formalized under WAC 173-500-040 and authorized under the Water Resources Act of 1971, RCW 90.54. Ecology was given the responsibility for the development and management of these administrative and planning boundaries. These boundaries represent the administrative under pinning of this agency's business activities. The original WRIA boundary agreements and judgments were reached jointly by Washington's natural resource agencies (Ecology, Natural Resources, Fish and Wildlife) in 1970.
Facebook
TwitterThe Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" “Standard” (http://pubs.usgs.gov/tm/11/a3/). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit (6th level) for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries are being developed where partners and data exist and will be incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications. Some GNIS names in this data are offensive so the word “Negro” has been replaced with the hydrologic unit code while the process of reviewing and changing the names is ongoing through official channels.
Facebook
TwitterUnincorporated 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.