Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

Place and export

A metes-and-bounds description defines shape, not location, so placement comes in three ways. All three behave the same in QGIS.

  • PLSS aliquot tracts already know where they are, so the browser places them for you: they are on the map, georeferenced from BLM’s public survey fabric, by the time the result opens. The card’s place button reads Placed before you have touched it.
  • Metes-and-bounds tracts take one click on the point of beginning. A live preview follows the cursor; adjust rotation if the deed’s bearing basis differs from grid north, then confirm.
  • Composite conveyances, where two or more tracts tie to the same commencement monument, place together. One click on that monument puts every tract at the offset its own tie courses describe, and rotation turns the assembly as a unit.

An aliquot tract placed on Citrus County imagery, its card showing a REVIEW verdict and the PLSS chain

The browser handles projection itself, so the geographic-CRS warning QGIS shows never appears here.

GeoPackage writes every placed tract as a polygon layer (verdict, closure, acreage, provenance) plus a per-call line layer (bearing, distance, confidence, verbatim text per segment).

DXF writes the traverse for a CAD operator. It arrives unplaced by design: point of beginning at the origin, distances in feet, because a deed describes a shape rather than a location and the basis is theirs to set. Curves come through as true arcs.

Certificate writes the GroundTruth Certificate of Digitization, the one-page artifact that goes in a project file.

Copy JSON puts the raw extraction on the clipboard for anything downstream.

Every one of these is byte for byte what the plugin and the API produce. The files are written by the service, not by the client that asked for them.

The runs list answers “where did my result go”, which is otherwise a support email. It spans every key on the account, because a person owns keys rather than the other way round.

It resurrects nothing and says so: a result that has been swept stays in the list with its availability marked false, and the response carries how many days fetched and unfetched results are kept. Dropping the row would answer the question with silence.