20241221
15002700
1.0
FALSE
tmap_tma_poly
002
-
Projected
GCS_North_American_1983
Linear Unit: Meter (1.000000)
NAD_1983_UTM_Zone_12N
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.1.0'><WKT>PROJCS["NAD_1983_UTM_Zone_12N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-111.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26912]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26912</WKID><LatestWKID>26912</LatestWKID></ProjectedCoordinateSystem>
20241221
13421600
20241221
13421600
150000000
5000
dataset
Bureau of Land Management Arizona State Office GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
(602) 417-9200
(602) 417-9556
20241221
ArcGIS Metadata
1.0
https://gbp-blm-egis.hub.arcgis.com/pages/arizona
File Geodatabase Feature Class
Bureau of Land Management Arizona State Office GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
(602) 417-9200
(602) 417-9556
Name: Bureau of Land Management Arizona State Office GIS Manager
Organization: Arizona State Office, Bureau of Land Management
Position: GIS Manager
Role: Point of Contact
BLM-AZData
Bureau of Land Management
ground
polygon
tma
tmap
travel management plan
BLM-STATE
Arizona
BLM-THEME
Authorization
Disturbance
Geospatial
Management
Recreation
REFERENCE-STATE
AZ
United States
USA
Western States
1
-114.697716
-108.883062
37.039404
31.277106
publication date
20220418
BLM AZ Travel Management Areas and Plans (TMAP) Travel Management Areas (TMA) Polygon
20220418
vector digital data
U.S. Department of the Interior, Bureau of Land Management (BLM)
Arizona State Office, Bureau of Land Management
Bureau of Land Management Arizona State Office GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
(602) 417-9200
(602) 417-9556
Name: GIS Manager
Organization: Arizona State Office, Bureau of Land Management
Position: GIS Manager
Role: Point of Contact
Bureau of Land Management Arizona State Office GIS Manager
Bureau of Land Management
Arizona State Office GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
(602) 417-9200
(602) 417-9556
Name: GIS Manager
Organization: Arizona State Office, Bureau of Land Management
Position: GIS Manager
Role: Point of Contact
This polygon feature class represents the spatial extent and boundaries for the Travel Management Area (TMA) polygons as part of the Bureau of Land Management's (BLM's)Travel Management Areas and Plans (TMAP) feature-dataset. TMA polygons are used for planning purposes only and can exist without a Travel Management Plan (TMP) or Resource Management Plan (RMP). TMAs are an optional planning tool to frame transportation issues and help delineate travel networks that address specific uses and resource concerns. Travel management is an approach to establishing networks of roads for travel and transportation including areas for both motorized and non-motorized uses. A National BLM TMAP data standard is essential for collecting the landscape-scale level geospatial data necessary to identify management opportunities and challenges that may not be evident when managing smaller land areas. TMAP data not only serve the crucial function of improving BLM travel and transportation planning, but are also invaluable to numerous BLM programs affected by travel and transportation management (e.g. water and air quality, wildlife habitat fragmentation, habitat mitigation. engineering, realty, and cultural resources).
In 2020, the BLM Arizona State Office (ASO) Geospatial Information System (GIS) team initiated geoprocessing steps for off-highway vehicle (OHV) and TMA footprints within the TMAP feature-dataset. This effort was executed in order to establish more precise arc and polygon footprints. Please see the Lineage section of this metadata for information regarding changes to the tmap_tma_poly.
This feature class depicts the boundaries for the AZ Bureau of Land Management Travel (BLM) Management Areas (TMA) polygons as part of the Travel Management Areas and Plans (TMAP) feature-dataset.
Bureau of Land Management, Arizona
Bureau of Land Management Arizona State Office GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
(602) 417-9200
(602) 417-9556
Arizona
Authorization
AZ
boundaries
Bureau of Land Management
Disturbance
environment
Geospatial
ground
Management
polygon
Recreation
tma
tmap
transportation
travel management plan
United States
USA
Western States
These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.
The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. 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, or for general or scientific purposes, 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 the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.
None, these data are considered public domain.
Esri ArcGIS 10.7.1.11595
A published revision of the Department Manual Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm).
Last metadata review date: 20200806
These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.
None, these data are considered public domain.
The expected horizontal accuracy is +/- 40 feet at a 24,0000 scale. Although this data is work in progress, its spatial accuracy can be found from the reliability and/or the error in X, Y coordinates contained in the Public Land Survey System (PLSS) points feature class. This represents the best estimate of spatial accuracy on a point-by-point basis.
This data is topologically aligned with Arizona's Public Land Survey System (PLSS) and other related datasets such as Surface Management Agency (SMA) boundaries, Administrative Unit Boundaries (ADMU), Land Use Planning Areas (LUPA), National Monument and National Conservation Areas (NM NCA) within the National Landscape Conversation System (NLCS), and associated feature classes within Travel Management Areas and Plans (TMAP).
Foundational to this data is the expectation that it topologically aligns where possible and appropriate with the official published version of BLM Public Land Survey System (PLSS) Cadastral National Spatial Data Infrastructure (CAD NSDI) GIS Data. The expected overall accuracy (correctness) of the non-spatial data values in the required attribute fields should be 95%. This accuracy is a target and is dependent on data from a variety of sources. Each section of attributes may be measured separately but the overall accuracy target is 95% for the data values.
Dataset is considered in progress for the information presented. Maintenance to be performed as needed.
This official BLM Data Management handbook contains information about how data is administered, managed, and tracked. This handbook discusses how the BLM operates with regard to data development and design, quality, metadata, and business rules. The information this resources contains also pertains to geospatial data.
H-1283-2 Data Administration and Management Handbook
H-1283-2 Data Administration and Management Handbook
2014-12-05
Release 1-1762
U.S. Department of Interior, Bureau of Land Management (BLM)
This document describes the business and the associated requirements for the national data standard for the geospatial dataset. It’s intended to be the basis for the database design. The business requirements ensure the right information is being designed in the database standard.
TMAP BUSINESS RULES
2019-01-31
Version 1.0
U.S. Department of Interior, Bureau of Land Management (BLM)
The Arizona State Office (ASO) BLM geospatial information system (GIS) team reviewed several entries for tmap_tma_poly that did not contain appropriately formatted completion dates but rather an abbreviation of "FY20". Entries without a month and/or day were entered with a '1' as the place holder. For Example: the value "FY2017" was reformatted to "1/1/2017". The BLM TMAP Implementation Guidelines and Business Rules documents require an estimation of completion dates if an actual completion date could not be found for the attribute field "TMP_CMPLTN_DT". Guidelines instruct the user to include the first or last day of the month as a valid entry. For more details regarding the validity of the recorded completion dates, please refer to the attribute "TMP_COMP", which indicates if the completion date value was accurate or a prediction.
2018-04-25
GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
The BLM TMAP implementation guidelines indicate that the attribute "TMP_ID" is the same value as the identification numbers associated with environmental documentation (For example: environmental impact statement (EIS), National Environmental Protection Act (NEPA), or environmental assessment(EA)). The number format is represented as follows: DOI-BLM-AZ-A000-2012-0001-NEPA, VBScript to generate the name: [TMP_ID] = "DOI-BLM" + "-" +!ADMIN_ST! + "-" + !ADM_UNIT_CD! + "-" + !TMP_NR!At the end of this is the Document type (EIS, NEPA, or EA). The TMA's and TMP's related to BLM's Arizona Strip field office were addressed in a single EIS that does not have an identification number and is referred to by name. The document name is: "Arizona Strip Proposed Plan/FEIS".
2018-05-19
GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
GIS analysts and third-party contractors reviewed the TMAP feature-dataset (including TMA) throughout 2018 to 2020. Subject matter experts and field and/or district office staff were also consulted to ensure accuracy of data. Emphasis was placed on travel management area and plan names, completion status of plans, and overall topology.
TMA polygons were cross-referenced against associated datasets (Land-use Planning Areas, Administrative Unit Boundaries, and National Monument and National Conservation Areas). TMA boundaries that were not aligned appropriately to adjacent footprints, were updated using various ArcGIS Desktop 10.7 editing and topology tools such as "clip", "split" and "align to edge". Updates to TMA boundaries were further validated by running topology and data reviewer rules such as "must not overlap" and "polygon sliver check". Please note that TMA boundaries will require improvements as referencing feature-datasets such as Public Land Survey System (PLSS), Land-Use Planning Areas (LUPA), Administrative Unit Boundaries (ADMU) are updated and made available.
2020-07-09
GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
GIS acreage values for the field "GIS_ACRES" were generated by use of the 'Calculate Geometry' function where area = acres(US). Please note that this calculation was derived with the tmap_tma_poly in a NAD83 UTM Zone 12 projection.
2020-08-06
GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
20003-3503
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
BLM land acreage values for the field "BLM_ACRES" were generated by use of the 'tabulate intersect' tool. This tool was executed by intersecting the BLM surface management area (SMA) layers for both California and Arizona with the tmap_tma_poly feature class. This execution was performed in a NAD83 UTM Zone 12 projection. A definition query of SMA ID =2 (where 2 = BLM-owned land) was applied to both SMA layers prior to tabulation. Tabulation results were verified by clipping test copies of SMA (BLM-owned land) to the TMA and TMP boundaries. Results were then applied to the field "BLM_ACRES" by use of the 'Field Calculator' tool.
2020-08-06
GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
The field "REG_TMP_NM" was updated to reflect the same names listed in the "TMA_NM" field. The "REG_TMP_NM" field will be updated in the future to "TMP_NM" in compliance with National implementation guidelines, as there is no existence of regional naming conventions for the TMAP dataset.
2020-08-06
GIS Manager
Arizona State Office, Bureau of Land Management
GIS Manager
One North Central Ave. Suite 800
Phoenix
AZ
85004
US
ASOWEB@blm.gov
Monday - Friday, 8 AM - 4 PM, Mountain Standard Time
0
EPSG
6.11(3.0.1)
tmap_tma_poly
The polygon footprint that defines travel management areas.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Feature Class
0
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
TMA_ID
Travel Management Area Identifier
String
19
0
0
A unique identifier used to uniquely identify an individual Travel Management Area. A 19 alpha-numeric digit unique identifier which is the concatenation of: · Prefix “TMA” · Administrative State Code (2 characters) · The Administrative Unit Code (8 characters) · TMA Number (3 characters)
Travel Management Areas and Plans Implementation Guidelines ver. 1.0
TMA_NM
The name given to the Travel Management Area.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Travel Management Area Name
String
255
0
0
TMA_NR
A 3 digit sequential number starting at 001 for a specific travel management area that falls within the jurisdictional area of the office coded in ADM_UNIT_CD.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Travel Management Area Number
String
3
0
0
ST_PRRTY_NR
Priority number assigned by the state office in order to rank the top ten TMA’s per state.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
State Priority Number
Short Integer
5
2
0
ADMIN_ST
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.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Administrative State Code
String
2
AK
Alaska
DOM_ADMIN_ST
AZ
Arizona
DOM_ADMIN_ST
CA
California
DOM_ADMIN_ST
CO
Colorado
DOM_ADMIN_ST
ES
Eastern States
DOM_ADMIN_ST
ID
Idaho
DOM_ADMIN_ST
MT
Montana
DOM_ADMIN_ST
NM
New Mexico
DOM_ADMIN_ST
NV
Nevada
DOM_ADMIN_ST
OR
Oregon
DOM_ADMIN_ST
UT
Utah
DOM_ADMIN_ST
WY
Wyoming
DOM_ADMIN_ST
0
0
ADM_UNIT_CD
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.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Administrative Unit Code
String
8
AZ000000
ARIZONA
DOM_ADM_UNIT_CD
AZA00000
ARIZONA STRIP DISTRICT OFFICE
DOM_ADM_UNIT_CD
AZA01000
ARIZONA STRIP FIELD OFFICE
DOM_ADM_UNIT_CD
AZA02000
VERMILION CLIFFS NATIONAL MONUMENT
DOM_ADM_UNIT_CD
AZA03000
GRAND CANYON/PARASHANT NATIONAL MONUM
DOM_ADM_UNIT_CD
AZC00000
COLORADO RIVER DISTRICT OFFICE
DOM_ADM_UNIT_CD
AZC01000
KINGMAN FIELD OFFICE
DOM_ADM_UNIT_CD
AZC02000
YUMA FIELD OFFICE
DOM_ADM_UNIT_CD
AZC03000
LAKE HAVASU FIELD OFFICE
DOM_ADM_UNIT_CD
AZG00000
GILA DISTRICT OFFICE
DOM_ADM_UNIT_CD
AZG01000
SAFFORD FIELD OFFICE
DOM_ADM_UNIT_CD
AZG01100
GILA BOX RIPARIAN NCA
DOM_ADM_UNIT_CD
AZG02000
TUCSON FIELD OFFICE
DOM_ADM_UNIT_CD
AZG02100
LAS CIENEGAS NCA
DOM_ADM_UNIT_CD
AZG02200
SAN PEDRO RIPARIAN NCA
DOM_ADM_UNIT_CD
AZG03000
IRONWOOD FOREST NMO
DOM_ADM_UNIT_CD
AZP00000
PHOENIX DISTRICT OFFICE
DOM_ADM_UNIT_CD
AZP01000
HASSAYAMPA FIELD OFFICE
DOM_ADM_UNIT_CD
AZP02000
LOWER SONORAN FIELD OFFICE
DOM_ADM_UNIT_CD
AZP03000
AGUA FRIA NATIONAL MONUMENT
DOM_ADM_UNIT_CD
AZP04000
SONORAN DESERT NATIONAL MONUMENT
DOM_ADM_UNIT_CD
0
0
ADMU_NM
The official name by which the administrative unit is known.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Administrative Unit Name
String
40
0
0
TMP_START_DT
The proposed or actual start date of Travel and Transportation Management (TTM) planning for the TMP. If proposed date entered, update with actual start date (date the TMP_ID was established) when completed.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Travel Management Plan Start Date
Date
8
0
0
TMP_ID
The unique identifier for the Travel Management Plan. Used to link Travel Management Plans to Travel Management Areas.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Travel Management Plan Identifier
String
32
0
0
TMP_CMPLTN_DT
Estimated or actual completion date of Travel and Transportation Management (TTM) planning for the TMP.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
Travel Management Plan Completion Date
Date
8
0
0
GIS_ACRES
The total number of acres within a travel management areas and plans polygon
Travel Management Areas and Plans (TMAP) Implementation Guidelines
GIS Acres
Double
38
8
8
BLM_ACRES
The total number of acres within a travel management areas and plans polygon under BLM jurisdiction.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
BLM Acres
Double
38
8
8
GlobalID
Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data.
Travel Management Areas and Plans (TMAP) Implementation Guidelines
GlobalID
UUID
38
0
0
created_user
The name of the user who created the feature within the feature class of a geodatabase.
Arizona State Office, Bureau of Land Management
created_user
String
255
0
0
created_date
The date (UTC) in which the feature within the feature class of a geodatabase was created.
Arizona State Office, Bureau of Land Management
created_date
Date
8
0
0
last_edited_user
The name of the user who most recently updated the feature within the feature class of a geodatabase.
Arizona State Office, Bureau of Land Management
last_edited_user
String
255
0
0
last_edited_date
The date (UTC) in which the feature within the feature class of a geodatabase was most recently edited.
Arizona State Office, Bureau of Land Management
last_edited_date
Date
8
0
0
SHAPE
SHAPE
Geometry
4
0
0
Feature geometry.
Esri
Coordinates defining the features.
AZ_CREATE_DATE
Created Date
Date
8
0
0
AZ_CREATE_BY
Created By Name
String
30
0
0
AZ_MODIFY_DATE
Modified Date
Date
8
0
0
AZ_MODIFY_BY
Modified By Name
String
30
0
0
AZ_TMP_COMP
TMP Complete
String
10
0
0
AZ_PROP_REG_PLN_YR
Proposed Regional Planning Year
String
25
0
0
AZ_CRRNT_STATEPARKGRANTS_NUM
Current State Parks Grant Number
String
50
0
0
AZ_GTLF_QC_STTS
GTLF QC Status
String
50
0
0
AZ_GIS_NOTES
GIS Notes
String
255
0
0
AZ_TMP_NM
Travel Management Plan Name
String
255
0
0
AZ_RI_COMP
Route Inventory Complete
String
3
0
0
AZ_RI_COMP_YR
Route Inventory Completion Year
SmallInteger
2
0
0
AZ_RI_UPDATE
Route Inventory Update Needed
String
3
0
0
AZ_RE_STATUS
Route Evaluation Status
String
15
0
0
AZ_NEPA_TYPE
NEPA Type
String
5
0
0
AZ_NEPA_STATUS
NEPA Status
String
30
0
0
AZ_NEPA_STATUS_NOTES
NEPA Status Notes
String
255
0
0
AZ_STATEPARKGRANTS_STATUS
Grant Status
String
15
0
0
AZ_STATEPARKGRANTS_NOTES
Grant Status Notes
String
150
0
0
AZ_CRRNT_STATEPARKGRANTS_AMT
Grant Amount Remaining
Double
8
0
0
AZ_STATEPARKGRANTS_EXP
Grant Expiration Date
Date
8
0
0
AZ_IMP_PLAN_DOC_STATUS
Implementation Plan Document Status
String
15
0
0
AZ_TMP_IMP_STATUS
TMP Implementation Status
String
15
0
0
AZ_SIGN_COMP
Signage Complete
String
3
0
0
AZ_DIG_MAP_STATUS
Digital Map Creation Status
String
15
0
0
AZ_DIG_MAP_URL
Digital Map URL
String
1000
0
0
AZ_PRINT_MAP_STATUS
Paper Map Printed
String
3
0
0
Shape_Length
Shape_Length
Double
8
0
0
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
Shape_Area
Shape_Area
Double
8
0
0
Area of feature in internal units squared.
Esri
Positive real numbers that are automatically generated.
Please refer to the Travel Management Areas and Plans (TMAP) Implementation Guidelines for additional information.
Simple
TRUE
0
TRUE
FALSE
2
1
5.000000
FALSE
2
6