Skip to content

Main content

Public Township Section Index Tool

Locate a supplied public section in an explicit serpentine grid, without inferring a legal land description.

Loading tool…

Description

Return section position in a supplied township grid.

Historical and archival records distinguish source labels, local grid conventions, edition numbers and validity periods. A parsed token or geometric area term cannot establish provenance, historical identity or land rights. Date endpoints, text-counting units and numbering origins must match the original record.

Return section position in a supplied township grid.

When to use this tool

Use Public Township Section Index when checking the stated archival record, grid, edition or validity-period convention.

How to use the tool and how it works

  1. Enter section, sectionsPerRow, rows, serpentine, firstRowEastToWest. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read row, column. Use the output convention below.

Return section position in a supplied township grid. Require positive whole section/dimensions and section <= rows*columns; derive zero-based row/offset, reverse columns under firstRowEastToWest and alternating serpentine policy.1

Input fieldMeaning and unitsAccepted input
sectionSectionRequired. Safe integer; minimum 1.
sectionsPerRowSections Per RowRequired. Safe integer; minimum 1.
rowsRowsRequired. Safe integer; minimum 1.
serpentineSerpentineRequired. Boolean.
firstRowEastToWestFirst Row East To WestRequired. Boolean.
Output fieldInterpretationReturned shape
rowRowRequired. Safe integer.
columnColumnRequired. Safe integer.
json
{
  "input": {
    "section": 7,
    "sectionsPerRow": 6,
    "rows": 6,
    "serpentine": true,
    "firstRowEastToWest": true
  },
  "output": {
    "row": 1,
    "column": 0
  }
}

Limitations and assumptions

  • The grid convention is supplied rather than a full public-land survey decoder; actual boundaries and legal title are not established.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Consult the original archive, survey and applicable authority for historical interpretation, provenance or actual property rights.

References

  1. Calculation and input contract: american-studies/public-township-section-index — tool.io

Similar or alternative tools