[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-\u002Fblog\u002Fdrone-surveying-and-plss-connecting-uav-flight-boundaries-to-legal-land-descriptions":3},{"id":4,"title":5,"body":6,"cover":164,"date":165,"description":166,"draft":167,"extension":168,"meta":169,"navigation":172,"path":173,"seo":174,"stem":175,"tags":176,"__hash__":180},"blog\u002Fblog\u002Fdrone-surveying-and-plss-connecting-uav-flight-boundaries-to-legal-land-descriptions.md","Drone Surveying and PLSS: Connecting UAV Flight Boundaries to Legal Land Descriptions",{"type":7,"value":8,"toc":153},"minimark",[9,13,16,21,24,27,31,34,37,51,55,58,61,65,68,90,93,97,100,103,123,126,130,133,136,140],[10,11,12],"p",{},"A drone finishes a flight and hands you a boundary. The output is a polygon of latitude and longitude vertices, a point cloud, and maybe a shapefile the flight software exported. That geometry is precise, but it is not what a right-of-way application, a title document, or an Application for Permit to Drill (APD) asks for. Those filings want a legal description: a section, township, range, and aliquot part tied to a principal meridian.",[10,14,15],{},"This post walks through how a survey team closes that gap: taking a UAV flight boundary, running a reverse PLSS lookup on its corners, verifying the geometry against the actual parcel, and exporting the result in the formats a permit package needs.",[17,18,20],"h2",{"id":19},"why-drone-surveys-produce-coordinates-but-legal-documents-need-plss","Why drone surveys produce coordinates but legal documents need PLSS",[10,22,23],{},"A UAV survey positions itself with a GNSS receiver, often corrected with RTK, so every vertex it records is expressed as latitude and longitude (or a state plane grid). That is the correct format for a field instrument. It is not the format a county recorder, a state land office, or the BLM expects on a filing.",[10,25,26],{},"A legal description built on the Public Land Survey System reads differently. It names a quarter-quarter (an aliquot part), a section, a township, a range, and a principal meridian, for example the NE1\u002F4 NE1\u002F4 of Section 12, Township 4 North, Range 5 East, Indian Meridian. Permit reviewers, title examiners, and lease administrators work in that notation because it ties directly to the official survey record. So a drone crew ends a flight with accurate geometry and still has to translate it before anyone downstream can act on it.",[17,28,30],{"id":29},"reverse-plss-lookup-from-a-boundary-corner-to-a-legal-description","Reverse PLSS lookup: from a boundary corner to a legal description",[10,32,33],{},"Township America resolves PLSS legal descriptions to coordinates and runs the conversion in reverse: give it a latitude and longitude, and it returns the section, township, range, and aliquot part that contains the point. The reverse direction is the one that matters for drone surveying, because you already have the coordinates and you need the notation.",[10,35,36],{},"The resolution is calculated from official BLM survey data (the GCDB and CadNSDI records), covering 30+ PLSS states and all 37 principal meridians, down to the 1\u002F256 aliquot part. That last detail matters for a survey crew: a boundary corner does not just fall in a section, it falls in a specific quarter-quarter, and the legal description has to name the right one. A lookup that only returns the section leaves you to work the aliquot string out by hand against a township plat.",[10,38,39,40,45,46,50],{},"A practical workflow looks like this. Take the corner coordinates of the drone boundary, run each through the reverse lookup, and record the section and aliquot notation returned. For a single tract you can do this in the browser with the PLSS converter. If you also need to go the other way, from a written description to coordinates, the ",[41,42,44],"a",{"href":43},"\u002Fguides\u002Fconvert-section-township-range-to-coordinates","guide to converting a section, township, and range to coordinates"," covers that direction, and there is a fuller walkthrough of the ",[41,47,49],{"href":48},"\u002Fblog\u002Fgps-to-legal-description-reverse-plss-lookup","reverse PLSS lookup"," itself.",[17,52,54],{"id":53},"checking-the-drone-boundary-against-the-parcel-with-geojson-polygons","Checking the drone boundary against the parcel with GeoJSON polygons",[10,56,57],{},"Naming the section is only half the check. You also want to confirm that the flight boundary lines up with the parcel it is supposed to describe. A transposed range digit or a misread aliquot part will still return a valid-looking answer, so the geometry has to be verified, not trusted.",[10,59,60],{},"Every section and quarter-section lookup returns a full GeoJSON polygon of the actual BLM survey boundary, not a centroid point estimated from a grid formula. That means you can overlay the drone boundary and the survey polygon in the same view (QGIS, ArcGIS, or a Leaflet map) and see whether they agree. A mismatch calls for review against survey records before the permit is filed. Matching polygons support the check but do not certify a legal boundary.",[17,62,64],{"id":63},"batch-workflows-for-multi-parcel-drone-projects","Batch workflows for multi-parcel drone projects",[10,66,67],{},"A corridor survey, a multi-parcel acquisition, or a season of flights produces more boundaries than a single-query browser workflow handles. Township America handles the volume in two ways:",[69,70,71,79],"ul",{},[72,73,74,78],"li",{},[75,76,77],"strong",{},"File upload."," On the Business plan, you can upload a CSV or Excel file and convert thousands of records in one pass, then take the results out as structured exports. This suits a survey shop that batches a project at the end of a flight week.",[72,80,81,84,85,89],{},[75,82,83],{},"REST API."," When the conversion needs to run inside a pipeline rather than in a person's browser, the ",[41,86,88],{"href":87},"\u002Fapi","REST API"," exposes single-lookup, batch, autocomplete, and map-tile endpoints, with Python and TypeScript SDKs and an MCP server for AI agents. The batch endpoint accepts up to 100 records per request and returns coordinates and GeoJSON polygon geometry as structured JSON, so a GIS pipeline can refresh legal descriptions on whatever schedule the project runs.",[10,91,92],{},"Use file upload for a periodic review and the API for an unattended pipeline. The remote MCP connector is included on Pro and Business.",[17,94,96],{"id":95},"exporting-for-permit-filings-shapefile-dxf-and-kml","Exporting for permit filings: Shapefile, DXF, and KML",[10,98,99],{},"Once the boundaries are resolved and verified, the result has to leave in a format the next tool can open. The Business plan includes structured exports in CSV, KML, Shapefile, GeoJSON, and DXF.",[10,101,102],{},"The format you pick depends on where the data is going:",[69,104,105,111,117],{},[72,106,107,110],{},[75,108,109],{},"DXF"," drops the parcel geometry straight into CAD, which is where most survey deliverables are assembled.",[72,112,113,116],{},[75,114,115],{},"Shapefile and GeoJSON"," move the boundaries into a GIS for overlay and analysis.",[72,118,119,122],{},[75,120,121],{},"KML"," is convenient for a quick visual review in a map viewer before the package goes out.",[10,124,125],{},"For a permit filing, the written legal description carries the parcel, and the exported geometry supports it as an exhibit. Having both come from the same resolved source keeps the notation and the drawing consistent.",[17,127,129],{"id":128},"a-worked-example-a-highway-right-of-way-survey","A worked example: a highway right-of-way survey",[10,131,132],{},"Consider a drone flight over a proposed highway right-of-way in Oklahoma. The UAV returns a boundary as a set of latitude and longitude vertices, accurate but with no legal notation attached.",[10,134,135],{},"The team runs each corner through the reverse lookup. A vertex near the northeast edge resolves to the NE1\u002F4 NE1\u002F4 of Section 12, Township 4 North, Range 5 East, Indian Meridian; the run continues across the rest of the corners, and the right-of-way is described as it crosses from one aliquot part into the next. Each lookup returns the section polygon as well, so the crew overlays the flight boundary on the survey boundaries and confirms the corridor sits where the description says it does.",[17,137,139],{"id":138},"closing-the-loop-between-the-flight-and-the-filing","Closing the loop between the flight and the filing",[10,141,142,143,147,148,152],{},"The missing step between a drone boundary and a filing-ready legal description is the PLSS translation. Township America handles it: reverse lookup for the notation, a survey-accurate polygon to verify the boundary, batch and API paths for volume, and CAD-ready exports for the deliverable. Start with the ",[41,144,146],{"href":145},"\u002Fplss-converter","PLSS converter"," or review batch and export options on the ",[41,149,151],{"href":150},"\u002Fpricing","pricing page",".",{"title":154,"searchDepth":155,"depth":155,"links":156},"",2,[157,158,159,160,161,162,163],{"id":19,"depth":155,"text":20},{"id":29,"depth":155,"text":30},{"id":53,"depth":155,"text":54},{"id":63,"depth":155,"text":64},{"id":95,"depth":155,"text":96},{"id":128,"depth":155,"text":129},{"id":138,"depth":155,"text":139},"\u002Fimages\u002Fblog\u002Fdrone-surveying-and-plss-connecting-uav-flight-boundaries-to-legal-land-descriptions\u002Fcover.webp","2026-09-24T10:00:00Z","Drone surveying and PLSS rarely speak the same language. Turn UAV boundary coordinates into township, range, section, and aliquot notation for permit filings.",false,"md",{"author":170,"category":171},"Township America","guides",true,"\u002Fblog\u002Fdrone-surveying-and-plss-connecting-uav-flight-boundaries-to-legal-land-descriptions",{"title":5,"description":166},"blog\u002Fdrone-surveying-and-plss-connecting-uav-flight-boundaries-to-legal-land-descriptions",[177,178,179],"drone-surveying","plss","reverse-lookup","0qN1GgNQy1Pd4hj9qeq54_h24CDzNNHN-4ieoDcZGkI"]