NGS control monuments · PLSS section grid

Every published NGS mark, on the section grid you already work in.

Pick a township section. See the control monuments inside it with their condition and full datasheet, then send the whole section to your data collector — before you pull out of the turnout.

Open the app See how it works

T1N R3E · SEC 8 6 MARKS

Marks: 801,673Every published NGS control point
Fields per mark: 59The whole datasheet, not a summary
Refreshed: MonthlyNew PIDs added, retired ones flagged
Decimal places: 7Never rounded on the way out

How it works

Four steps, in the order you actually work.

Find your section

Tap the map or let it locate you. Section lines come from the BLM national PLSS, so the boundaries are the ones on your plat.

See what is in it

Every monument inside the section, each showing its condition — so a mark reported destroyed is obvious before you drive to it.

Open the record

The full published record for that PID: State Plane with its zone first, feet and metres, then latitude and longitude. The NGS datasheet is one tap away.

Send it

The whole section as a file — copy it, share it, download it, or email it to yourself. Your format is remembered for next time.

Precision

The digits that reach the file are the digits NGS published.

A northing exported as 890485.564 and read back as 890485.56 is a quarter-inch error the software handed you, silently. Nothing here rounds a coordinate. The file is rendered once, on the server, so the copied, downloaded and emailed versions are byte for byte identical.

Feet are converted per state, not with one factor. Every state legislates the US survey foot except AZ MI MT ND OR SC, which use the international foot. The two differ by roughly 3.7 ft on a typical northing — a surveying difference, not a rounding one.

ngs-T1N-R3E-Sec-8-pnezd.csvPNEZD

1,890485.564,651034.765,1086.94,DV0490 - MESAPORT AZ MK
2,889221.123,651998.301,1092.11,DV2071 - ARLINGTON RM 2
3,888904.887,650117.442,1081.60,DV2076 - GILA BEND AZ
…no header row, no comment lines — a data
collector reads the first field as a point number

Export

Two formats, and the one your collector reads is the default.

PNEZD is point, northing, easting, elevation, description — five bare fields, numbered from one, with nothing in front of them. It is what a data collector and every CAD package import, and it is what the app opens on.

Lat / Long is the full record with a header row, for the spreadsheet the job usually ends up in. Marks with no published elevation are called out rather than left silently blank, because an empty field and a zero are not the same thing to the software downstream.

Delivery: Copy, the device share sheet, a downloaded CSV, or emailed to an address you type once and it remembers.
Scope: A single mark, or every mark in the section, from the same sheet.
Description field: PID - designation, so a row ties back to a datasheet after the point numbers are renumbered.
Provenance: Travels inside the full-record file, for whoever opens it who was not there when it was made.

In the field

Built for the half of the job with no signal.

Sections you have looked at are cached on the device, with their marks, automatically. Drive into a canyon and the data you already pulled is still there — no sync button, no "you are offline" wall between you and a coordinate you loaded an hour ago.

The map remembers the section you were last working in, and the format you last sent. A surveyor works one job in one coordinate system, so neither should be a decision you make twice.

Everything the app remembers stays on the device. Your email address is used to send the file you asked for and is not retained or sold.

iPhone & iPadInstalled app

AndroidPhone and tablet

Any browserInstalls to the home screen

DesktopFor the office half of the work

Get started

Open it, pick a section, and see what is out there.

Nothing to install to try it — it runs in the browser, and installs to your home screen if you want it there.

Open the app Email us