Field sheet
Flights
– square miles
– flight time
– battery sets
– photos
– control points
– checkpoints
– to survey them
– distance
– travel time
– stops
Start on the map: draw an area, draw a corridor along a fiber route or road, import the client's file, or set a launch point to get a starter area around it.
Breakdown
Save everything as
KML
KMZ
GPX
GeoJSON
Stops Nowhere to go yet. Set a launch point and the day's stops appear here by themselves, or search for a place, click a pin, or right-click (long-press on a phone) anywhere on the map.
Add the day's stops
Add a spot on the map
Shortest order
Clear
Add a place from this project
This project has no launch point, corridor launch points, GNSS bases or control points yet.
Starting from
My location
Pick on the map
Directions
Units and voice
Distances in Miles and feet Kilometres and metres
Try again
Start navigation
Apple Maps
Google Maps
Needs a connection Save for offline
Directions (PDF)
Route (GPX)
Route (KML)
Step by step
Saved on this device A saved route works with no signal: the route, its steps and the map along it are kept here. Working out a new route needs a connection.
Directions: Swathwise's own router (Valhalla) on © OpenStreetMap contributors. Only the places asked about are sent to it; nothing about a route is kept or counted.
1 Mark the area
Draw an area
Draw a corridor
Pick a road
Pick parcels
Import a file…
Set launch point
Merge areas
Clear all
2 What the control is for
Drone job
Trimble MX60 (driven)
Product vertical accuracy (RMSE, cm)
Product horizontal accuracy (RMSE, cm)
Surveyed with
Method
Farthest point from the base (km)
The receiver's figures, and where they come from
3 Place the points
Control points
Checkpoints
Place the points
Add a control point
Add a checkpoint
Clear points
Why this many, and where — the rules and their sources
On the ground
Occupying each point
Sources
Points for Trimble Access (CSV)
Points (KML)
Points (GeoJSON)
The CSV is Name, Latitude, Longitude, Height, Code in decimal degrees — import it into the Trimble Access job as a points file and stake each point out. Height is left at 0: the positions are where to go, not what to record.
4 Check the survey Export the surveyed points from Trimble Access as a comma-delimited file — with H.Prec and V.Prec if the export offers them — and open it here. Names are matched to the plan; GCP… are control, CHK… are checkpoints.
Units in the file
Columns, when there is no header row
Grid is UTM zone
Open the survey file…
Close it
5 Check the accuracy Measure each checkpoint in the finished product — in the point cloud or on the orthomosaic — and open those positions as a point file with the same names, in the same system and units as the survey. Or open the checkpoint residual table the processing software wrote (Error X, Error Y, Error Z).
Open the product's points…
Open a residual table…
2 Choose the job
LiDAR
Photogrammetry
Job type
Ground cover
Pulses reaching the ground (%)
Reapply
Why these settings — requirement, working, sources
What the standard requires
How the settings were worked out
What it needs beyond the flight
Sources
3 Choose the equipment
Drone
LiDAR unit Lens
What is unverified, and how to check it
Flight settings
Height above ground (m)
Speed (m/s)
Side overlap (%)
Forward overlap (%)
Shutter you will set
Corridor width (m)
Cut the route every (m)
Passes along a corridor
Flying the corridor
You can see the aircraft to (m)
GNSS base every (mi)
Pulse rate
Scan mode
Returns
Line direction
Auto — along the longest edge
Set a heading
Heading (° from north)
Grids over each area
Each grid is flown as its own route and exported as its own file. Extra grids are spread evenly in heading from the first.
Battery & field day
Land with battery at (%)
Site elevation (ft)
Usable minutes per battery set
Battery swap on the ground (min)
Move to the next launch point (min)
Flying hours per field day
Export routes
4 Save and export Project name
Save project
Open or start another…
Download a copy
Estimate (CSV)
Route (KMZ)
Flight plan (print)
Flight paths (KML)
Flight paths (GeoJSON)
Areas (GeoJSON)
Parcel boundaries (KML)
Parcel boundaries (GeoJSON)
(USGS 3DEP — United States, needs a connection)
Flight plan is one page per area — lines drawn to scale, time, battery sets, route files — that opens in any browser and prints to PDF. Flight paths are the same lines for Google Earth (KML) or a GIS (GeoJSON); they are for looking at, not for flying. Parcel boundaries are every lot the areas touch, with the assessor's fields, from the county or state parcel service.
Routes follow the ground. With the box ticked, each route is exported with terrain follow on and the ground under it packed inside the file, so it flies at its height above the ground , not above the takeoff point. The ground is USGS bare earth at about 30 m: trees, buildings, towers and wires are not in it . Before it flies, open the route in Pilot 2 and check that the height profile follows the ground rather than sitting flat — flat means the terrain did not load.
Without terrain — the box unticked, no connection, or a site outside the United States — a route holds its height above the takeoff point. The app says so when it happens.
File names and folders
Organization prefix (optional)
Projects are kept in Open folder · Change…
Offline maps
Save this view for offline
Install as an app
Delete saved maps
State, county and tribal-land boundaries are built in and need no connection. Bulk saving uses public-domain US government maps (USGS, NAIP, Census). Any other map source offered is kept only as you view it — its terms do not allow bulk downloads.
Runs entirely on this computer — no account, no API key, no AI. Map tiles, place search, elevation lookup and directions use the network when there is one.
Before you use Swathwise