USGS - science for a changing world
Logo and link to The National Map

The National Map


ArcGIS REST Services Directory
JSON | SOAP | WMS

Tribal_Restricted_Boundaries (MapServer)

View In:   ArcGIS JavaScript   ArcGIS Online Map Viewer   ArcGIS Earth   ArcGIS Pro

Service Description:

Contains boundaries of all restricted Tribal areas in the U.S., as requested by Tribes and Alaska Native Corporations.

Field name definitions:

Tribe_Name: The Tribe’s official name as listed in the Federal Register or Alaska Native Corporation official name.

NGTOC_ID: Unique number for each Tribe or Alaska Native Corporation

State: State where the Tribe or Corporation is headquartered

OK_to_Pub: names of lidar projects which CAN be published since the Tribe has not requested restriction

Tribal boundary information:

National Geospatial Program (NGP)’s Tribal boundary sources are Census Bureau and BIA for CONUS and BLM data for Alaska. These 3 datasets are merged to ensure maximum coverage. NGP notifies and offers consultation based on federally recognized reservations and trust lands, Oklahoma Tribal statistical areas, and conveyed lands in Alaska. NGP does not notify or offer consultation for fee simple lands. In Alaska, NGP notifies and offers consultation to both Native Villages and Native Corporations.

For more on the datasets used for CONUS, see:

BIA American Indian and Alaskan Native Land Area Representations (LAR) - https://biamaps.doi.gov/bogs/datadownload.html

US Census Bureau Tribal boundaries - https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-geodatabase-file.html

For Alaska, see: https://www.blm.gov/services/geospatial/GISData/alaska

Update Process:

New boundaries are incorporated from the Census Bureau, BIA, and BLM on a yearly basis. Note that updates to the BIA LAR dataset are temporarily suspended (since 2019) until BIA completes their consultations with Tribes.

Tribal requests for changes to the restriction status (new restrictions or removing restrictions) are incorporated as they are received.

Information on Federal Agency Tribal Trust Responsibility for Restricted Tribal lands:

The USGS will not publish the lidar point cloud or digital elevation model (DEM) datasets better than 10m resolution for these areas, including high-resolution metadata such as intensity imagery. Furthermore, because all federal agencies have trust responsibilities related to federally recognized Tribes, the data for restricted Tribal lands may be shared within your agency to accomplish your mission but may not be distributed outside your agency.

If your federal agency has a contract with a third party to do data processing on your behalf, the third party can have a copy of the restricted data, as long there is a contract requiring the third party to keep restricted data confidential, not distribute it, and delete it once finished. If your federal agency wants to share the restricted Tribal data with a third party, your agency will need to request permission from the affected Tribes directly. Data located outside the restricted Tribal boundary can be made publicly available.



Map Name: Tribal_Restricted_Boundaries

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers: Description: Contains boundaries of all restricted Tribal areas in the U.S., as requested by Tribes and Alaska Native Corporations.Field name definitions: Tribe_Name: The Tribe’s official name as listed in the Federal Register or Alaska Native Corporation official name.NGTOC_ID: Unique number for each Tribe or Alaska Native Corporation State: State where the Tribe or Corporation is headquartered OK_to_Pub: names of lidar projects which CAN be published since the Tribe has not requested restrictionTribal boundary information:National Geospatial Program (NGP)’s Tribal boundary sources are Census Bureau and BIA for CONUS and BLM data for Alaska. These 3 datasets are merged to ensure maximum coverage. NGP notifies and offers consultation based on federally recognized reservations and trust lands, Oklahoma Tribal statistical areas, and conveyed lands in Alaska. NGP does not notify or offer consultation for fee simple lands. In Alaska, NGP notifies and offers consultation to both Native Villages and Native Corporations. For more on the datasets used for CONUS, see: BIA American Indian and Alaskan Native Land Area Representations (LAR) - https://biamaps.doi.gov/bogs/datadownload.htmlUS Census Bureau Tribal boundaries - https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-geodatabase-file.html For Alaska, see: https://www.blm.gov/services/geospatial/GISData/alaskaUpdate Process:New boundaries are incorporated from the Census Bureau, BIA, and BLM on a yearly basis. Note that updates to the BIA LAR dataset are temporarily suspended (since 2019) until BIA completes their consultations with Tribes. Tribal requests for changes to the restriction status (new restrictions or removing restrictions) are incorporated as they are received. Information on Federal Agency Tribal Trust Responsibility for Restricted Tribal lands:The USGS will not publish the lidar point cloud or digital elevation model (DEM) datasets better than 10m resolution for these areas, including high-resolution metadata such as intensity imagery. Furthermore, because all federal agencies have trust responsibilities related to federally recognized Tribes, the data for restricted Tribal lands may be shared within your agency to accomplish your mission but may not be distributed outside your agency. If your federal agency has a contract with a third party to do data processing on your behalf, the third party can have a copy of the restricted data, as long there is a contract requiring the third party to keep restricted data confidential, not distribute it, and delete it once finished. If your federal agency wants to share the restricted Tribal data with a third party, your agency will need to request permission from the affected Tribes directly. Data located outside the restricted Tribal boundary can be made publicly available.

Copyright Text: USGS 3DEP

Spatial Reference: 4269  (4269)


Single Fused Map Cache: false

Initial Extent: Full Extent: Units: esriDecimalDegrees

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info: Supports Dynamic Layers: true

MaxRecordCount: 2000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, geoJSON, PBF

Supports Query Data Elements: true

Min Scale: 0

Max Scale: 0

Supports Datum Transformation: true



Child Resources:   Info   Dynamic Layer

Supported Operations:   Export Map   Identify   QueryLegends   QueryDomains   Find   Return Updates