easting
Easting reads recorded deeds and easements, verifies closure and acreage, and places them on your map. Work in the browser, in QGIS, or through the API.
A vision model reads the document. Deterministic code decides whether to believe it. Every parcel, corridor, and site Easting produces arrives with the arithmetic already checked and the source text still attached.
Easting Deeds turns a recorded land document into parcel geometry you can put on a map: one verification engine behind three surfaces, the browser app, the QGIS plugin, and the hosted API. You plot the deed straight from the PDF the county gave you, scanned, stamped, no text layer, and it transcribes every course with the words it was read from, walks the traverse, and tells you whether the result can be trusted before you place anything. One account covers all three: same key, same quota, same results wherever you work.
What goes in
Recorded deeds, easements and rights of way, subdivision plats, and utility as-builts. PDF, TIFF, PNG, a phone photo of a recorded page, or a legal description pasted as text. Descriptions in feet, meters, varas, or chains.
What comes out
Polygon and per-course line layers in your project, a GeoPackage or DXF for the people downstream, and a signed GroundTruth Certificate of Digitization for the file.
What gets checked
The traverse has to close to better than 1:5,000 and the computed area has to corroborate the area the document states, within 2%, in that document's own unit. Whatever fails says which check it failed.
What it refuses
A blanket easement locates nothing, and an illegible plat is not a boundary. Both certify the finding rather than inventing geometry, and an unreadable page says so instead of guessing.
Easting Deeds has the pricing and the full capability list, and the user guide walks the whole path from sign-in to export, in the browser and in QGIS.
Recorded deeds become parcel geometry you can defend in a plat room.
Kill bad sites before the consultants bill for them.
Where to spend the trimming budget, argued from the point cloud.
All three run on the same GroundTruth verification layer.
They shouldn't, and we don't. Acreage sets tax assessments. Buffers decide who gets legal notice. So the model's job at Easting is narrow: transcribe faithfully, quote its source, and flag what it cannot read. Everything that follows is arithmetic.
This is GroundTruth, the verification layer every Easting product passes through. On the evaluation corpus that qualified it, no extraction containing an error ever reached a PASS.
Easting Deeds is shipping. Start free (3 documents, no card) in the browser, or do the whole signup from the plugin's settings inside QGIS: first deed in minutes. Assembling rights across parcels instead? Easting for land teams covers easements and rights of way.