An area depicting ownership parcels of the surface estate. Each surface ownership parcel is tied to a particular legal transaction. The same individual or organization may currently own many parcels that may or may not have been acquired through the same legal transaction. Therefore, they are captured as separate entities rather than merged together. This is in contrast to Basic Ownership, in which the surface ownership parcels having the same owner are merged together. Basic Ownership provides the general user with the Forest Service versus non-Forest Service view of land ownership within National Forest boundaries. Surface Ownership provides the land status user with a current snapshot of ownership within National Forest boundaries.

AFRAA Data Upgrade & Transition Plan for 2025 Fire SeasonGiven the mission-critical nature of AFRAA dataset and federal mandates, the FS Enterprise Data Warehouse (EDW) and AFRAA data stewards will fully support the legacy map services throughout the 2025 fire season before retirement. The latest 2025 data, approved by Forest Service Regional Forester and GIS Coordinators, has been integrated into legacy schemas, ensuring authoritative data while maintaining backward compatibility for applications relying on legacy endpoints.What You Need to KnowWhere is the New Data Most users will use the new map image service REST endpoints:https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Aquatic_01/MapServerhttps://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Terrestrial_01/MapServerMetadata is available in these ArcGIS items that reference the new map services:Fire_AerialFireRetardantAvoidanceAreas_Aquatic (Landing Page)Fire_AerialFireRetardantAvoidanceAreas_Terrestrial (Landing Page)Sync Enable ArcGIS Online Hosted Feature Services:Aquatic Hosted Feature ServiceTerrestrial Hosted Feature ServiceInternal FS users can make direct SDE connections (see detailed instructions on the AFRAA SharePoint ).Downloadable Data from the FS GeoData Clearinghouse:Fire_AerialFireRetardantAvoidanceAreas_Aquatic.gdb.zipFire_AerialFireRetardantAvoidanceAreas_Terrestrial.gdb.zipWhen Will the Legacy Product Be Retired?March 14, 2025 – New terrestrial map service available, and a deprecation watermark is added to the legacy service.March 14, 2025 - Region 3 approved 2025 aquatic data via the legacy service endpoint.April 1, 2025 – All 2025 approved data loaded into both new and legacy services.April 1, 2025 – New aquatic service published, and a deprecation watermark is added to the legacy service.April 1, 2025 – Legacy download products removed from the Clearinghouse and replaced with the new versions.April 7, 2025 – Sync enabled Hosted Feature Services published to ArcGIS OnlineSTOPPING LEGACY SERVICES HAS BEEN POSTPHONED DUE TO GOVERNMENT SHUTDOWNTBD (previously slated for October 1, 2025) – Legacy services stopped. Fire personnel can contact SM.FS.afraa@usda.gov during regular business hours if unknown dependencies are discovered. The services will be restarted if needed.November 1, 2025 – Unless an extension is requested, legacy services will be deleted, and all feature classes will be removed from EDW, making the data inaccessible.What Products Are Being Deprecated?Terrestrial Map Services & Associated Feature ClassesLegacy Terrestrial:https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_01/MapServerS_USA.AerialFireRetardantAvoidanceNew Authoritative Terrestrial:https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Terrestrial_01/MapServerS_USA.Fire_AerialFireRetardantAvoidanceAreas_TerrestrialAquatic Map Services & Associated Feature ClassesLegacy Aquatic:https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantHydrographicAvoidanceAreas_01/MapServerS_R01.AFRAA_HydroS_R02.AFRAA_HydroS_R03.AFRAA_HydroS_R04.AFRAA_HydroS_R05.AFRAA_HydroS_R06.AFRAA_HydroS_R08.AFRAA_HydroS_R09.AFRAA_HydroS_R10.AFRAA_HydroNew Authoritative Aquatic Map Service and Feature Class:https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Aquatic_01/MapServerS_USA.Fire_AerialFireRetardantAvoidanceAreas_Aquatic

Forest Service Enterprise Data Warehouse (EDW) Surface Ownership updated with saltwater shoreline Mean High Water Combined Source (MHW_CS). Forest service Shoreline Integration Tool was employed to accomplish this update. Note, Forest service land areas were updated to MHW_CS shoreline, while non-forest service areas were not. The Forest Service prepared this dataset to support the Tongass National Forest (TNF) plan revision GIS analysis. This 2025 update builds upon the 2024 TNF forest plan assessment analysis incorporating all available NOAA CUSP shoreline updates, including additional Lidar derived shoreline. Forest Service Lands Team is updating Land Status Record System (LSRS) in 2024/2025 with expected completion and publication to EDW in 2026. These data may not be used to determine title, ownership, legal descriptions or boundaries, legal jurisdiction, or restrictions that may be in place on either public or private land. Jason Gaudreau 20250506

Area Units are geographic areas established by Districts to manage outfitter/guide activities developed by each district. Geographic areas are identified by similar features, Land Use Designation, and recreation experience.

Area Units are geographic areas established by Districts to manage outfitter/guide activities developed by each district. Geographic areas are identified by similar features, Land Use Designation, and recreation experience.

FS Recreation One App Offline Sync Enabled View

This layer shows new stand delineations for young growth as prepared by Terra Verde Inc. under the Combined Cost Share Agreement (CCSA) and delivered to the USFS in September 2020. This is the working layer developed from that work and includes an updated birth year attribute for stands that were coded "0" in the CCSA delivery. This layer includes only young growth stands. Old growth and non-forest stands are not included.This young growth timber type map layer shows each individual young-growth stand on the Tongass, lists its acreage and describes its structure by specifying (1) species composition (i.e., dominant species), (2) tree size (i.e., overstory height), and (3) stocking (i.e., per cent crown closure) in one spatially integrated attribute (timber type code). The year the stand is expected to reach the "2-log" condition (an estimation of commercial merchantability) is also attributed along with basin, year of origin, age class 5 and 10 and site grid attributes needed to support the FPS growth and yield model. .

A route feature stores the spatial locations (geography) of the road. These feature classes have an (M) value or measure on their vertices. A route system depicts all roads within or in close proximity to an administrative unit. A road is a motor vehicle travel way over 50 inches wide, unless classified and managed as a trail. This feature is only SPATIAL ROAD DATA, other data (open, closed, jurisdiction, maintenance level) is stored in INFRA. Used to link spatial roads to INFRA data, ROAD NO., BMP, EMP and Calibration. Routed roads are a single spatial line, all have data in INFRA and this data must be attached. Routed roads need to have INFRA data table attached by use of R10 Geospatial Interface (GI) tool and Visualization named Roads with Core Attributes RSW - This creates an output roads layer and adds the following fields from the INFRA database at NITC: name, lanes, service life, system, surface type, jurisdiction, objective maintenance level, operational maintenance level, route status, functional class and primary maintainer. Routed ROADS CAN HAVE OTHER DATA TABLES ATTACHED, (R10 Stream Data Point-RSW, Road Points -RSW, Bridges-RSW, MVUM Roads and Transportation Atlas. A road may be classified or unclassified. Classified roads are roads within the National Forest System lands planned and managed for motor vehicle access including State roads, county roads, private roads, permitted roads, and Forest Service roads. Unclassified roads are roads not intended to be a part of nor managed as a part of the forests transportation system, such as temporary roads, and unplanned, unengineered, unauthorized off-road vehicle tracks and abandoned travel ways. Route measurements and route directions must correspond to those stored in the INFRA Oracle table RTE_BASICS. Associated National Application: INFRA Travel Routes. IWeb Infra Roads webpage http://basenet.fs.fed.us/support/help/roads/. All routed roads are required to have data in INFRA and all roads having data in INFRA are required to be routed.

This layer is generated by a model based on the following layers: Stream_LN, Stream_PL, Lake_PL, Soil, and uses look up tables TLMP_StrmBuf containing buffer distances and common_soil_LUT used to identify riparian associated soils and wetland fens. Larger stream channels are buffered directly from the Stream_PL polygons and combined with the stream line buffers. Model Logic: The RMA model buffers streams based on the channel process and fish value attributes. Buffer distances described in Appendix D of the Tongass National Forest plan and coded in the lookup table TLMP_StrmBuf. The model buffers lakes that are greater than 3 acres in size or have a class 1 stream intersecting by a distance of 30.7 meters. The Stream_PL polygons are buffered by 39.6 meters. The fresh water portions of Stream_PL and lakes are merged and coded as ‘F’ to differentiate the wetted area from the riparian buffer. The common_soil_lut is used to select the soil polygons to be added to the Riparian Management Area. Riparian associated soil map units (SMU’s) are flagged via the RIPAR = ‘Y’ attribute. Additionally, riparian associated wetland fens (see table below) will be included where associated with Floodplain, Glacial Outwash, moderate-gradient mixed-control and Palustrine process group and lake buffers.Wet_Hab CodeDescriptionEEstuarine Emergent or scrub/estuarineEFEstuarine EmergentESEstuarine mudflat, subtidalEIEstuarine mudflat, intertidalMTEmergent tall sedge muskegBWShrub/alder-willowBWSScrub/shrub Alder-Willow-Emergent SedgeThe selected soil polygons are then merged with the hydrology buffers and processed to create the final Riparian Managment Area feature class.

Contact information for the elected officials for Strathcona County for 2021 - 2025. This dataset conforms to the Represent CSV Schema for elected officials' contact information. For more information on Represent please visit http://represent.opennorth.ca/

This polygons dataset displays the areas recommended for wilderness designation for the Chugach National Forest's 2019 Revised Land Management Plan.The forest supervisor for the Chugach National Forest is required by the planning rule (36 CFR 219.7 (v)) to “identify and evaluate lands that may be suitable for inclusion in the National Wilderness Preservation System, and determine whether to recommend any such lands for wilderness designation.” Any lands the forest supervisor recommends for wilderness area designation through forest plan revision would be a preliminary administrative recommendation and are referred to here as recommended wilderness areas. Designation of wilderness is reserved to Congress. Nearly 99 percent of the Chugach National Forest was included in the inventory as suitable for wilderness area designation. The national forest has ecosystems generally appearing to be affected primarily by the forces of nature; outstanding opportunities for solitude or for a primitive and unconfined type of recreation; areas of sufficient size to make preservation and use in an unimpaired condition practicable; and areas that can be managed to preserve wilderness characteristics. Additionally, many areas of the national forest contain ecological, geological, or other features of scientific, educational, scenic, or historical value. The national forest does not have any designated wilderness areas. The Nellie Juan-College Fiord Wilderness Study Area in Prince William Sound, designated in 1980 by Congress through ANILCA, has been managed to maintain the area’s presently existing character and potential for designation into the National Wilderness Preservation System. The Forest Supervisor exercised their discretion and chose which areas to analyze for wilderness recommendation within the NEPA process resulting in alternatives for recommended wilderness of differing acreage levels. All recommended wilderness acreages for all alternatives are located within the wilderness study area boundary. This dataset contains the areas recommended for wilderness designation under the selected alternative.This dataset was used for geospatial analysis and/or cartographic production during the revision process of the USDA Forest Service, Chugach National Forest’s Land Management Plan. The data were compiled from multiple sources and the USFS makes no guarantees about the accuracy or completeness of the data.

These polygons were pulled from the NFPORS Treatment Poly service on 12/15/2024 and only include BLM Treatment Polygons (filtered for Bureau = BLM). They would include all fuels treatment polygons that were put into the BLM SDE VTRT layer that had a correct associated NFPORS Treatment ID and were thus bulk uploaded at the NOC to NFPORS and attached to the corresponding treatment within NFPORS. This service does not include all polygons in the archived BLM SDE VTRT layer that did not have a correct associated NFPORS Treatment ID. This data is static as the BLM stopped using the NFPORS Application for fuels treatment accomplish reporting at the end of FY24. For FY25 and beyond BLM Fuels Treatment Data, please see the BLM IFPRS Actions service, also located in NIFC AGOL.BLM IFPRS Actions: https://nifc.maps.arcgis.com/home/item.html?id=00818aff23654e5b9c602c9adfdd5fc3Source: https://www.nfpors.gov/Update Frequency: Static/Historical. Last updated December 2024.Area Covered: Nationwide

This dataset shows information about the USDA Forest Service recreation sites used to populate the public facing web pages. This information is the descriptive and qualitative information used to set appropriate expectations for visitor use.

Planning, Zoning Sierra Vista Feature Service

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved. We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. Purpose County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use. Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon) Cartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov Field and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. AccuracyCDTFA"s source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city). Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above. Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions). Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

Locations used by the Outfitter Guides of SE Alaska.

An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area.

FS Recreation One App Offline Sync Enabled View

This feature class consists of the trail routes on the Tongass National Forest. A route feature stores the spatial locations (geography) of the trail. These feature classes have an (M) value or measure on their vertices. A route system depicts all trails within or in close proximity to an administrative unit. A trail is a linear feature constructed for the purpose of allowing the free movement of people, stock, or Off Highway Vehicles (OHV). Route measurements and route directions must correspond to those stored in the INFRA Oracle table RTE_BASICS. Associated National Application: INFRA Travel Routes INFRA Web Page: http://basenet.fs.fed.us/support/help/trails/. New field called Data_Source was added but because these are routed trails based on trail number, and many trails have a mix of data sources, this field is not populated. To see the data source see the feature class Trail_Ln which allows a trail to be split so different data sources along the trail can be identified.

Sign Posts Locations For the City of Westbrook. This feature service has full create, delete, query, update, and sync functionality.