How to Batch Convert PLSS Descriptions

Converting one PLSS description to GPS coordinates takes a few seconds. Converting five hundred takes all day — if you are doing them one at a time. Whether you are a landman processing a title run, a GIS analyst building a well location database, or a crop insurance adjuster mapping claims across a county, batch conversion turns hours of manual work into minutes.

This guide covers how to prepare your data, run a batch conversion, and handle the results.

When Batch Conversion Makes Sense

Single conversions work fine for one-off lookups. Batch conversion is the right approach when you have:

• A spreadsheet of legal descriptions from a regulatory filing, lease schedule, or property list
• A title run with dozens or hundreds of tracts across multiple townships
• Well location data from state oil and gas commission records that need GPS coordinates added
• USDA program records tied to sections and quarter sections across a service area
• Timber sale inventories or BLM grazing allotments listed by PLSS location
• Genealogy research involving multiple land patents or homestead entries from GLO records

If you are looking at more than 10 descriptions, batch processing saves significant time.

Step 1: Prepare Your Data

The batch converter accepts descriptions in a CSV file or pasted directly as a list. Each description needs to include enough information for an unambiguous conversion:

Required Components

Every description should include:

• Quarter section (optional but recommended) — NE, NW, SE, SW, or a quarter-quarter like NWNE
• Section number — 1 through 36
• Township — Number and direction (e.g., 5N, 3S)
• Range — Number and direction (e.g., 3W, 7E)
• Principal meridian — The governing meridian (e.g., 6th PM, IM, WM)

Accepted Formats

The batch converter handles several common notation styles:

NE 14-5N-3W 6th PM
NE 1/4 Sec 14 T5N R3W 6th Principal Meridian
T5N R3W Sec 14 NE, Sixth Principal Meridian
SW 22-9N-15W 6th PM
NW 15-8N-4W IM
NE 12-4S-2W WM

You do not need to standardize all descriptions to the same format before uploading. The parser recognizes common PLSS notation patterns and extracts the components automatically.

CSV Format

If your data is in a spreadsheet, export it as a CSV with the PLSS descriptions in a single column. The converter reads one description per row. You can include other columns (property ID, owner name, etc.) — the tool will process the PLSS column and add coordinate columns to the output.

A sample CSV might look like this:

id,description,state
1,"NE 14-5N-3W 6th PM",Kansas
2,"SW 22-9N-15W 6th PM",Nebraska
3,"NW 15-8N-4W IM",Oklahoma
4,"NE 12-4S-2W WM",Oregon
5,"NWNE 8-12N-7E 6th PM",Colorado

Common Data Preparation Issues

Before uploading, review your data for these common problems:

• Missing meridian references. If your descriptions do not include the principal meridian, add a state column so the converter can determine the correct meridian. In single-meridian states (Kansas, Oklahoma, Oregon), the state alone is sufficient. In multi-meridian states (Colorado, California), you may need to specify the meridian explicitly.
• Inconsistent formats. Some spreadsheets mix formats within the same column — "NE 14-5N-3W 6th PM" in one row and "Township 5 North, Range 3 West, Section 14, NE Quarter" in the next. The parser handles most common variations, but extreme inconsistency may cause parsing errors on some rows.
• Lot descriptions instead of quarter sections. Government lots (Lot 1, Lot 2, etc.) along water boundaries replace standard quarter sections. These require the original survey plat data for precise conversion and may not parse the same way as standard aliquot part descriptions.
• Extra text. Descriptions copied from legal documents sometimes include supplementary language — "less and except," easement references, or acreage qualifiers. Strip these to the core PLSS components before uploading.

Step 2: Upload and Convert

Open the Township America batch converter and either:

• Upload your CSV file — Select the file and identify which column contains the PLSS descriptions.
• Paste descriptions directly — Copy your list of descriptions and paste them into the text area, one per line.

Click convert. The tool processes each description, matching it to the BLM PLSS data and calculating the center-point GPS coordinates for the described parcel.

Processing speed depends on volume. A few hundred descriptions convert in seconds. Larger batches of several thousand take a bit longer but still finish in minutes rather than the hours (or days) manual lookup would require.

Step 3: Review the Results

After processing, you get a results table showing:

• Original description — Your input, preserved for reference
• Latitude and longitude — The center-point GPS coordinates for each parcel
• Parsed components — Township, range, section, and quarter section broken out into separate columns
• Status — Whether each row converted successfully or encountered an error

Handling Errors

Some rows may fail to convert. Common reasons include:

• Parsing failure — The description format was not recognized. Check for typos, missing components, or non-standard notation.
• Invalid PLSS reference — The township/range/section combination does not exist in the BLM data. This can happen with transposed digits (writing T3N R5W when you meant T5N R3W) or section numbers outside the 1–36 range.
• Meridian mismatch — The description specifies a meridian that does not cover the given state, or the meridian was not identified at all.

Review error rows individually. Most failures are data quality issues in the input that can be corrected and re-run.

Step 4: Export the Results

Download the results as a CSV with your original data plus the added coordinate columns. You can also export as:

• KML — For viewing in Google Earth
• GeoJSON — For importing into GIS platforms like QGIS or ArcGIS
• Shapefile — For direct use in GIS workflows

The exported file retains all your original columns plus the new latitude, longitude, and parsed PLSS component columns.

Real-World Use Cases

Oil and Gas

A landman processing a title opinion for 200 tracts in the Sixth Principal Meridian area of Wyoming needs GPS coordinates for each tract to build a map exhibit. Upload the list of legal descriptions from the title run, convert, and export a KML file to overlay on Google Earth. What used to take a full day of manual lookups now takes five minutes.

Agriculture

A county FSA office needs to map all enrolled tracts for a disaster assistance review after a hailstorm in central Nebraska. The tract list is in PLSS format — section, township, range. Batch convert the list to GPS coordinates, import into a mapping tool, and overlay the storm track to identify affected tracts.

Real Estate

A title company is verifying legal descriptions for 50 rural property closings across Oklahoma. Each deed references an Indian Meridian PLSS description. Batch convert all 50, generate a map, and confirm that each description matches the expected property location.

GIS and Data

A state agency is building a database of all active well locations from regulatory filings. The filings list well locations as PLSS descriptions. Batch convert thousands of descriptions to GPS coordinates and import them into a spatial database for analysis and mapping.

Tips for Best Results

1. Include the principal meridian whenever possible. The more complete each description is, the higher the success rate.
2. Clean your data first. Remove extraneous text, correct obvious typos, and verify that all descriptions have the minimum required components (section, township, range).
3. Process by state. If your data spans multiple states, grouping by state before upload can help catch meridian assignment issues early.
4. Spot-check results. After batch conversion, pick a few rows and verify them manually. Open the coordinates in a mapping application and confirm they land where expected.
5. Re-run failed rows. Fix the errors flagged in the results and re-process only the failed rows rather than the entire batch.

Batch conversion is one of the most practical features for anyone working with PLSS data at scale. Instead of converting descriptions one by one, you process your entire dataset in a single pass and get back coordinates you can map, analyze, and include in reports.