ArcGIS REST Services Directory
JSON

Layer: BdyPlan_LMP_GeographicArea (ID:1)

View In:   Map Viewer

Name: BdyPlan_LMP_GeographicArea

Display Field: GEOG_AREA_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Contextual Definition of Geographic Areas: It is required for every National Forest to have a Land Management Plan (LMP), often referred to as a Forest Plan. Every plan must have management areas or geographic areas or both. The 2012 Planning Rule defines geographic areas as “spatially contiguous land areas identified within the planning area. A geographic area may overlap with a management area.” The Forest Service Handbook states that “geographic areas are based on place, while management areas are based on purpose. A typical geographic area map represents large areas that have desired conditions with a range of possible resource management emphases. Rather than a management emphasis map, a geographic area map tends to focus on a place (Red Rock Canyon, Mount Whitney, or perhaps a specific watershed).” Geographic Areas have an associated place name naming convention. They are identified in a LMP and are identified with plan components that detail how these areas will be managed. These areas are based on specific “places” and not “themes” like Management Areas. For example, “Hanging Lake Meadow” is a Geographic Area, but a “ski-area” is an example of a Management Area. This feature class shows the geospatial extent of each Geographic Area within land management plans, with pertinent metadata and includes data from both the 1982 and 2012 planning rules. This schema can also be used as a template to build data regionally or for individual units. Characteristics: - Based on “place”. - Has a different set of plan components than Management Areas. - Generally contiguous polygons, but may be a multi-part polygon due to private lands. - Polygons must be semi-contiguous and in close proximity. - Can overlap with Management Areas or Designated Areas. - Do not overlap with other Geographic Areas. - Cannot extend outside the land management plan or Administrative Forest Boundary., Contextual Definition of Geographic Areas: It is required for every National Forest to have a Land Management Plan (LMP), often referred to as a Forest Plan. Every plan must have management areas or geographic areas or both. The 2012 Planning Rule defines geographic areas as “spatially contiguous land areas identified within the planning area. A geographic area may overlap with a management area.” The Forest Service Handbook states that “geographic areas are based on place, while management areas are based on purpose. A typical geographic area map represents large areas that have desired conditions with a range of possible resource management emphases. Rather than a management emphasis map, a geographic area map tends to focus on a place (Red Rock Canyon, Mount Whitney, or perhaps a specific watershed).” Geographic Areas have an associated place name naming convention. They are identified in a LMP and are identified with plan components that detail how these areas will be managed. These areas are based on specific “places” and not “themes” like Management Areas. For example, “Hanging Lake Meadow” is a Geographic Area, but a “ski-area” is an example of a Management Area. This feature class shows the geospatial extent of each Geographic Area within land management plans, with pertinent metadata and includes data from both the 1982 and 2012 planning rules. This schema can also be used as a template to build data regionally or for individual units. Characteristics: - Based on “place”. - Has a different set of plan components than Management Areas. - Generally contiguous polygons, but may be a multi-part polygon due to private lands. - Polygons must be semi-contiguous and in close proximity. - Can overlap with Management Areas or Designated Areas. - Do not overlap with other Geographic Areas. - Cannot extend outside the land management plan or Administrative Forest Boundary.

Copyright Text: ,

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field: GlobalID_2

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 4/24/2026 3:45:56 PM

Schema Last Edit Date: 4/24/2026 3:45:53 PM

Data Last Edit Date: 4/23/2026 9:35:38 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat