GIS Parcel Mapping & PLSS Legal Land Descriptions Guide
Technical practices for converting legal land descriptions into spatial GIS layers, managing coordinate datums, and eliminating boundary gaps.
Translating PLSS Aliquot Parts and Metes-and-Bounds Deeds
Land and mineral rights rest on legal descriptions written in deeds rather than visual maps alone. Across the western and midwestern United States, the Public Land Survey System (PLSS) divides land into townships, ranges, sections, and aliquot subdivisions such as the NW/4 of the SE/4. By contrast, colonial states and Texas rely heavily on metes-and-bounds surveys, abstract numbers, or block-and-section grids.
Modern GIS land platforms parse structured PLSS strings directly against authoritative federal cadastral grids while flagging irregular government lots created by surveyed section corrections or navigable rivers. For metes-and-bounds parcels, COGO (coordinate geometry) tools trace bearings and distances from a verified point of beginning to check polygon closure errors before publishing tract layers.
Coordinate Systems, Datums, and Acreage Discrepancies
A leading cause of spatial overlap alerts is mixing coordinate reference systems—such as NAD27, NAD83, and WGS84—without proper datum transformations. Even a 40-meter shift between unprojected survey data and web-mercator basemaps can falsely place a well pad outside a lease boundary or misalign a pipeline corridor across neighboring tracts.
Standardizing storage in a single geodetic datum while computing acreage in an equal-area projection preserves geometric accuracy across large basins. GIS administrators should clearly distinguish deeded (legal) acreage from calculated GIS polygon acreage so landmen understand when small variances reflect survey curvature versus missing tract slivers.
- Store canonical geometries in a documented datum such as NAD83 (EPSG:4269).
- Compute planar areas using local State Plane or Albers Equal-Area projections.
- Preserve both deeded legal acreage and computed GIS acreage as separate attributes.
- Flag polygon closure errors exceeding survey tolerance during COGO deed entry.
Detecting Gaps, Overlaps, and Unleased Slivers
When acquisition teams lease contiguous tracts from dozens of mineral owners, tiny unleased slivers or overlapping depth polygons can create serious compliance exposure. Automated topology rules run spatial intersection checks across lease polygons, drilling spacing units, and environmental buffer zones every time a new instrument is digitized.
Three-dimensional attribute filtering extends spatial checks to stratigraphic horizons. Two leases covering the exact same surface footprint do not overlap legally if Lease A is restricted from surface to the base of the Niobrara formation and Lease B covers all depths below the Niobrara.
Integrating Field Mobile Apps and Satellite Basemaps
Connecting central GIS repositories to mobile field applications empowers landmen, surveyors, and environmental inspectors to verify property corners, fence lines, and reclamation boundaries offline. High-resolution orthorectified satellite imagery exposes encroachments, unpermitted road cuts, and surface water features that static plat books miss.
Exporting standardized GeoJSON, Shapefile, and KML packages allows seamless collaboration with outside title counsel, joint-venture partners, and state regulatory portals without losing attribute linkages to lease numbers or owner IDs.
PLSS Subdivision Acreage & Spatial Reference Standards
| Legal Description Unit | Standard Nominal Area | GIS Representation | Verification Check |
|---|---|---|---|
| Full Township | 36 sq. miles (23,040 acres) | 6 x 6 section grid | Verify principal meridian and baseline |
| Standard Section | 640 acres (1 sq. mile) | Polygon with monument corners | Check northern/western correction lots |
| Quarter Section (e.g., NE/4) | 160 acres | Aliquot quadrant polygon | Confirm equal-area split vs. government lot |
| Quarter-Quarter (e.g., NW/4 SE/4) | 40 acres | 1/16th section polygon | Validate parent section monument control |
| Metes & Bounds / Abstract | Varies by call bearings | COGO traversed polygon | Verify closure error under 1:5,000 ratio |
Nominal PLSS acreages assume regular sections; irregular sections along township north/west borders contain surveyed Government Lots.
Worked Illustration: Parsing a Multi-Part PLSS Aliquot Description
Worked illustration converting a layered PLSS legal description into exact nominal acreage for GIS polygon validation.
- Step 1 (Base Section): Township 4 North, Range 64 West, Section 12 nominally equals 640.00 acres.
- Step 2 (First Subdivision): 'N/2 of the SW/4' equals (1/2) x (1/4) x 640 = 80.00 acres.
- Step 3 (Second Subdivision): 'SE/4 of the SE/4' equals (1/4) x (1/4) x 640 = 40.00 acres.
- Step 4 (Aggregate Tract Check): Combined tract equals 80.00 + 40.00 = 120.00 nominal acres; compare against BLM GCDB lot plat.
Worked Outcome: The parsed legal description maps to 120.00 nominal acres across two non-adjacent aliquots in Section 12, ready for GIS topology check.
GIS Cadastral Mapping Quality Checklist
- Verify principal meridian, township, range, and county state FIPS codes on all tracts.
- Check BLM CadNSDI / GCDB monument coordinates for irregular government lots.
- Confirm consistent datum transformations (NAD27 to NAD83/WGS84) on legacy maps.
- Run automated polygon overlap and gap-sliver topology validation across unit boundaries.
- Tag every polygon with upper and lower stratigraphic depth limits where applicable.
- Store both legal deeded acreage and projected equal-area GIS acreage fields.
Frequently Asked Questions
Why does GIS-calculated acreage rarely match deeded acreage to the exact hundredth?
Deeded acreage comes from historical chain-and-compass surveys or nominal PLSS assumptions, whereas GIS acreage reflects modern geodetic projections and earth curvature adjustments.
What is a Government Lot in the PLSS system?
A Government Lot is an irregular subdivision of a section created where earth convergence, survey errors, or meandered rivers prevented a standard 40-acre aliquot split.
How do you prevent false spatial overlaps on depth-severed leases?
Associate each GIS lease polygon with structured top-depth and bottom-depth formation attributes so overlap queries compare three-dimensional stratigraphic intervals rather than 2D footprints alone.
Which spatial formats are best for exchanging land data with partners?
GeoJSON and Esri Shapefiles or File Geodatabases with embedded `.prj` projection metadata are standard for lossless parcel geometry and attribute exchange.
Primary References & Standards
- Federal Geographic Data Committee (FGDC) — Cadastral Data Content Standard for the National Spatial Data Infrastructure
- U.S. Bureau of Land Management (BLM) — Manual of Surveying Instructions (PLSS Standards)
- Open Geospatial Consortium (OGC) — Simple Features & GeoJSON Coordinate Reference Specifications