PLSS / BLM Cadastral (US): Intelligence Source Guide

The Bureau of Land Management publishes the Public Land Survey System grid, federal surface and mineral ownership layers, and the historical patent records that first transferred land out of federal hands – as open ArcGIS REST services. It is the closest thing the United States has to a national land-status layer.

At a glance

Source	PLSS / BLM Cadastral (US)
Category	Corporate, Ownership & Legal Records › Land & Property Registries
Homepage	https://www.blm.gov/services/land-records
Machine interface	https://gis.blm.gov/arcgis/rest/services
Format	REST
Access	Open — no account required
Disciplines	Government Intelligence
Mission domains	Energy Security, Border Security & Migration

US Bureau of Land Management Public Land Survey System and land-record ArcGIS REST services. — as catalogued in the platform’s own source registry.

The Bureau of Land Management is the federal agency responsible for cadastral survey on public lands and for the land records that flow from it. Three distinct bodies of data sit behind this entry. The first is the Public Land Survey System: the rectangular survey grid of townships, ranges, sections and aliquot parts that covers roughly thirty states, established from the Land Ordinance of 1785 onward and still the legal basis for describing land in most of the western and midwestern United States. The BLM publishes it as CadNSDI, a national geospatial representation of the survey framework with township, section, subdivision and special survey layers. The second is land status: Surface Management Agency layers showing which federal agency administers a given tract – BLM, Forest Service, National Park Service, Fish and Wildlife Service, Department of Defense, Bureau of Reclamation and others – together with mineral estate and split-estate representations, wilderness and national conservation lands designations, and grazing allotments. The third is the historical record: the General Land Office records system, which holds scanned federal land patents, survey plats and field notes going back to the late eighteenth century, indexed by patentee name and legal description. Delivery is principally through ArcGIS REST services at gis.blm.gov, with additional download and application routes, and the current land and mineral records system that replaced the older LR2000 reporting system handles case-level records for authorisations, claims and leases.

This source does the job that The National Map explicitly does not: it tells you about land status and, in the historical record, about a chain of title's first link. It does not tell you who owns a private parcel today – that remains a county function – but it answers four questions no other free national source answers. Is this tract federal, and if so which agency administers the surface? Is the mineral estate severed from the surface, and who holds it? What is the legal description of this location in township, range, section and aliquot terms, which is how deeds, leases, mining claims and oil and gas permits in the western United States actually describe land? And when did this land first leave federal ownership, to whom, and under which statute? That last question is the one investigators underuse. A patent record names a person, a date, a legal description and an authorising act, which makes it a genealogical, historical and title-research instrument at once. For energy work the mineral estate and split-estate layers are load-bearing: a company can hold drilling rights under land it does not own on the surface, and that fact is invisible in every dataset except this one. For border and public-lands work, the surface management layer determines which federal law enforcement agency has authority over an incident. And for anything involving western water, grazing or mining, the PLSS description is the join key that connects a state permit, a federal lease and a county deed to the same piece of ground.

Who publishes it, and why that matters

The BLM is a land management agency inside the Department of the Interior with about a quarter of a billion acres under its administration and a statutory cadastral survey mission that predates the agency itself – the General Land Office lineage runs back to 1812. That gives the data both durability and a particular character: it exists to support land administration, not analysis. The consequence is that the geospatial products are excellent where the agency's own business requires them – federal surface status, the survey grid, mineral estate on lands it administers – and thin where the business does not, which is anything about private land. Funding is appropriated and the mission is statutory, so the source is not going to disappear, but delivery has been reorganised repeatedly: the legacy LR2000 reporting system was retired in favour of a modern land and mineral records platform, geospatial delivery has moved between hosted platforms, and service URLs have changed accordingly. Treat any specific service path as a maintenance liability and the agency's land records landing page as the authoritative index of what currently exists. There is also a distributed-authorship problem: much of CadNSDI is compiled from state offices and partner submissions on different schedules, so the survey grid's precision and currency vary by state in ways that only the layer metadata reveals.

Provenance is the first question to ask of any dataset and the one most often skipped. Who collects it, what their incentive is, whether they publish a methodology, and whether they correct the record when they get something wrong all bear directly on how much weight a finding drawn from it can carry.

What a record actually contains

The fields you will be working with, what each one means, and whether it is something you can pivot on. Read the meanings carefully — more analysis is wrecked by misreading a field than by failing to find one, and a field that looks like an observation is often an inference.

Field	Type	What it means	Pivot value
PLSSID / township identifier	string	The composite key identifying a township within a principal meridian – state, principal meridian code, township number and direction, range number and direction. It is the primary index into the entire survey system and the string a deed description resolves to.	All sections within the township, adjoining townships, and any lease, claim or permit described against the same township and range.
principal meridian	enum	Which of the survey system's independent origin meridians governs the township and range numbering. There are dozens, they are not sequential geographically, and township 3 north range 2 west means nothing until you know the meridian.	The survey history of the region and the plats filed under that meridian.
section number	int	The numbered square mile within a township, ordinarily 1 to 36 numbered boustrophedonically from the north-east corner. Irregular townships contain lettered lots and fractional sections instead, which is where naive parsers break.	Aliquot subdivisions within the section, and any legal description referencing it.
aliquot part / first division	string	The subdivision of a section into halves, quarters and quarter-quarters expressed as strings such as NE quarter of the SW quarter. This is the resolution at which most deeds, leases and mining claims are described – about forty acres.	The specific tract in a lease, patent or claim record described with the same aliquot string.
government lot number	int	Numbered irregular parcels created where a section could not be regularly subdivided – typically along water bodies, state lines or earlier surveys. Their acreage is stated on the plat and is not derivable from the grid.	The original survey plat, which is the only authority for the lot's dimensions and acreage.
surface management agency	enum	Which federal agency administers the surface of a tract, or an indication that it is not federal. This determines jurisdiction, applicable regulation and which agency's records will exist for the tract.	The administering agency's own case files, land use plans and enforcement records.
mineral estate indicator	enum	Whether the federal government retains the mineral estate, and whether surface and minerals are severed. Split estate – private surface over federal minerals, or the reverse – is common in the west and drives most surface-use conflict.	Federal oil, gas and mineral lease records for the same legal description.
patent / document number	string	In the General Land Office records, the identifier of the instrument that transferred land from federal ownership, tied to a scanned image of the original document.	The named patentee, the authorising act, and the county recorder's subsequent chain of title from that first conveyance.
patentee name	string	The person or entity to whom the original patent was issued, as spelled on the instrument. Spelling is nineteenth-century and inconsistent, and one physical person may appear several ways.	Census, probate and county deed records for the same individual; adjoining patents issued the same day often indicate family or company groupings.
issue date	timestamp	Date the patent was issued, which is later – sometimes by years – than entry, settlement or the events that established the claim. The gap is itself informative about how the land was acquired.	Contemporaneous survey plats and field notes for the same township.
authority / act	enum	The statute under which land was conveyed: homestead, mineral entry, cash sale, railroad grant, military bounty warrant, desert land and many others. It is a compact statement of how and why the land left federal hands.	The class of similar disposals in the region and the policy history that produced them.
case / serial number	string	Identifier for an active land record case – a lease, right-of-way, mining claim, permit or authorisation – in the agency's land and mineral records system.	The holder of record, the case status, and the geographic description the case attaches to.
survey plat reference	string	Pointer to the official survey plat for a township, which is the legal authority for the survey's monuments, lot dimensions and acreage. Where the digital grid and the plat disagree, the plat governs.	Field notes for the same survey, which record monument descriptions and are the evidence behind boundary disputes.
geometry	object	Polygon or point geometry for the survey unit or status polygon, delivered in the service's projection. It is a representation of a legal boundary, not a survey of it, and carries a data-collection tolerance rather than survey accuracy.	none

Coverage — and what is not in it

Coverage is defined by history rather than by geography. The Public Land Survey System applies to the public domain states – broadly the thirty states created out of federal territory – and does not exist in the original thirteen colonies, their derivatives, Texas, Hawaii or the parts of the country surveyed under metes-and-bounds or Spanish and Mexican land grant systems. In practice this means the west, the midwest, the plains, Alaska and Florida are covered by the rectangular system, while New England, the mid-Atlantic, much of the south-east, Texas and Hawaii are not. Within the PLSS states, the survey grid is essentially complete for surveyed lands, but large parts of Alaska remain unsurveyed and are represented as protraction diagrams rather than surveyed townships – a legally significant difference. Federal surface management coverage is national in the sense that it shows federal holdings wherever they are, but the density is overwhelmingly western: federal land is a majority of several western states and a rounding error in most eastern ones. The historical patent record covers the public domain states from the earliest federal disposals through the twentieth century, with digitisation completeness varying by state and era – some states are comprehensively imaged, others have index-only coverage for parts of their record. Update rhythm is slow and administrative: the survey grid changes when a resurvey or a new survey is filed, status layers change when land is acquired, exchanged, withdrawn or designated, and the historical record grows only as more archival material is scanned.

Known blind spots

Absence of evidence here is not evidence of absence. These are the conditions under which PLSS / BLM Cadastral (US) will not show you something that is nevertheless real:

• This is not a private property register. It will not tell you who owns a private parcel, what it sold for, whether it is mortgaged, or who lives there – all of which are county recorder and assessor functions with no federal aggregation.
• The PLSS does not exist in about twenty states, so an investigation east of the public domain line or in Texas gets nothing from the survey layers and must work in metes-and-bounds descriptions and colonial or state grant systems instead.
• Large areas of Alaska are unsurveyed and appear only as protraction diagrams – a mathematical extension of the grid that has no monuments on the ground and therefore no legal force as a boundary.
• The digital grid is a cartographic representation compiled to a data standard, not a boundary survey. Where it conflicts with the official plat, field notes and monuments on the ground, the ground and the plat govern and the digital layer is simply wrong.
• Tribal lands, allotments and trust status are represented inconsistently and are legally complex in ways that no polygon captures. Do not assert jurisdiction over trust or restricted land from these layers alone.
• Mineral estate representation is complete only for federal minerals. Private and state mineral ownership, and the severances recorded only in county deeds, are invisible, which means a split-estate picture built from this source is partial by construction.
• Historical patent digitisation is uneven. A missing patent may mean the land never left federal ownership, or that the record has not been imaged, or that it was conveyed under a state rather than federal grant – three very different conclusions with the same appearance.
• Case-level records for active authorisations are administrative documents about the agency's own business. They reflect what has been filed and processed, not what is happening on the ground, and an expired case does not mean activity stopped.
• Nothing here is timely. Status changes propagate on administrative cycles measured in months, so a recently completed land exchange or withdrawal will not yet appear even though it is legally effective.

Write the blind spot into the product. A statement that something “was not observed in PLSS / BLM Cadastral (US)” is defensible; a statement that it “did not happen” is not, and the difference is what survives cross-examination.

Access, licensing and what you may do with it

Access model: Open — no account required

The ArcGIS REST services are open and unauthenticated. Point a browser or an HTTP client at the services root and you get the directory of published services, each with layer descriptions, field lists and supported query operations – which is the correct way to learn the current schema rather than trusting any written description including this one. Query endpoints accept spatial and attribute filters and return JSON or GeoJSON, with server-side record limits per request that force pagination on large extents. For volume work, look for the published download packages of the national layers rather than paging a service several hundred thousand times. The General Land Office records site is a separate web application with its own search over patents, plats and field notes; it is designed for interactive research rather than bulk extraction, and it returns scanned images that require reading rather than parsing. The land and mineral records system for case-level data is a separate system again, oriented toward reporting rather than integration. In practice a serious workflow uses three routes: services for geometry and status, the historical records application for documents, and the case system for authorisations, joined on the legal description.

Licence

As works of the United States Government, BLM-produced data and documents are in the public domain domestically and can be reused, redistributed and incorporated into commercial products without permission or fee. The agency attaches standard disclaimers about fitness for legal boundary determination that are not licence restrictions but are substantive warnings: the data is explicitly not a substitute for a boundary survey, and using it to assert a property line is a misuse the agency disclaims. Some layers incorporate state, tribal or partner contributions with their own terms recorded in layer metadata, and scanned historical documents occasionally include material with separate provenance. The practical rule is that you may publish freely, you should cite the specific layer and its currency date, and you must not represent a digital polygon as a surveyed boundary. That last point has legal consequences in property disputes and is the reason the disclaimers exist.

Rate limits and fair use

No published quota, but ArcGIS REST services enforce a maximum record count per request – commonly a low four-figure number – which is the practical constraint you will meet first. Design queries to be spatially bounded and paginate with result offsets rather than requesting a state at once. Keep concurrency modest, identify yourself in the user agent, and back off on errors rather than retrying immediately; these are shared services supporting the agency's own operations as well as the public. Because the underlying data changes on administrative timescales, caching is not just permitted but correct: pull the layers you need, hold them locally, and refresh quarterly or when you have reason to think a status changed. The historical records application is interactive and should be treated as such – scripted bulk harvesting of scanned images is both slow and outside the spirit of a research service, and the documents you actually need in an investigation number in the dozens, not the millions.

Licensing changes, and it changes without warning. A dataset that was free for research this year may not be free for commercial or evidential use next year. Confirm the current terms before you build a dependency on it, and record the terms you relied on alongside the data — the licence in force at the time of collection is part of the provenance.

Collecting it

How PLSS / BLM Cadastral (US) is actually pulled, in the order you would set it up. Prefer the bulk or export interface over per-item lookups wherever one exists: it is kinder to the publisher, faster for you, and gives a reproducible snapshot rather than a series of point-in-time answers you cannot reconstruct later.

Method	Format	Cadence	Notes
ArcGIS REST feature query	JSON	Quarterly refresh; on-demand for specific tracts	Spatially or attribute-filtered queries against the PLSS, surface management and mineral estate layers. Returns geometry and attributes as JSON or GeoJSON. Respect the per-request record cap and paginate.
Service directory introspection	JSON	Before every schema change	The services root and each layer's metadata endpoint describe fields, types, domains and extents. This is the authoritative current schema and should be read at build time rather than assumed.
Bulk layer download	bulk	Per publication	Packaged national or state extracts of the survey and status layers. The right route for anything above a county and the only sane way to hold the PLSS grid locally for repeated legal-description resolution.
Historical land records search	HTML	Ad hoc	Interactive search over federal land patents, survey plats and field notes by name, legal description or document number, returning indexed metadata and scanned images. Manual work, high value per document.
Land and mineral case records	CSV	As cases change	Case-level records for leases, claims, rights-of-way and authorisations from the agency's records system. Reporting-oriented rather than API-first, so expect extract-and-parse rather than a clean feed.

Ingesting it into the platform

Every step below is idempotent and cursor-based: interrupt one and it resumes from where it stopped rather than duplicating rows or losing progress. Collection is recorded per source, so a feed that quietly stops publishing shows up as a stale timestamp instead of silently thinning your coverage.

1. Register the survey grid as reference data, not as intelligence — The PLSS layers are a coordinate framework and belong in the platform as a resolution service. sources.php holds them with their compilation date, and they are used to translate between legal descriptions and geometry rather than to generate records.
2. Build the legal description parser — import.php normalises inbound legal descriptions – meridian, township, range, section, aliquot – into a canonical form and resolves them to geometry against the local PLSS copy. Handle irregular sections, government lots and fractional townships explicitly, because they are where naive parsing produces confident errors.
3. Load status layers with their currency dates — Surface management, mineral estate and designation layers are ingested with the compilation date carried as a first-class attribute, so that any status assertion the platform makes is dated rather than presented as current.
4. Cross-resolve against the geographic frame — resolve-everything.php ties PLSS geometry to the National Map boundary and hydrography layers, so a legal description also yields a county, a watershed and a named locality without a second lookup.
5. Attach historical patents as documents, not as records — Patents are scanned instruments. The platform stores the index metadata – patentee, date, authority, legal description, document number – as structured data and the image as an attached document, keeping the distinction between what was indexed and what the instrument actually says.
6. Wire mineral and energy questions into the domain views — Split-estate and federal mineral status feed the energy mission view, where a lease, a permit and a surface conflict can be seen against the same legal description.
7. Refresh on administrative cadence — cron.php pulls status layers quarterly and compares against held versions, raising a change record when a tract's administering agency or mineral status moves. Daily polling of a source that changes seasonally generates noise and nothing else.
8. Preserve superseded status snapshots — Land status history is the analytical product. Prior versions of the status layers are retained so that the platform can answer what the status was on a past date, which is the question that actually arises in litigation and in historical work.

Registered sources and their last-collected state are listed in sources.php, and the scheduled chain that keeps them current is in automation.php.

How it is wrong, and how to tell

Every dataset is wrong in characteristic ways. Knowing which ways is the difference between using a source and being used by one, and it is the part of source evaluation most often skipped because it is the part that takes work.

The survey framework is high quality for what it is, and the qualification matters more than the compliment. CadNSDI is compiled to a documented data standard from official plats by state offices, and in well-resourced states it is accurate to a few metres and internally consistent. In other states it is a digitised approximation of century-old paper, and the agency says so in the metadata. The critical point is categorical rather than numerical: the digital representation has no legal standing as a boundary. The plat, the field notes and the monuments on the ground are the authority, and where they disagree with the polygon, the polygon is wrong. Status layers are reliable for federal land and silent about everything else, and their reliability degrades near boundaries and in areas with active exchanges. The historical patent index is generally faithful to the instruments but the transcription of nineteenth-century names is imperfect, and the imaging is incomplete in ways that vary by state. Judge quality per layer and per state from the metadata, and treat any assertion that depends on a boundary being exactly where the polygon says it is as requiring a survey rather than a query.

Characteristic false positives

• Township and range without a meridian: the same township and range designation recurs under every principal meridian, so a description parsed without the meridian will resolve to the wrong state entirely and look perfectly reasonable doing it.
• Regular-grid assumptions on irregular townships: sections are not always 640 acres, aliquot subdivision does not always apply, and government lots exist precisely where the grid broke. Software that divides a section into quarters mathematically produces parcels that do not exist.
• Digital polygon treated as a legal boundary: the most consequential error in this source. A dispute, a trespass allegation or an encroachment finding built on the polygon rather than the survey is not defensible.
• Federal absence read as private ownership: a tract not shown as federal may be state, tribal, municipal or in a status the layer does not model. The layers describe federal administration, not the complement of it.
• Surface status read as mineral status: they are severed across huge areas of the west, and reading one from the other reverses the answer on split estate – which is exactly the situation where the question matters.
• Patent absence read as no conveyance: an unfound patent may be undigitised, indexed under a variant spelling, issued under a state grant, or in a record series not covered. Three of those are archival gaps and one is a finding.
• Case records read as ground truth: an active lease means an authorisation exists, not that drilling is happening; an expired one means the paperwork lapsed, not that operations stopped. The system tracks the agency's business, not the world.
• Currency drift in status layers: land exchanges, withdrawals and designations become legally effective long before they appear, so a recent change looks like no change.

None of these make the source unusable. They make it a source that requires corroboration before an assertion built on it goes into a product, which is true of every source and admitted by few.

Ageing

The survey grid barely ages – a township surveyed in 1878 is still described the same way – but its digital representation improves over time as states resurvey and recompile, so an old local copy is worse than a new one even though the underlying reality did not move. Status layers age in discrete jumps on administrative events: an exchange, a withdrawal, a designation, a transfer between agencies. Between events they are perfectly current and after one they are silently wrong until the next compilation. Case records age fast and badly, because case status is a workflow state that changes without any external signal and an extract taken last year describes last year's paperwork. Historical patents do not age at all; they are documents about a fixed past, and their only movement is the slow addition of newly scanned material. A stale record in this source looks exactly like a current one. The practical defence is to carry the layer's compilation date into every assertion and, for anything with legal or financial consequence, to verify current status directly with the administering agency rather than from a cached polygon.

What this source feeds

A source is only worth what it lets you conclude. These are the disciplines that collect through it, the mission domains it serves and the data points it yields — every one is a tag, so you can follow any thread from here into the rest of the library.

Collected by these intelligence disciplines

• Government Intelligence

Serves these mission domains

• Energy Security
• Border Security & Migration

Yields these data points

• Real Property / Parcel

How each sector uses PLSS / BLM Cadastral (US)

The same dataset is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The records are shared — the constraints, thresholds and outputs are not.

🎖 Military and defence

Installation and range management, and any domestic operation touching federal land, depends on knowing which agency administers the surface and what withdrawals apply. Military withdrawals of public land – ranges, training areas, buffer zones – appear in the status layers and their boundaries determine access, environmental obligation and jurisdiction. For domestic support and border operations, the surface management layer answers which federal law enforcement authority applies on a given tract, which is a decision that has to be made before an operation rather than after. The survey grid is also the language in which land withdrawals, rights-of-way and utility corridors are written, so anyone reading a federal land instrument needs to be able to resolve a township-range-section description to ground. Expect the layers to lag recent administrative action and confirm current status with the administering agency for anything operational.

🕵 National intelligence

The GOVINT value is in ownership and control of terrain rather than in reporting. Federal land status determines which government body has authority, what regulatory record will exist, and where foreign or corporate acquisition of land is even possible. For work on foreign acquisition of land near sensitive sites – a recurring counterintelligence concern – this source establishes the federal baseline and the split-estate picture, and county records supply the private layer above it. The historical patent record is a genuine and underused analytical asset for understanding how land tenure in a region formed, which explains present-day patterns of control that look inexplicable from current data alone. Remember the source is entirely domestic and administrative, and that its silences about private and tribal land are structural rather than incidental.

👮 Law enforcement

Jurisdiction and land status are the operational questions. Whether an offence occurred on federal land determines which agency investigates, which prosecutor charges and which statute applies, and the surface management layer is the first-pass answer to that. For public-lands crime – timber theft, artefact looting, illegal grazing, unauthorised cannabis cultivation, dumping, wildlife offences – the status and grazing allotment layers identify the responsible manager and the authorised users of a tract, which converts an anonymous location into a set of people with a documented relationship to it. Mining claim and lease records identify who has a legal interest in a site. Treat every polygon as investigative lead material rather than as an element of proof, and get a survey or an agency records custodian for anything that will be charged.

🔍 Private investigation and corporate security

For asset tracing and due diligence in the western United States, this is where the federal layer of a land picture comes from, and it is free. Mineral and lease interests are assets that do not appear in county deed searches oriented to surface title, and a subject holding federal oil, gas or mining interests is visible here in a way they are not elsewhere. The historical patent record supports genealogical and heir-property work, which is a recurring line of business and one where a scanned original instrument is persuasive to a client in a way that a database row is not. The professional discipline is to be clear about the boundary between what this source establishes – federal status, survey description, historical conveyance – and what it does not, which is current private ownership. Selling the former as the latter is how firms get sued.

📰 Journalism and OSINT media

Public lands reporting runs on this data. Which company holds leases on which federal tracts, where grazing allotments sit relative to conservation designations, how a land exchange moved acreage between owners, what a national monument boundary actually encloses – all of it is answerable from these layers and all of it is public domain, so maps can be published without licensing. The historical patent record adds a dimension most coverage lacks: how a region's land tenure was created, and by whom, which frequently reframes a contemporary dispute. Two cautions for publication: never present a digital polygon as a property line in a story about a boundary dispute, and always date the status layer, because land status stories are usually about a change and the layer may predate it.

🌍 NGO, humanitarian and human rights

Conservation, environmental justice and indigenous rights organisations use the status and designation layers to establish what protections apply where, to track changes in federal land designation over time, and to identify the split-estate situations where surface owners have limited ability to prevent mineral development. Grazing allotment and lease data supports monitoring of authorised use against observed condition. For work with tribal nations, the layers should be treated as the federal government's representation of land status – which is precisely the thing often in dispute – rather than as neutral fact, and assertions about trust or restricted land should be developed with the nation concerned. The historical patent record is directly relevant to dispossession research and to heir property work, where the original conveyance is the starting point of a chain that later broke.

🎓 University and research

For land tenure, environmental history, resource economics and legal geography this is a primary source of unusual depth: a machine-readable survey framework, a status layer, and a digitised archive of the instruments by which a continent was transferred out of public ownership. The patent record supports quantitative work on settlement, on the operation of the homestead and mineral entry statutes, and on the geography of railroad and military grants. Methodologically, the recurring pitfalls to teach are the meridian problem, the irregular township problem, the difference between the cartographic grid and the legal survey, and the uneven digitisation of the historical record – the last of which biases any count of patents by state and era in ways that are easy to miss and fatal to inference.

Playbook: working PLSS / BLM Cadastral (US) end to end

A repeatable sequence from first pull to finished product. Each phase states what you are trying to establish, not merely what to click — the objective is a defensible chain of reasoning, not a completed checklist.

Phase 1 — Establish whether the PLSS applies at all

Check your area of interest against the public domain states before anything else. If you are in New England, the mid-Atlantic, much of the south-east, Texas or Hawaii, there is no township and range and the legal descriptions you encounter will be metes and bounds or colonial or state grants. Discovering this after building a parser is a common and avoidable waste.

Phase 2 — Read the service directory before writing code

Open the ArcGIS services root and the layer metadata endpoints and record the actual field names, types and domains you will consume. Published descriptions age; the service directory is the current truth. Note the maximum record count per request at the same time, because it determines your pagination strategy.

Phase 3 — Resolve the legal description carefully

Parse meridian, township with direction, range with direction, section and aliquot as separate components and never accept a description missing the meridian. Handle government lots and fractional sections as explicit cases rather than as failures. A description that resolves to a plausible location in the wrong state is the characteristic failure and it does not announce itself.

Phase 4 — Determine surface status and administering agency

Query the surface management layer for the tract and record which agency administers it, along with the layer's compilation date. This single determination drives jurisdiction, which records exist, whom you can ask, and what law applies. Where the tract is not federal, say that it is not federal rather than that it is private.

Phase 5 — Check for split estate before drawing any conclusion about resources

Query the mineral estate layer separately from the surface layer and expect them to disagree. Federal minerals under private surface is common and is the structural cause of most surface-use conflict in the west. An analysis that reads mineral rights off surface ownership will be wrong in exactly the cases that matter.

Phase 6 — Pull the case records attaching to the tract

Leases, claims, permits, rights-of-way and allotments name holders of record and give you people and companies with a documented interest in the ground. Read status and dates carefully: these are administrative states, and an authorisation existing is not activity occurring. Record the case serial numbers so the finding can be re-verified.

Phase 7 — Go back to the original conveyance

Search the historical land records for patents covering the legal description. You get the first private holder, the date, the statute and a scanned instrument. This anchors a chain of title at its origin and frequently explains present-day parcel shapes, access easements and mineral severances that are otherwise inexplicable.

Phase 8 — Widen the patent search by neighbourhood and date

Patents issued for adjoining tracts around the same date often indicate family groups, company acquisitions or a single settlement scheme. Reading a township's patents as a set is far more informative than reading one, and it is cheap once you are in the records. Watch for name spelling variants and search phonetically as well as exactly.

Phase 9 — Cross to the county for the private layer

Take the legal description to the county recorder and assessor to get from the original patent to current ownership, encumbrances and value. This is the step that converts a federal land-status picture into a present-day ownership picture, and there is no way around it. Note which county – the PLSS grid crosses county lines freely.

Phase 10 — Build the temporal status picture

If the question involves change – a land exchange, a designation, a withdrawal, a transfer – compare status layer versions across dates rather than reading the current one. Where you lack historical layers, the Federal Register is where the legal instrument that made the change was published, and it is dated precisely.

Phase 11 — Escalate to the survey record for any boundary question

If your conclusion depends on where a line actually is, stop using the digital layer and get the official plat and field notes, and if the stakes justify it, a licensed surveyor. The polygon is a representation compiled to a tolerance, and a boundary assertion built on it will not survive contact with a competent opponent.

Phase 12 — State status with its date in the product

Every land status assertion in the finished report should read as status per the layer compiled on a stated date, not as a bare fact. This is the difference between a finding that ages gracefully and one that becomes wrong the moment an exchange completes, with no way for a reader to tell.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

What to pair it with

No single source carries a finding. These are the datasets that corroborate, extend or contradict this one — and a source that contradicts is worth more than one that agrees, because it is the only thing that will tell you when you are wrong.

Source	Relationship	What it adds
INSPIRE / data.gov cadastral (US NationalMap)	prerequisite	Supplies the terrain, hydrography, boundary and named-feature frame that land status polygons need to become intelligible on the ground. Use the two together: status from BLM, geography from USGS.
County recorder and assessor records	extends	The only source of current private ownership, deeds, encumbrances and assessed value. This source anchors the chain at its federal origin; the county holds everything after it.
Federal Register API	corroborates	Land withdrawals, monument designations, resource management plan decisions and lease sale notices are published here as legal instruments, usually before the status layers reflect them.
USASpending.gov	extends	Federal land management contracts, restoration awards and lease revenue arrangements identify contractors and grantees operating on specific tracts, joinable through place of performance and agency.
US Energy Information Administration	extends	Production, well and infrastructure data that gives operational meaning to a federal mineral lease, converting a legal interest into an activity picture.
GovInfo / Official Gazettes	corroborates	Holds the Code of Federal Regulations, statutes and Congressional record behind the land disposal and management statutes named in patent authorities and case records.
US Census Bureau TIGER/Line	corroborates	Independent representation of county, place and tribal boundaries useful for cross-checking which jurisdictions a township spans, and for statistical geography joins.
National Archives land records	extends	Holds the case files behind land entries – the applications, proofs and correspondence – which contain far more than the patent index and are the next step when a patent raises questions.

Legal, ethical and operational constraints

The data is public domain and freely usable, and the significant legal constraints are about how you characterise it rather than whether you may have it. The agency explicitly disclaims the geospatial layers as a basis for boundary determination, and in most jurisdictions asserting a property line from a cartographic product rather than a survey is professionally reckless and potentially actionable. Land status assertions carry similar risk when they are stale: acting on a status that has changed can affect access rights, trespass exposure and regulatory obligation. Tribal land status deserves particular care – the federal representation of trust, restricted and reservation land is both legally complex and sometimes contested, and jurisdiction over acts on such land depends on the parties and the offence as well as the geography, so a polygon is not a jurisdictional conclusion. Historical patent records are public documents about people long dead, but they name individuals and their descendants can be living, so genealogical use should observe ordinary privacy norms even where no law compels it. Finally, combining lease and claim holder data into profiles of individuals engages data protection law in many jurisdictions even though each record is public.

Operational security

Queries go to federal government infrastructure and are logged. A spatially bounded query against the status layers is a fairly loud statement of interest in a specific tract, and a sequence of them describes an investigation's footprint precisely. The historical records application is interactive and search terms – particularly personal names – are more revealing than coordinates, because a name search states who you are looking for rather than merely where. Case record queries against a named lessee or claimant are the most revealing of all. Mitigations are the usual ones: hold the bulk layers locally so that repeated status questions never leave your network, widen queries beyond the tract of interest, separate collection infrastructure from attributable identity, and reserve name searches for the point at which the exposure is worth it. There are no accounts on the open services, so identity is a matter of network path rather than credentials, which limits both the exposure and your ability to control it.

Two rules that hold regardless of jurisdiction. Collection that is lawful is not automatically proportionate, and a dataset assembled for one purpose does not carry consent for another. Where the records concern identifiable people, the question is not only whether you may hold the data but whether holding it serves the purpose you are accountable for.

Is it earning its place?

Sources accumulate. Feeds get added during an incident and are never reviewed again, and a decade later the pipeline is carrying dead weight that nobody dares remove. These are the measures that show whether PLSS / BLM Cadastral (US) is contributing anything, and they are worth baselining now so the answer is available later.

• Share of inbound legal descriptions that resolve to geometry on first pass, broken down by state, which exposes both parser weaknesses and the states where the grid is poor.
• Number of split-estate situations identified where surface and mineral status differ, since finding these is the specific analytical value this source adds over any other.
• Age of your held status layers against the agency's current compilation date, tracked per layer, because status assertions built on stale layers are the main way this source produces wrong findings.
• Ratio of land status assertions in published products that carry an explicit compilation date, which is a direct measure of analytical discipline.
• Count of investigations where a historical patent search materially changed the understanding of a parcel, measuring whether the archival route is actually being used or merely available.
• Frequency with which a boundary question was escalated from the digital layer to the plat or a surveyor, which should be non-zero in any practice doing serious land work.
• Number of federal case records – leases, claims, rights-of-way – successfully attached to entities already in the platform, measuring the source's contribution to entity resolution rather than to mapping.

Beware of volume. Indicator counts rise easily and say almost nothing. Unique contribution — findings this source produced that no other source in your stack would have — is the measure that matters, and it is usually far lower than anyone expects.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

• A township and range description without its principal meridian is not a location. Reject it, ask for the meridian, or infer it from independent geography – never guess from the numbering.
• Learn to read a section as it actually is. Irregular townships, government lots and fractional sections are the norm along water, state lines and older survey boundaries, and they are where a mathematically subdivided section becomes fiction.
• Surface and minerals are different questions with different answers. Ask both, every time, in the western states. Assuming they travel together is how analysts miss the entire structure of a resource conflict.
• The polygon is a picture of the survey, not the survey. For anything consequential go to the plat and field notes, which describe monuments, and remember that the monument on the ground beats every document when they conflict.
• Patent absence has at least four explanations and only one of them is that the land stayed federal. Check spelling variants, check whether the state's records are imaged, and check whether a state rather than federal grant applies before concluding anything.
• Case status is workflow, not activity. Read the dates, read the status codes, and describe them as what the agency's file says rather than as what is happening on the ground.
• Cache the grid, query the status. The survey framework is stable enough to hold locally forever; status layers are the part that changes and the part you should re-check.
• When a status change matters, find the Federal Register notice that effected it. The legal instrument is dated to the day and the map is dated to the compilation, and only one of those is evidence of when the change happened.
• Read a township's patents as a group rather than a tract's patent in isolation. Settlement, speculation and corporate acquisition all leave patterns that are invisible one record at a time.

Questions analysts actually ask

Does this tell me who owns a piece of land?

It tells you whether the federal government owns or administers it, and which agency. For private land it tells you nothing about current ownership – that is a county recorder function in the United States, with no federal aggregation. What it does give you for private land is the original federal patent, which is the first link in the chain of title and the starting point for a county deed search.

Why does my township and range description resolve to the wrong place?

Almost certainly a missing or wrong principal meridian. Township and range numbering restarts at every principal meridian and there are dozens of them, so the same designation exists in many states. Check also for direction indicators – north and south, east and west – which are frequently dropped in transcription and reverse the location.

Can I use the PLSS polygons to settle a boundary dispute?

No, and the agency says so explicitly. The digital layers are a cartographic compilation to a data standard, not a boundary survey, and they have no legal standing as a property line. The official plat and field notes are the authority for the survey, and the monuments set on the ground govern over both. For a real dispute you need a licensed surveyor.

What is split estate and why does this source matter for it?

Split estate is where the surface and the mineral rights beneath it are owned separately, which is extremely common in the western United States because of how federal land was disposed of. This source is the only free national representation of federal mineral estate, so it is where you discover that a private surface owner has federal minerals underneath and limited ability to prevent their development. Private and state mineral severances are not covered and require county deed research.

How complete are the historical patent records?

Digitisation is uneven by state and era. Some states are comprehensively imaged with searchable indexes; others have partial coverage or index-only entries for portions of their record. This matters enormously for quantitative work, because a count of patents by state reflects digitisation as much as history. For a specific tract, absence should prompt a check of the National Archives holdings rather than a conclusion.

What replaced LR2000 and does it matter to me?

The legacy land and mineral case reporting system was retired and its function moved to a modern records platform. It matters in that any script, saved query or documentation written against the old system is dead, and case-level data now comes from a different place with a different structure. Check the agency's land records landing page for the current route rather than trusting older guidance, including guidance in older investigative handbooks.

Is there anything equivalent for states without the PLSS?

Not federally, because the survey system simply does not extend there. In metes-and-bounds states you work from county deed descriptions, colonial or state grant records and state land offices, and the description resolution problem is much harder because the descriptions reference monuments and adjoining owners rather than a grid. Texas has its own land office with its own extensive records, which is a separate research route entirely.

How current is the surface management layer?

It reflects the last compilation, which lags legally effective changes by months. Land exchanges, withdrawals, designations and transfers become effective when the legal instrument takes effect, not when the map is redrawn. For anything operational or legally consequential, confirm current status with the administering agency and use the Federal Register to find the instrument that changed it.

Can I bulk-download the historical patent images?

The records application is designed for interactive research rather than bulk extraction, and scripted mass harvesting of scanned images is both impractical and against the spirit of the service. In practice an investigation needs a specific and small set of documents, and the right approach is targeted search and retrieval. If you have a genuine research need at scale, approach the agency and the National Archives directly rather than scraping.

Standards, formats and interoperability

What this source speaks natively, and what it has to be translated into before a partner can consume it. Work that arrives in a recognised format is easier to defend, easier to hand over and easier to automate against:

• The Public Land Survey System itself, established by the Land Ordinance of 1785 and successive statutes, which is the legal description framework used by deeds, leases and claims across thirty states.
• CadNSDI, the cadastral data content standard governing how the survey framework is represented geospatially and what attributes each layer must carry.
• ArcGIS REST service conventions, which define the query syntax, pagination behaviour, record limits and metadata endpoints used to access the layers.
• Federal Geographic Data Committee metadata standards, which govern the lineage and accuracy statements attached to each published layer.
• GeoJSON and Esri JSON as the interchange formats returned by the query services, and shapefile and geodatabase for packaged downloads.
• The Manual of Surveying Instructions, which is the authority for how public land surveys are executed and therefore for what a plat and its monuments actually mean.
• Federal land disposal statutes cited in patent authority fields – homestead, mineral entry, desert land, railroad grant and others – which classify how land left public ownership.

References

Primary documentation and authoritative references for this source. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

1. BLM Land Records — US Bureau of Land Management. The agency's index of land records services and the authoritative statement of which systems are current. Start here whenever a route described elsewhere has stopped working, which happens.
2. BLM ArcGIS REST services directory — US Bureau of Land Management. The live service directory listing published layers with their fields, domains and extents. The only reliable current schema reference and the first place to look before writing a query.
3. General Land Office Records — US Bureau of Land Management. Searchable index and scanned images of federal land patents, survey plats and field notes. The route to the original conveyance and to the survey documents that govern boundaries.
4. Bureau of Land Management — US Department of the Interior. The agency site, covering land use planning, leasing programmes, designations and state office contacts. Necessary context for interpreting what a status layer means administratively.
5. The National Map — US Geological Survey. The complementary federal geographic base. Land status polygons are hard to interpret without terrain, hydrography and boundaries underneath them.
6. Data.gov catalogue — US General Services Administration. Federal open data index, useful for locating the state and county datasets that fill the private-ownership gap this source leaves open.
7. Federal Register — US National Archives and Records Administration / GPO. Where land withdrawals, designations, management plan decisions and lease sale notices are legally published, usually months before the geospatial layers catch up.
8. GovInfo — US Government Publishing Office. Statutes and the Code of Federal Regulations behind the land disposal and management authorities cited in patents and case records.
9. National Archives — US National Archives and Records Administration. Holds the land entry case files behind patents – applications, proofs, correspondence – which contain the substance that the patent index only summarises.
10. US Energy Information Administration — US Department of Energy. Production and infrastructure data that turns a federal mineral lease from a legal interest into an operational picture, which is usually the question actually being asked.
11. Esri ArcGIS REST API documentation — Esri. Reference for the query syntax, pagination parameters and record limits that govern how much you can extract per request from these services.

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this source: it caches the survey grid as a resolution service, turns any legal description into geometry and jurisdiction, tracks surface and mineral status as dated snapshots rather than current facts, and attaches historical patents to the entities that hold land today.. Browse the full source catalogue, or follow any tag above into the rest of the library.