View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
ArcGIS Earth
ArcGIS Pro
Service Description: This dataset contains Land Tenure case types grouped by serial number combining individual Legal Land Descriptions into unified polygons. Case types included are acquisitions, classifications, exchanges, grants, occupancy and use, public administrative procedures, R&PP patents and reconveyances, sales, segregations, withdrawals, and other case groups effecting activities on public land. The data are derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores "0", "1", "2", "3" should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores "4", "4.1", "5", "6", "7" and "8" were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlying PLSS. Group 3: Mapped to Section. Score of "8.1", "8.2", "8.3", "9" and "10" are mapped to the Section for various reasons (refer to log information in data quality field). Group 4: Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5: No NLSDB Geometry, Only Attributes. Scores "11", "12", "20", "21" and "22" do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 :Mapped to County. Scores of "25" map to the County. Group 7: Improved Geometry. Scores of "100" are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.
Map Name: Land_Tenure_Case_Land_Status_PUBLIC
Legend
All Layers and Tables
Dynamic Legend
Dynamic All Layers
Layers:
Description: This dataset contains Land Tenure case types grouped by serial number combining individual Legal Land Descriptions into unified polygons. Case types included are acquisitions, classifications, exchanges, grants, occupancy and use, public administrative procedures, R&PP patents and reconveyances, sales, segregations, withdrawals, and other case groups effecting activities on public land. The data are derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores "0", "1", "2", "3" should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores "4", "4.1", "5", "6", "7" and "8" were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlying PLSS. Group 3: Mapped to Section. Score of "8.1", "8.2", "8.3", "9" and "10" are mapped to the Section for various reasons (refer to log information in data quality field). Group 4: Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5: No NLSDB Geometry, Only Attributes. Scores "11", "12", "20", "21" and "22" do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 :Mapped to County. Scores of "25" map to the County. Group 7: Improved Geometry. Scores of "100" are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.
Copyright Text: U.S. Department of Interior, Bureau of Land Management (BLM)
Spatial Reference:
4269
(4269)
Single Fused Map Cache: false
Initial Extent:
XMin: -161.69699999979844
YMin: -72.67299999990956
XMax: 161.69699999979844
YMax: 80.6949999998981
Spatial Reference: 4269
(4269)
Full Extent:
XMin: -179.16173646699997
YMin: 31.08547897400007
XMax: 179.77696883900012
YMax: 71.38988427500004
Spatial Reference: 4269
(4269)
Units: esriDecimalDegrees
Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP
Document Info:
Title: BLM MLRS Land Tenure - Case Land Status
Author:
Comments: This dataset contains Land Tenure case types grouped by serial number combining individual Legal Land Descriptions into unified polygons. Case types included are acquisitions, classifications, exchanges, grants, occupancy and use, public administrative procedures, R&PP patents and reconveyances, sales, segregations, withdrawals, and other case groups effecting activities on public land. The data are derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores "0", "1", "2", "3" should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores "4", "4.1", "5", "6", "7" and "8" were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlying PLSS. Group 3: Mapped to Section. Score of "8.1", "8.2", "8.3", "9" and "10" are mapped to the Section for various reasons (refer to log information in data quality field). Group 4: Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5: No NLSDB Geometry, Only Attributes. Scores "11", "12", "20", "21" and "22" do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 :Mapped to County. Scores of "25" map to the County. Group 7: Improved Geometry. Scores of "100" are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.
Subject: To geospatially represent Land Tenure Case Land Status within Mineral and Land Records System (MLRS).
Category:
Keywords: acquisition,Alabama,Alaska,Arizona,Arkansas,Authorization,boundaries,California,case land status,classifications,Colorado,Connecticut,Delaware,District of Columbia,Eastern States,exchanges,Florida,Georgia,geoscientificInformation,Geospatial,grants,Idaho,Illinois,Indiana,Iowa,Kansas,Kentucky,land grid,land status,Land Tenure,Louisiana,Maine,Management,Maryland,Massachusetts,Michigan,Minnesota,Mississippi,Missouri,Montana,Nebraska,Nevada,New Hampshire,New Jersey,New Mexico,New York,North Carolina,North Dakota,occupancy and use,Ohio,Oklahoma,Oregon,patents,Pennsylvania,planningCadastre,PLSS,public administrative procedures,Public Land Survey System,reconveyance,recreation and public purpose,Rhode Island,sales,section,segregations,South Carolina,South Dakota,status,Tennessee,Texas,township,Utah,Vermont,Virginia,Washington,West Virginia,Wisconsin,withdrawals,Wyoming
AntialiasingMode: None
TextAntialiasingMode: Force
Supports Dynamic Layers: true
MaxRecordCount: 2000
MaxImageHeight: 4096
MaxImageWidth: 4096
Supported Query Formats: JSON, geoJSON, PBF
Supports Query Data Elements: true
Min Scale: 1500000
Max Scale: 0
Supports Datum Transformation: true
Child Resources:
Info
Dynamic Layer
Supported Operations:
Export Map
Identify
QueryLegends
QueryDomains
Find
Return Updates