Data format: Shapefile
File or table name: az_fos
Coordinate system: Universal Transverse Mercator
Theme keywords: Boundaries, Environment, BLM, Administrative Boundaries, Field Office, District Office
| BLM Field Office Boundary Polygons | |
|
|
Data format: Shapefile File or table name: az_fos Coordinate system: Universal Transverse Mercator Theme keywords: Boundaries, Environment, BLM, Administrative Boundaries, Field Office, District Office |
|
Abstract:
Polygon features for active BLM Field Office Administrative areas. |
|
Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.
Polygon features for active BLM Field Office Administrative areas.
Polygon features for active BLM administrative unit boundary polygons. These polygons should represent lower level administrative units known as Field Offices. Higher level administrative units (District Offices) may be derived from the attribution in this feature class.
publication date
The Bureau of Land Management (BLM) provides these geographic data "as is." BLM makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. BLM further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.
One North Central Ave.
Data has been topologically checked - no errors were found
Data is considered complete
Horizontal accuracy is +/- 100 ft.
Original data was digitized from 1:100,000 scale manuscripts circa 1990. Numerous updates and positional accuracy improvements have been done over the years. Recent improvements include integrating appropriate linework with the BLM Geographic Coordinate Database (GCDB)
One North Central Ave.
Dataset copied.
Dataset copied.
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
ESRI
An alpha-numeric string that represents a specific Field Office
Tucson Field Office
Lower Sonoran Field Office
Yuma Field Office
Lake Havasu Field Office
Safford Field Office
Kingmand Field Office
Grand Canyon/Parashant National Monument
Arizona Strip Field Office
Hassayampa Field Office
The official name of the Field Office
BLM
The type of administrative office
Area of feature in internal units squared.
ESRI
Effective Date: (Logical Attribute: Administered BLM Land Location Effective Date. The date on which an area of BLM Land becomes the responsibility of a BLM administrative unit) Effective date when the administrative unit number, name, or physical boundary was changed. The date will be in the format of mm/dd/yyyy. The effective date will occur on or after the approval date. If the effective date is unknown for the initial data load, the default date will be used. Changes that occur after implementation of the standard must use the actual effective date. Default: 09/09/9999
BLM
Approval Date: (Logical Attribute: BLM Organization Unit Approval Date. The date on which the BLM Washington Office or Assistant Secretary, Land and Minerals Management approved or concurred with the change to the organization unit number, name and/or administrative unit boundaries.) The date that the change to the administrative unit was approved. If the approval date is unknown for the initial data load, the default date will be used. Changes that occur after implementation of the standard must use the actual approval date. Format as mm/dd/yyyy. Default: 09/09/9999
BLM
Parent Admin Code: This is the parent of the administrative unit being mapped. An Administrative State may be the parent of District Offices, Field Offices, or other autonomous areas such as National Monuments. A District Office is the parent of Field Offices. This attribute may be used to derive the boundaries of the parent administrative unit, and should reflect organizational tiers. The BLM administrative unit/office that is a combination of Administrative State Code and Administrative Office Code that fully identifies the geographic area which has jurisdiction over the lands. This is an eight-character code. In the FPPS Organization Codes, use the last eight characters (e.g. "AK030900" from LLAK030900). (Logical Attribute: BLM Organization Unit Parent Identifier. The identifier for the administrative unit that is a tier above this unit. The code that indicates the formal grouping of positions at into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure.)
BLM
Administrative State Code: Two letter, upper case abbreviation for the administrative state office. The current list of values is: AK, AZ, CA, CO, ES, ID, MT, NM, NV, OR, UT and WY. In the FBMS Organization Codes, use the second 2 characters (after the LL). (e.g. LLAK039000). Attribute Domain Assignment: DOM_ADMIN_ST (Logical Attribute: State Alphabetic Code. An alphabetic abbreviation that represents each of the 50 states of the United States, the District of Columbia, the outlying areas of the United States, and associated areas. FIPS PUB 5-2.) An administrative unit that identifies the state or geographic area which has administrative jurisdiction over lands, and cases. The land for a case may not be physically located in the associated administrative state. Only those states that are BLM administrative states are in the domain for this entity. Example: Montana is the Administrative State for public lands in the geographic States of Montana, South and North Dakota.
BLM
Alaska
BLM
Arizona
BLM
California
BLM
Colorado
BLM
Eastern States
BLM
Idaho
BLM
Montana
BLM
New Mexico
BLM
Nevada
BLM
Oregon
BLM
Utah
BLM
Wyoming
BLM
One North Central Ave.
One North Central Ave.