Instructions
How Cover Mapper is used, and how each of its numbers is worked out.
Projects and members · Plots · Visits and scans · Lining up · Analysis · Plants · Patches · Species and records · Related tables · Rare species and public plots · Exports · Requirements
Projects and members
A project holds plots, their visits and scans, the project's tables, and its species records. It is made on the Projects page, which needs a storage plan; its storage counts against the owner's plan.
Members join through an invitation link made on the project's Members tab. The link carries a role and lasts the number of days set; whoever opens it signed in joins.
- Owner: everything, including members, settings and deleting the project.
- Editor: adds and changes plots, visits, scans, analyses, rows and records.
- Viewer: reads the project and exports what they see.
The owner also decides which members see rare species (see Rare species and public plots).
The Settings tab sets the height classes (edges in metres, lowest first; the first edge is the vegetation threshold) and the grid cell of the analysis. Visits are compared on the same grid, so a change of cell starts a new series.
Plots
A plot is added on the project page: its name and code, its centre (typed, or placed on the map), its shape and size, and who sees it. A circular plot has a radius; a rectangular plot has a width, a length and the bearing of its length from true north.
The plot's frame is metres east, north and up about the centre. The first visit with a scan sets it from the plot's markers, as described under Lining up.
Markers are permanent: rebar, a painted stake, a monument. A marker that is still there years later lines up every later visit.
Visits and scans
A visit is added on the plot's page with its date, observer and notes. It also records whether crown widths of plants are recorded on that visit.
Its scan is added on the visit's page. Accepted formats:
- PLY from a phone's LiDAR (Stem Mapper's Save point cloud, or another scanning app);
- LAS or LAZ from a terrestrial scanner or a drone;
- a text file of x y z.
The file is read in the browser and thinned to one point per cell of the size chosen (1 cm by default). It is then tiled and stored.
Phone PLY files have y up; scanner and lidar files have z up. The page sets the up axis from the file and it can be changed. Metres per file unit is read from a LAS file's coordinate system.
Scanning a plot with a phone:
- Walk the plot slowly, holding the phone about a metre from the vegetation, and include the markers and the ground round them.
- Fine foliage seen against the sky and grass under about 10 to 15 cm are often missed by a phone's LiDAR.
- Scans in poor light are weaker.
Lining up
Each scan is in its own frame. Lining it up turns it about the vertical and moves it onto the plot's frame, so the grids of every visit match cell for cell. Phone scans and lidar files are level, so four numbers do it: a turn and three moves.
The first visit
The first visit with a scan sets the plot's frame. Pick the centre marker and a second marker in the scan (click the top of each stake), and type the compass bearing from the centre to the second marker, in degrees from true north.
The centre becomes the origin, and its ground, read from a plane fitted round the stake, becomes height 0. The bearing turns the scan to north.
More markers are added on any lined-up visit with Add a marker; they are saved to the plot with their positions.
Later visits
Pick each marker you can see in the scan, two or more, and fit. The fit is the least-squares turn and move from the markers' positions in the scan to their positions in the plot.
The error of each marker and their root mean square are shown and kept with the visit. An error over a few centimetres usually means a marker was picked in the wrong place.
Georeferenced scans
A LAS or LAZ file in a known coordinate system can be lined up by its coordinates. The first such scan sets the plot's height datum at the ground of the plot centre.
Refining
Refine tightens a lined-up visit against the plot's baseline visit, or the latest earlier lined-up visit. It uses the lowest point of each 10 cm cell of the scan and of each 5 cm cell of the reference: the ground, rocks, stumps and banks, which do not grow.
Each round pairs each point with the nearest reference point. It keeps the closest 80 % of pairs, so vegetation that grew in between drops out, and solves for the turn and move that bring each point onto the reference surface there.
Flat ground fixes the height well and the horizontal position little; rocks, stumps and banks fix the rest. The surface distance before and after is shown, and the refinement is kept only if you keep it.
Analysis
Analyse the scan reads every stored point, carries it into the plot's frame and works on the plot's grid. The cell is 5 cm unless the project sets another.
The ground
The ground comes from this scan, or from the plot's baseline visit. The baseline is a visit marked as bare ground, such as the first visit after a fire; its ground is then used for every later visit, under vegetation the later scans cannot see through.
From a scan, the ground is found in four steps:
- A 50 cm grid takes the third lowest point of each cell.
- Cells more than 20 cm above the median of their neighbours (vegetation the scan saw no ground under), or well below it, are dropped, in three passes. Empty and dropped cells are filled from their neighbours.
- Each cell is refined to the mean of the points from 6 cm below that surface to 2 cm above it, plus what the cell's slope adds across its width. That mean falls at the cell's middle.
- The analysis grid is interpolated from the 50 cm grid.
The analysis reports the share of scanned 50 cm cells where ground was seen.
The top of the vegetation
The top of each cell is its highest point over the ground with another point within 5 cm below it, in the cell or beside it. A lone point (a stray reflection at an edge) is skipped; a thin leader carrying a few points is kept.
A cell with points is scanned. The share of the plot scanned is reported, and the cover figures are shares of the scanned area.
The figures
- Vegetation cover
- The share of the scanned area whose top stands above the first height class edge (5 cm by default).
- Top in each height class
- The share of the scanned area whose top falls in each class: the cover of the vegetation as seen from above.
- Columns with returns in each band
- The share of the scanned area with any point in each height band, whether or not the band is the top. It shows the layers under a canopy, as far as the scan reached under it. Stray single points are left out.
- Mean, 95th percentile and maximum height
- Of the tops of the vegetated cells.
- Volume under the surface
- The sum of the tops over the scanned area, in cubic metres per square metre (equal to the mean top height).
- Occupied voxels
- The volume of the cubes of one cell on a side that hold a point above the threshold, per square metre. Dense vegetation fills more of the space under its top than sparse vegetation does.
- Change since the last visit
- The mean difference in top height from the latest earlier analysed visit on the same grid, and the area that grew or was lowered by more than 10 cm.
The figures are saved as the visit's row of the Lidar summary table, and the grids are stored with the visit. The plot's map shows a visit's height grid or its change grid.
Rocks, stumps, logs and marker stakes stand above the ground as vegetation does and count as such. Their share is read from the bare baseline visit.
Plants
The plant tool
Measure a plant uses the seedling tool of Stem Mapper. Click the base of the plant, where its stem meets the ground.
- Ground: at the base, the low end of the points within 25 cm. Round it, a plane is fitted to the lowest point of each 10 cm cell within 60 cm, so a slope is not read as a plant.
- The plant: the points connected to the base through occupied 5 cm cells.
- Height: to the top, which is the highest point with another within 5 cm below it, in a cone over the base. The tool climbs through gaps of up to 15 cm, so foliage beyond a bare twig is reached.
- Crown width: from the foliage above the lowest fifth of the height. It is the mean of the widest extent and the extent at right angles to it, each the span of the middle 80 % of the foliage points across it.
- A crown seen from one side only: the widest extent stands alone, and this is recorded.
The plant is saved to the Plants table with its tag, species, height, crown width, method and position.
Crown widths
A visit is set to record crown widths or not when it is added, and this can be changed on the visit's page. On a grassy plot, grass at the height of a plant's foliage widens its crown, and crowns are better left unrecorded.
With crowns on, a single plant's crown width can be rejected before it is saved. The Plants table records each crown as measured, rejected, not recorded, seen from one side only, or not resolved.
Finding plants
Find plants looks on the height grid for tops at least the height asked for (30 cm by default). A top must:
- be higher than every cell within a quarter of its height (10 cm to 1.5 m);
- stand out of what is round it: along at least six of eight directions the surface drops by a quarter of its height, at least 10 cm, within 0.6 of its height.
The ripples of a sward and the edge of a flat patch are therefore not plants.
Each top's crown grows from the top over its upper part (above 60 % of its height), and below that while the surface keeps falling away. Its width is the diameter of a circle of its area.
Two tops of nearly the same height joined by a level surface (a stump, a clipped shrub) are one plant. The plot's marker stakes are left out. Rocks and stumps can still be found as plants; untick them before saving.
Plants over the years
A plant found or measured on a visit is matched to the nearest plant of the latest earlier visit with plants, within half the larger crown width (30 cm to 1.5 m). It takes that plant's tag and species, and its growth since then is shown. A plant with no match gets the next free tag.
Patches
Find patches outlines the connected areas of the plot whose top lies within a height band, of at least the area asked for. Gaps of one cell are closed first.
Each patch has its area, mean and maximum height, and the mean colour of its top when the scan has colour. Holes inside a patch are not outlined.
Select a patch to record its species: the record is a polygon on the plot, with the cover typed and the patch's measurements.
Species and records
A species box offers the species of the list and the project's own species as you type. A name not on either is added as a species of the project, with its common name, life form, status, and whether it is rare.
The project's species are listed on its Species tab. Rare can be ticked there, and species of the list can be added to those hidden like rare species.
On the plot's Species records tab, choose the species, the date, and the cover, count and notes. Then draw a point (a plant), a line (a band along a road or a creek) or a polygon (a patch) on the map.
- Points snap to the vertices of other records.
- Change the records on the map moves vertices, adds them at midpoints, and deletes vertices or whole records; every change can be undone.
- A record can be hidden from the public by its observer.
Records are coloured by status: invasive, introduced, native, other.
Related tables
Every plot carries the project's tables: one row per observation, tied to the plot and, usually, to a visit. The built-in tables are:
- Species cover: species, cover, height, phenology, notes.
- Plants: written by the plant tool and Find plants, and by hand.
- Lidar summary: written by each visit's analysis.
On the project's Tables tab, fields of the project's own are added to any table. A whole table is added for a protocol (line-point intercept, quadrat cover, photo points, browse damage).
Field types are text, number, whole number, date, choice, yes or no, and species. Built-in fields stay, though their labels can change.
Rows are added and edited on the plot's page; a row can be hidden from the public.
Rare species and public plots
A plot is private to the project's members, or public, open to anyone without an account.
A row or record is hidden when its species is rare (on the list's rare ranks, or marked rare by the project) or when its observer hid it. A hidden row or record is shown only to:
- the project's owner;
- members allowed to see rare species;
- the observer.
Everyone else, the public included, sees the rest of the plot without it: its tables, its map, the labels on its scan and its exports.
On the map of public plots, a rare species on a public plot appears only as the 0.2 degree square it lies in (about 22 by 18 km), with no plot named.
Exports
A plot's page and a project's page export what you can see:
- each table as CSV, with the plot and the visit date;
- the species records as CSV, with their geometry as WKT;
- a GeoPackage holding the plot boundaries, the records in point, line and polygon layers, and every table linked to the plots by plot_id.
QGIS shows the links between the plots and the tables. In ArcGIS Pro the layers and tables open, and the tables are related to the plots on plot_id.
Requirements
A current browser with WebGL (Chrome, Edge, Firefox or Safari). A scan is read and analysed in the browser; a plot's scan of a few million points needs a computer with 8 GB of memory or more.
The base maps are from the United States Geological Survey's National Map.