Two maps sit side by side in one frame. Drag the round handle left and right to wipe
between them — same ground, same scale, so every tree stays exactly where it is as you
wipe and you are always comparing like with like.
Pick what goes in each side with the two dropdowns below. Every map made for this block is
also listed in the table at the bottom, with ◀ L and R ▶ buttons to
drop it straight into either side.
Scroll or pinch to zoomDrag to panDouble-click to re-frame the block
LEFT PANE
RIGHT PANE
N ↑
▾
Opens on the whole mapped block — scroll to zoom right in on individual trees.
All maps in this set
Every map produced from the flight. Use the ◀ L and R ▶ buttons to drop any map into either side of the viewer above — the true-color ortho against any of the derived maps is usually the most telling pairing.
About these files. The JPEG links download a full-resolution copy of each map — 2 to 3 MB apiece, the same images shown above at full detail. For a close look you may not need them at all: the viewer above zooms and pans to the same resolution.
GeoTIFFs are not posted here. Those are the georeferenced originals for QGIS or ArcGIS, and they run from hundreds of megabytes to several gigabytes apiece — too large to leave sitting on a web page. Ask for whichever you need and we will send a direct link.
ID
Date
Flight
Type
Product
GSD
View (JPEG)
GIS (GeoTIFF)
Load
Photos and video
Set
What is in it
Files
Open
What the terms mean
Plain definitions for the words used on this page.
Orthomosaic (ortho)
Hundreds of overlapping photos stitched into a single image and geometrically corrected, so
every point is shown as if viewed from directly overhead. A distance measured on it is a
true distance on the ground — unlike an ordinary aerial photo, where only the center
is looking straight down.
GSD
Ground sample distance — how much ground one pixel covers. These maps were analyzed
at 3 cm/px, so a single pixel is roughly the size of one blossom cluster. That is the
resolution that makes scoring a single tree possible rather than a whole row.
Canopy extent
Which pixels are tree and which are orchard floor. Worked out from the height of the
surface rather than its color, so mown grass, weeds and drive lanes are excluded even when
they are every bit as green as the canopy. Everything else here is measured inside this
boundary only, which is why bare ground between trees cannot dilute a tree's score.
Blossom density
For each mapped unit, the share of its own canopy that is in bloom — not a
count of flowers, and not a share of the block. A small unit in heavy bloom and a large one
in heavy bloom score the same, which is what makes the number comparable across the
orchard. Sorted into six classes held fixed at 3, 12, 25, 40, 60 and 80 percent.
Unit
What gets scored. Where crowns stand apart, a unit is one tree. Where a row has grown
together into continuous canopy, the imagery cannot see a boundary that is not there, so a
unit is a segment of row instead — which is why some shapes on the map are
round and others run along the row.
RTK
A satellite-positioning correction that places each photo within a couple of centimeters of
its true location. It is what allows maps flown weeks apart to be laid over one another and
compared pixel for pixel.
Wipe
Dragging the round handle across the frame to reveal one map from beneath another. Both are
locked to the same ground and the same scale, so a tree sits in exactly the same place on
both sides — only what is being shown about it changes.
Want this for your farm?
FirSight gives your farm its own private page like this one: your blocks, your counts, your sale sizes.