<?xml version="1.0" encoding="UTF-8"?><metadata xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gml="http://www.opengis.net/gml" xmlns:srv="http://www.isotc211.org/2005/srv" xmlns:xlink="http://www.w3.org/1999/xlink">
<idinfo>
<citation>
<citeinfo>
<title>BLM National Coal Rights Polygon</title>
<origin>U.S. Department of the Interior, Bureau of Land Management (BLM)</origin>
<pubdate>20260427</pubdate>
<pubinfo>
<publish>Bureau of Land Management</publish>
</pubinfo>
<onlink>https://gis.dev.blm.doi.net/arcgis/rest/services/lands/BLM_Natl_CoalRights/MapServer</onlink>
<geoform>vector digital data</geoform>
</citeinfo>
</citation>
<descript>
<abstract>As of April 1, 2022 the BLM Coal mapping data is no longer being updated nightly from the LR2000 system. The data will remain static from that date forward until efforts are completed to migrate this data to the Mineral and Land Records System (MLRS). Within the Bureau of Land Management (BLM), Coal Rights (COAL) is the part of a unit area which is considered reasonably proven to be productive in paying quantities or which is necessary for unit operations and to which production is allocated in the manner prescribed in the unit agreement. Within Coal Rights, there are eight individual case types: Coal Leases, Coal Exploration License, Coal Prospecting Permit, Coal Split Estate Surface Owner Qualification, Coal Lease and Land Exchanges, Coal License to Mine, Coal Category 5 Petitions, and Coal Logical Mining Unit. Each polygon represents a record that was matched from the Legacy Rehost 2000 case recordation database (LR2000) to the Public Lands Survey System (PLSS) geospatial polygon dataset. This map service displays a product that best represents locations for coal rights managed by the BLM.</abstract>
<purpose>The BLM's Legacy Rehost System, called LR2000, provides reports on BLM land and mineral use authorizations for oil, gas, and geothermal leasing, rights-of-way, coal and other mineral development, land and mineral title, mining claims, withdrawals, classifications, and more on federal lands or on federal mineral estate. The Coal Rights (COAL) geospatial data represents coal rights, which allow for the development of leases or a portion thereof that cannot be independently developed and operated in conformity with an established State well-spacing or well-development program. The term coal rights is the documentation/tracking of an agreement between one or more operators to conduct well developing operations between multiple leases. Each polygon in this geospatial dataset represents a record that was matched from the case recordation database (LR2000) to the Public Lands Survey System (PLSS) polygon dataset. This geospatial data is a final product that best represents the geographic version of the LR2000 case recordation data that includes records that represent locations for oil and gas coal rights managed by the BLM.</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20260427</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Daily</update>
</status>
<spdom>
<bounding>
<westbc>-122.235441</westbc>
<eastbc>-84.058005</eastbc>
<northbc>49.000001</northbc>
<southbc>29.084651</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>ISO 19115 Topic Category</themekt>
<themekey>planningCadastre</themekey>
<themekey>location</themekey>
</theme>
<theme>
<themekt>BLM-THEME</themekt>
<themekey>Energy</themekey>
<themekey>Management</themekey>
</theme>
<place>
<placekt>BLM-STATE</placekt>
<placekey>Alaska</placekey>
<placekey>Arizona</placekey>
<placekey>California</placekey>
<placekey>Colorado</placekey>
<placekey>Eastern States</placekey>
<placekey>Idaho</placekey>
<placekey>Montana</placekey>
<placekey>Nevada</placekey>
<placekey>New Mexico</placekey>
<placekey>Oregon</placekey>
<placekey>Utah</placekey>
<placekey>Wyoming</placekey>
</place>
<theme>
<themekt>None</themekt>
<themekey>BLM</themekey>
<themekey>Coal Rights</themekey>
<themekey>Bureau of Land Management</themekey>
<themekey>Planning</themekey>
<themekey>Geospatial</themekey>
<themekey>Coal</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Western States</placekey>
<placekey>Eastern States</placekey>
<placekey>United States</placekey>
</place>
</keywords>
<accconst>Generally releasable. However, the data must be reviewed prior to release to assure that no protected data is contained within the dataset.</accconst>
<useconst>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.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Bureau of Land Management (BLM)</cntorg>
<cntper>National Data Steward</cntper>
</cntorgp>
<cntpos>National Data Steward</cntpos>
<cntaddr>
<addrtype>physical</addrtype>
<address>20 M Street SE</address>
<city>Washington</city>
<state>DC</state>
<postal>20003-3503</postal>
<country>United States</country>
</cntaddr>
<cntvoice>(307)775-6261</cntvoice>
<cntemail>j35spenc@blm.gov</cntemail>
</cntinfo>
</ptcontac>
</idinfo>
<dataqual>
<attracc>
<attraccr>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States and derived data from LR2000, please contact the distributor for additional information on provenance, history, accuracy and quality of a particular state's data. The accuracy of attributes in this dataset reflects that of the source datasets. Attribute accuracy was tested by validating attribute coded values against accepted domain values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero.</attraccr>
</attracc>
<logic>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of a particular state's data. The logical consistency of this dataset reflects that of the source datasets. Each source dataset is run through a series of tests to verify that the data complies with the format specified in the Data Standard. ERRORS AND INCONSISTENCIES MAY STILL BE PRESENT IN THE DATA. These tests were conducted using ESRI ArcMap 10.7. The tests consisted of checking coded values for attributes against a domain of accepted values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero. For the geometry, the topology is not validated since features can overlap.</logic>
<complete>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States and derived from LR2000 data, please contact the distributor for additional information on provenance, history, accuracy and quality of a particular state's data. The positional accuracy across this dataset varies according to the source.</complete>
<posacc>
<horizpa>
<horizpar>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States and derived from LR2000, please contact the distributor for additional information on provenance, history, accuracy and quality of a particular state's data. The positional accuracy across this dataset varies according to the source.</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>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 resource contains also pertains to geospatial data.</origin>
<pubdate>20141205</pubdate>
<title>H-1283-2 Data Administration and Management Handbook</title>
<edition>Release 1-1762</edition>
<onlink>http://web.blm.gov/internal/wo-500/directives/dir-hdbk/h1283-2.pdf</onlink>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
<srccontr>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 resource contains also pertains to geospatial data.</srccontr>
</srcinfo>
<procstep>
<procdesc>This COAL dataset is derived from the LR2000 reporting database as an interim solution. Ideally this data would be sourced from the LR2000 Case Recordation transactional database in the future. Any transactional data quality information would reside with that system. Data quality for this COAL dataset is documented in the COAL QC Standardized Dataset Report using the COAL_QC and COAL_QC_GeoState layers. These layers have information that indicates the quality of the LLD matches between the LR2000 database and the PLSS geographic dataset.</procdesc>
<procdate>Unknown</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>U.S. Department of the Interior, Bureau of Land Management (BLM)</cntorg>
<cntper>Spatial Data Coordinator</cntper>
</cntorgp>
<cntpos>Spatial Data Coordinator</cntpos>
<cntaddr>
<addrtype>physical</addrtype>
<address>Bldg. 85, Denver Federal Center</address>
<city>Denver</city>
<state>CO</state>
<postal>80225</postal>
<country>United States</country>
</cntaddr>
<cntemail>scrowe@blm.gov</cntemail>
</cntinfo>
</proccont>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>GT-polygon composed of chains</sdtstype>
<ptvctcnt>13684</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>8.9831528411952133e-09</latres>
<longres>8.9831528411952133e-09</longres>
<geogunit>Decimal Degrees</geogunit>
</geograph>
<geodetic>
<horizdn>D North American 1983</horizdn>
<ellips>GRS 1980</ellips>
<semiaxis>6378137.0</semiaxis>
<denflat>298.257222101</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<overview>
<eaover>See COAL Standarized Dataset Report</eaover>
</overview>
<detailed>
<enttyp>
<enttypl>plad_ln</enttypl>
<enttypd>Lines that represent where and what type of access (public or administrative) to BLM managed lands exist via existing and perfected easements and patent reservations.</enttypd>
</enttyp>
<attr>
<attrlabl>SN_FULL</attrlabl>
<attalias>BLM Case File Number</attalias>
<attrdef>BLM Casefile serial number of the acquisition in LR2000. Business Rule: Polygon and linear features are related by the casefile serial number</attrdef>
</attr>
<attr>
<attrlabl>MLRS_SRL_NO</attrlabl>
<attalias>MLRS Serial Number</attalias>
<attrdef>BLM Case File Number assigned when MLRS system is implemented. A unique number that will be assigned to all existing and new cases when MLRS is brought online for the lands and realty program.</attrdef>
</attr>
<attr>
<attrlabl>CASE_ID</attrlabl>
<attalias>Case ID Number</attalias>
<attrdef>A unique number up to nine digits in length that is automatically generated by LR2000 when a new case is serialized within the system.</attrdef>
</attr>
<attr>
<attrlabl>PRPRTY_INTRST_TYPE</attrlabl>
<attalias>Interest Acquired or Reserved</attalias>
<attrdef>The type of property right acquired.</attrdef>
</attr>
<attr>
<attrlabl>ESMNT_RIGHT_TYPE</attrlabl>
<attalias>Easement Rights Acquired or Reserved</attalias>
<attrdef>The nature of the easement rights acquired.
Design Consideration: A Realty Specialist, Land Law Examiner or Legal Instrument Examiner is required to validate this data entry.
</attrdef>
</attr>
<attr>
<attrlabl>ACS_RGHTS_TYPE</attrlabl>
<attalias>Access Rights Acquired or Reserved</attalias>
<attrdef>The specific access provided by the property right acquired or reserved.
Design Consideration: A Realty Specialist, Land Law Examiner or Legal Instrument Examiner is required to validate this data entry.
</attrdef>
</attr>
<attr>
<attrlabl>LEGAL_USE_TYPE</attrlabl>
<attalias>Legal Use Acquired or Reserved</attalias>
<attrdef>Legal use as defined in the conveying legal document (easement deed or patent). Design Consideration: Selection of one primary legal use is required using the established domain values of: Road, Trail, Recreation Site, Defined Use (see deed or patent for specific use allowed) </attrdef>
</attr>
<attr>
<attrlabl>SPLMNTL_LEGAL_USE_TYPE</attrlabl>
<attalias>Supplemental Legal Use Acquired or Reserved</attalias>
<attrdef>Supplemental Uses are defined in the conveying legal document (easement deed or patent). Business Rule: When applicable, selection of one or more supplemental legal use is required using the established domain values of: Non-motorized, Non-motorized; includes uses with electric motors, Non-Mechanized, Over-the-Snow, Camping, Boat Ramp, Parking Area, Toilet, etc. SPLMNTL_LEGAL_USE_TYPE to be left NULL if no supplemental legal use has been described in the document. In the event a defined supplemental legal use is not included in the existing supplemental legal use type list, a request can be submitted to add that use to the established list of legal uses.
</attrdef>
</attr>
<attr>
<attrlabl>SSNL_USE_TYPE</attrlabl>
<attalias>Seasonal Use Restriction</attalias>
<attrdef> Seasonal Use Type indicates the type of use restriction an easement or reservation has during the year. This restriction may be constrained by certain conditions (snow conditions, mud, wildlife presence, etc.) Design Consideration: When applicable, selection of one seasonal restriction required using the established domain values of: Event, Date Range, Event Range, Use Condition, None.
If SSNL_USE_TYPE = None, SSNL_USE_START, SSNL_USE_END and SSNL_USE_DTL should be null.
If SSNL_USE_TYPE = Date Range or Event Range both SSNL_USE_START and SSNL_USE_END are required
If SSNL_USE_TYPE = Event or Use Condition, then SSNL_USE_END can be Null (note: discuss whether to require that SSNL_USE_END should be required to be Null)
If SSNL_USE_TYPE = Event or Use Condition, then SSNL_USE_END can be Null (note: discuss whether to require that SSNL_USE_END should be required to be Null)</attrdef>
</attr>
<attr>
<attrlabl>SSNL_USE_START</attrlabl>
<attalias>Seasonal Restriction Start</attalias>
<attrdef>The data a seasonal use or event restriction begins. (Example, Elk calving season begins restricting use of the location)
Design Consideration: This field is required if an easement or reservation contains a seasonal use restrictions with a date range or event range.
See Design Consideration for SSNL_USE_TYPE.
</attrdef>
</attr>
<attr>
<attrlabl>SSNL_USE_END</attrlabl>
<attalias>Seasonal Restriction End</attalias>
<attrdef>The data a seasonal use restriction ends. (Example, Elk calving season ends removing the use restriction on the location). Design Consideration: This field is required if an easement or reservation contains a seasonal use restrictions with a data range or event range.
See Design Consideration for SSNL_USE_TYPE
</attrdef>
</attr>
<attr>
<attrlabl>SSNL_USE_DTL</attrlabl>
<attalias>Seasonal Restriction Description</attalias>
<attrdef>Seasonal Use Detail is the description of conditions found in the easement deed or patent describing when use is restricted and the conditions governing the restriction. (Example, Over the snow travel is restricted when snow depth reaches an average of less than XX inches.) Design Consideration: This field is required if an easement or reservation contains a seasonal use restriction. The field must be used to provide additional detailed information about the seasonal use restriction not covered by the SSNL_USE_TYPE field.
See Design Consideration for SSNL_USE_TYPE</attrdef>
</attr>
<attr>
<attrlabl>TRVL_PLAN_YN</attrlabl>
<attalias>Approved Travel Plan</attalias>
<attrdef>Indicates if a Travel and Transportation Management Plan and/or travel management decision has been completed for the easement or patent location. This attribute is associated with global domain, DOM_YES_NO. The codes and descriptions are as follows: Yes - route is closed at some point during the year, every year. No - route is available for use all year, every year. Default: No
Business Rule: Selecting “Yes” indicates that a travel management plan or travel management decision has been made on a route located within the easement or patent location. Travel planning decision are made in various planning documents (ie. EIS, EA, sundry notice, allotment authorizations, realty actions). </attrdef>
</attr>
<attr>
<attrlabl>TRVL_PLAN_URL</attrlabl>
<attalias>Travel Plan Website</attalias>
<attrdef>The web address or URL of the planning document containing the travel management decisions for the area where the easement or patent reservation is located. Design Consideration: Input the URL for the Travel Management Plan from ePlanning or another resource if available.
</attrdef>
</attr>
<attr>
<attrlabl>FAMS_ID</attrlabl>
<attalias>FAMS ID</attalias>
<attrdef>A unique number 5-10 characters in length associated with a BLM designated asset within the Facility Asset Management System (FAMS).</attrdef>
</attr>
<attr>
<attrlabl>GEO_NAME</attrlabl>
<attalias>Geographic Name</attalias>
<attrdef>Geographic name of the road or trail that the property right is associated</attrdef>
</attr>
<attr>
<attrlabl>ROUTE_NO</attrlabl>
<attalias>Road or Trail Number</attalias>
<attrdef>The numeric code by which the feature is known according to the person or organization contained in route ownership code attribute. Note: Route Number should not include the route or trail name.
</attrdef>
</attr>
<attr>
<attrlabl>WIDTH_FT</attrlabl>
<attalias>Width in Feet</attalias>
<attrdef>Total width in feet of the property right acquired. It defines the area where the BLM can legally operate. Record total width of the property right, not the width on either side of the linear feature.
Business Rule: this value must be NULL if PRPRTY_INTRST_TYPE not Access Easement, Project (Site) Easement, or Conservation Easement</attrdef>
</attr>
<attr>
<attrlabl>LNGTH</attrlabl>
<attalias>Length in Feet or Miles</attalias>
<attrdef>Total length of the line of the easement right recorded. Preference is for length to be entered in feet or miles.</attrdef>
</attr>
<attr>
<attrlabl>LNGTH_UOM</attrlabl>
<attalias>Length Unit of Measurement</attalias>
<attrdef>Length Unit of Measurement in US Customary Units of Length (inch, foot, yard, mile). Expectation for this dataset is feet and miles will be used.</attrdef>
</attr>
<attr>
<attrlabl>RCRD_ACRES</attrlabl>
<attalias>Recorded Acres</attalias>
<attrdef>The legal acreage of property right acquired as described in the recorded legal instrument</attrdef>
</attr>
<attr>
<attrlabl>PHOTO_URL</attrlabl>
<attalias>Photo URL</attalias>
<attrdef>The URL that depicts the link to a photo of the area.</attrdef>
</attr>
<attr>
<attrlabl>PHOTO_TEXT</attrlabl>
<attalias>Photo Text</attalias>
<attrdef>A description of the photo in the PHOTO_URL.</attrdef>
</attr>
<attr>
<attrlabl>WEB_URL_BLM</attrlabl>
<attalias>BLM URL</attalias>
<attrdef>An internal URL that is used to link a website that contains content specific to the feature.</attrdef>
</attr>
<attr>
<attrlabl>WEB_URL_EXTRNL</attrlabl>
<attalias>External URL</attalias>
<attrdef>An external, non-BLM URL that is used to link a website that contains content specific to the feature.</attrdef>
</attr>
<attr>
<attrlabl>DATA_RLSBLTY_CD</attrlabl>
<attalias>Data Releasability to Public</attalias>
<attrdef>Indicates whether or not the record is approved to publish for public use. Design Consideration: The field office is responsible for identifying data that can be displayed to the public.
Records Access Category 1A - Public Data
These are externally provided data made available to the public and are considered public domain. These data contain no sensitive information which would be prevented from disclosure by Freedom of Information Act (FOIA), the Privacy Act or other laws. DATA_RLSBLTY_CD attribute will be populated YES for this data.
Records Access Category 2 - Non-Public Data, Internal Use
These are BLM data that could contain information that should not be disclosed to the public because of the Privacy Act or FOIA. It may be requested by the public through FOIA.
The data to be published for public use under Category 1A will be a subset of the complete data that will be available for internal BLM use. Easements and reservations that provide administrative access only will not be published/provided to the public. A field in the dataset/geodatabase attributes will be added as publish Yes/No. Upon field office review and QC of the data they will confirm the Yes for public access features. The data that is defined by publish “No” would fall under Category 2 and the publish “Yes” under Category 1A.
DATA_RLSBLTY_CD attribute will be populated YES or NO for this data.
</attrdef>
</attr>
<attr>
<attrlabl>BLM_FLD_OFC</attrlabl>
<attalias>BLM Field Office</attalias>
<attrdef>Field office with jurisdiction over the property right. No district offices should be entered here.</attrdef>
</attr>
<attr>
<attrlabl>CNTY_FRST</attrlabl>
<attalias>First County</attalias>
<attrdef>First county where the property right is located and recorded. No priority or order of precedent is inferred by being the first or second county listed.</attrdef>
</attr>
<attr>
<attrlabl>CNTY_SCND</attrlabl>
<attalias>Second County</attalias>
<attrdef>Second county where the property right is located and recorded if applicable. No priority or order of precedent is inferred by being the first or second county listed.</attrdef>
</attr>
<attr>
<attrlabl>CSTPE</attrlabl>
<attalias>Casetype Code</attalias>
<attrdef>Casetype Code is derived from numbering in title 43 of the Code of Federal Regulations. Casetypes relate to the legal authority used to obtain the access right.</attrdef>
</attr>
<attr>
<attrlabl>MTHD_ACQSTN_RSRVTN_TYPE</attrlabl>
<attalias>Method of Acquisition or Reservation</attalias>
<attrdef>The means used to acquire the property right through an easement acquisition or a patent reservation. Business Rule: Selection of one Acquisition or Reservation Type is required using the established domain values of: Monetary Consideration, Reservation, Donation, Bargain Sale, Reciprocal Row, Exchange, Condemnation, Special Authority.
</attrdef>
</attr>
<attr>
<attrlabl>ACQSTN_FUND_TYPE</attrlabl>
<attalias>Acquisition Fund</attalias>
<attrdef>The fund type used to acquire the property rights</attrdef>
</attr>
<attr>
<attrlabl>APRSD_VALUE</attrlabl>
<attalias>Appraised Value</attalias>
<attrdef>Fair Market Value as determined by AVSO in the approved Appraisal or Appraisal Waiver determination.</attrdef>
</attr>
<attr>
<attrlabl>PYMNT_MADE</attrlabl>
<attalias>Payment Made</attalias>
<attrdef>The amount of the payment made to acquire the property rights
Design Consideration: When dollars and cents are present, round up: $289000.57 would be rounded to $289001.
</attrdef>
</attr>
<attr>
<attrlabl>AUTH_DT</attrlabl>
<attalias>Date of Authorization</attalias>
<attrdef>Date property right was established</attrdef>
</attr>
<attr>
<attrlabl>TITLE_REC</attrlabl>
<attalias>Title Recordation</attalias>
<attrdef>Volume, book and page or reception number at the county where the document is recorded. This comes from the remarks field.</attrdef>
</attr>
<attr>
<attrlabl>GRFRNCE_SRCE_TYPE</attrlabl>
<attalias>Georeferenced Source</attalias>
<attrdef>Source data or documents used to geographically represent a legal description of land or interest in land from a deed or patent.</attrdef>
</attr>
<attr>
<attrlabl>MPNG_MTHD</attrlabl>
<attalias>Mapping Method</attalias>
<attrdef>The method of digitizing the polygon area that indicates the quality of the boundary placement on the map. </attrdef>
</attr>
<attr>
<attrlabl>NOTES</attrlabl>
<attalias>Notes</attalias>
<attrdef>General notes for more information. Captures input when “Multiple” value is selected in the domains.</attrdef>
</attr>
<attr>
<attrlabl>QLTY_NOTES</attrlabl>
<attalias>Quality Notes</attalias>
<attrdef>Quality Notes about migration, digitization, general, and to capture mapping notes from the first iteration.</attrdef>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Bureau of Land Management (BLM) National Operations Center</cntorg>
<cntper>NOC Data Management Lead</cntper>
</cntorgp>
<cntpos>NOC Data Management Lead</cntpos>
<cntaddr>
<addrtype>physical</addrtype>
<address>Bldg 50, Denver Federal Center</address>
<city>Denver</city>
<state>CO</state>
<postal>80225</postal>
<country>United States</country>
</cntaddr>
<cntvoice>(303) 236-0721</cntvoice>
<cntemail>jshouldis@blm.gov</cntemail>
</cntinfo>
</distrib>
<resdesc>Map Files</resdesc>
<distliab>BLM INTERNAL USE. NOT FOR DISTRIBUTION. The BLM will not be held liable for the unintentional disclosure of these data. 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.</distliab>
</distinfo>
<metainfo>
<metd>20210312</metd>
<metrd>20220312</metrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Bureau of Land Management (BLM) National Operations Center</cntorg>
<cntper>NOC Data Management Lead</cntper>
</cntorgp>
<cntpos>NOC Data Management Lead</cntpos>
<cntaddr>
<addrtype>physical</addrtype>
<address>Bldg 50, Denver Federal Center</address>
<city>Denver</city>
<state>CO</state>
<postal>80225</postal>
<country>United States</country>
</cntaddr>
<cntvoice>(303) 236-0721</cntvoice>
<cntemail>jshouldis@blm.gov</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metsi>
<metsc>Unclassified</metsc>
</metsi>
</metainfo>
<Esri>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<DataProperties>
<itemProps>
<imsContentType export="False">
</imsContentType>
</itemProps>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<dataIdInfo>
<placeKeys>
<thesaName>
<resTitle>BLM-STATE</resTitle>
</thesaName>
<keyword>Arizona</keyword>
<keyword>California</keyword>
<keyword>Colorado</keyword>
<keyword>Idaho</keyword>
<keyword>Montana</keyword>
<keyword>Nevada</keyword>
<keyword>New Mexico</keyword>
<keyword>North Dakota</keyword>
<keyword>Oregon</keyword>
<keyword>South Dakota</keyword>
<keyword>Utah</keyword>
<keyword>Washington</keyword>
<keyword>Wyoming</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>BLM-THEME</resTitle>
</thesaName>
<keyword>Authorization</keyword>
<keyword>Management</keyword>
<keyword>Recreation</keyword>
</themeKeys>
<idPurp>Congress passed the Modernizing Access to our Public Land Act (MAPLand Act) in 2022. Section 4 of the MAPLand Act requires the BLM to, not later than four years after the date of enactment of the Act, digitize and publish, on the applicable agency website, GIS mapping data that specifies, with respect to the BLM, all Federal interests in private land, including easements, reservations, and rights-of-way (1) in which the Federal Government does not have a fee title interest; and (2) that provide legal public recreational access to the Federal land. This aggregated dataset contains public and BLM public access easement and reservation data.
The Public Lands Access Data Project modernizes BLM public access easement and reservation data from tabular form (Realty case files and GLO Records) to geospatial form. This effort will provide opportunity for participating BLM state and field offices the ability to modernize (digitize) existing tabular lands and realty data (i.e., easements, reservations, land exchanges and other lands and realty records and case file types) to populate a national public lands access dataset.
The data will directly support improved public access to public lands by providing the information in an accessible format for public use and integration into commercial mobile applications that informs the public how to reach public lands via legally perfected easements or patent reservations that cross private, state or other agency owned lands.</idPurp>
<idCredit>Bureau of Land Management, National Operations Center (NOC), Bureau of Land Management (BLM), Alaska State Office, Arizona State Office, California State Office, Colorado State Office, Idaho State Office, New Mexico State Office, Nevada State Office, Oregon Washington State Office, Montana State Office, Utah State Office, Wyoming State Office</idCredit>
<idCitation>
<citRespParty>
<rpIndName>Bureau of Land Management</rpIndName>
<role>
<RoleCd value="010">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpIndName>U.S. Department of the Interior, Bureau of Land Management (BLM)</rpIndName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<resTitle>BLM Public Land Access Data Line</resTitle>
<date>
<pubDate>2026-04-27</pubDate>
</date>
<presForm>
<PresFormCd value="005">
</PresFormCd>
</presForm>
</idCitation>
<searchKeys>
<keyword>Arizona</keyword>
<keyword>Authorization</keyword>
<keyword>California</keyword>
<keyword>Colorado</keyword>
<keyword>Idaho</keyword>
<keyword>location</keyword>
<keyword>Management</keyword>
<keyword>Montana</keyword>
<keyword>Nevada</keyword>
<keyword>New Mexico</keyword>
<keyword>North Dakota</keyword>
<keyword>Oregon</keyword>
<keyword>Recreation</keyword>
<keyword>South Dakota</keyword>
<keyword>Utah</keyword>
<keyword>Washington</keyword>
<keyword>Wyoming</keyword>
</searchKeys>
<idAbs>This line feature represents Federal interests in private land, including easements and reservations (1) in which the Federal Government does not have a fee title interest; and (2) that provide both legal public recreational access and legal administrative access to the Federal land in conformance with the MAPLand Act and the PLAD project. This dataset also also provides BLM managers with information to identify access limitations, vulnerabilities, and areas where access to public lands may be improved. The dataset can also support additional management of resources such as timber harvest, travel and transportation planning, wildfire fuels reduction projects and many other land management related decisions.</idAbs>
<idStatus>
<ProgCd value="004">
</ProgCd>
</idStatus>
<dataChar>
<CharSetCd value="004">
</CharSetCd>
</dataChar>
<idPoC>
<rpIndName>Jeff Cartwright</rpIndName>
<rpOrgName>Bureau of Land Management, National Conservation Lands and Community Partnerships, HQ400</rpOrgName>
<rpPosName>Public Land Access Program Manager</rpPosName>
<role>
<RoleCd value="007">
</RoleCd>
</role>
<rpCntInfo>
<cntAddress addressType="physical">
<delPoint>760 Horizon Drive, Ste 102</delPoint>
<city>Grand Junction</city>
<adminArea>CO</adminArea>
<postCode>81506</postCode>
<eMailAdd>jcartwright@blm.gov</eMailAdd>
<country>US</country>
</cntAddress>
</rpCntInfo>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="008">
</MaintFreqCd>
</maintFreq>
</resMaint>
<resConst>
<Consts>
<useLimit>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.</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>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.</useLimit>
<othConsts>Generally releasable. However, the data must be reviewed prior to release to assure that no protected data is contained within the dataset.</othConsts>
</LegConsts>
</resConst>
<dataExt>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>20201201</tmBegin>
<tmEnd>2026-04-27</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL>-124.368205</westBL>
<eastBL>-77.182370</eastBL>
<northBL>48.987865</northBL>
<southBL>31.332563</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="013">
</TopicCatCd>
</tpCat>
</dataIdInfo>
<mdHrLv>
<ScopeCd value="005">
</ScopeCd>
</mdHrLv>
<mdDateSt Sync="TRUE">2026-04-27</mdDateSt>
<mdContact>
<rpIndName>Jeff Cartwright</rpIndName>
<rpOrgName>Bureau of Land Management, National Conservation Lands and Community Partnerships, HQ400</rpOrgName>
<rpPosName>Public Land Access Program Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>760 Horizon Drive, Ste 102</delPoint>
<city>Grand Junction</city>
<adminArea>CO</adminArea>
<postCode>81506</postCode>
<eMailAdd>jcartwright@blm.gov</eMailAdd>
<country>US</country>
</cntAddress>
</rpCntInfo>
</mdContact>
<mdMaint>
<maintNote>Last metadata review date: 20230322</maintNote>
<maintFreq>
<MaintFreqCd value="009">
</MaintFreqCd>
</maintFreq>
</mdMaint>
<dqInfo>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please call the distributor for additional information on provenance, history, accuracy and quality of the data. The positional accuracy across this dataset varies according to the source.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The logical consistency of this dataset reflects that of the source datasets. Each source dataset is run through a series of tests to verify that the data complies with the format specified in the Data Standard. ERRORS AND INCONSISTENCIES MAY STILL BE PRESENT IN THE DATA. </measDesc>
</report>
<report type="DQCompOm">
<measDesc>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The completeness of this dataset reflects that of the source datasets.</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States. Please call the distributor for additional information on provenance, history, accuracy and quality of the data. The accuracy of attributes in this dataset reflects that of the source datasets. Attribute accuracy was tested by validating attribute coded values against accepted domain values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero.</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>Using the Schema Workbook, GIS staff at BLM field and state offices cross-walk and clean up their data to comply with the standardized national dataset. Then, the BLM field and/or state offices submit the data to the National Operations Center (NOC), where it is compiled to produce seamless national datasets. This process of data replication to the National Operations Center is intended to occur on a monthly basis.</stepDesc>
<stepDateTm>2026-04-27</stepDateTm>
<stepProc>
<rpIndName>Stacey Crowe</rpIndName>
<rpOrgName>BLM National Operations Center</rpOrgName>
<rpPosName>Spatial Data Coordinator</rpPosName>
<rpCntInfo>
<cntAddress addressType="postal">
<delPoint>111 South Kipling Street, Bldg. 85, Denver Federal Center</delPoint>
<city>Lakewood</city>
<adminArea>CO</adminArea>
<postCode>80215</postCode>
<eMailAdd>scrowe@blm.gov</eMailAdd>
<country>US</country>
</cntAddress>
</rpCntInfo>
</stepProc>
</prcStep>
</dataLineage>
</dqInfo>
<distInfo>
<distributor>
<distorCont>
<rpOrgName>BLM National Operations Center, OC530</rpOrgName>
<rpPosName>NOC Data Management Lead</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>111 S Kipling Street</delPoint>
<city>Lakewood</city>
<adminArea>CO</adminArea>
<postCode>80215</postCode>
<eMailAdd>kkirkpatrick@blm.gov</eMailAdd>
<country>US</country>
</cntAddress>
</rpCntInfo>
</distorCont>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://www.blm.gov/programs/recreation/recreation-programs/travel-and-transportation/public-lands-access-data</linkage>
</onLineSrc>
</distTranOps>
</distInfo>
<mdChar>
<CharSetCd value="004">
</CharSetCd>
</mdChar>
</metadata>
