Skip to content
Lake and pond expertiseSoftware, monitoring, and consulting
Learning CenterField methods chapterAquatic Vegetation Survey, Identification, and Mapping
Field methods chapter · Aquatic vegetation

Aquatic Vegetation Survey, Identification, and Mapping

A defensible lake and reservoir macrophyte survey guide connecting objectives, survey-unit design, field and mapping methods, taxonomic confidence, repeatability, safety, spread prevention, and raw evidence.

For
Lake managers, aquatic plant survey crews, consultants, reservoir operators, natural-resource agencies, taxonomists, GIS analysts, and quality-assurance reviewers
Reading time
25 minutes
Reviewed
Next review
Direct answer

What to do first

Start by naming the population and decision the survey must describe, then freeze the survey frame, units, stage or depth datum, season, method, effort, taxonomic authority, quality controls, and rules for inaccessible or non-detect sites. Point-intercept, transect or quadrat, rake, visual, hydroacoustic, remote-sensing, and biomass methods answer different questions; they are not interchangeable. Preserve actual locations, depths, effort, observations, photographs, vouchers, identification confidence, map lineage, exclusions, and safety or decontamination exceptions. Report a taxon as not detected within the sampled frame and method unless the design supports a broader claim, and never turn one survey score or suspected identification into an automatic treatment decision.

Use this guide to
  • Choose a survey frame and method that match a named lake-management or ecological question.
  • Record survey depth, stage, datum, effort, non-detects, inaccessibility, and observation method without overstating absence.
  • Separate occurrence, cover, categorical rake abundance, acoustic canopy metrics, and harvested biomass.
  • Preserve photographs and voucher specimens with identification confidence, determiner history, permits, and taxonomic escalation.
  • Produce repeatable spatial data and a raw evidence package suitable for QA review, future comparison, and bounded management planning.
Continue the work

Field route

Use an authored handoff; this is not an automatic recommendation or approval.

Define the objective, target population, and survey unit

A vegetation survey becomes interpretable only when the team states what population, place, period, and decision its observations are intended to represent.

Write the primary objective before choosing points or equipment. A whole-lake community inventory, early detection search, delineation of a suspected bed, maximum-depth-of-colonization study, habitat assessment, navigation-zone map, and before/after management evaluation require different frames, effort, replication, and inference. Preserve secondary observations, but do not redesign the primary objective after seeing favorable results.

Define the target population and included plant groups. State whether the frame includes open water, the mapped littoral area, a stage-bounded depth zone, shoreline sectors, management and comparison areas, habitat strata, or a suspected occurrence polygon. Define how the project treats submerged vascular plants, rooted floating-leaved plants, free-floating plants, emergent plants, bryophytes, macroalgae, filamentous algae, and terrestrial or wetland-edge taxa. The word macrophyte does not guarantee identical inclusion rules across programs.

Name the observational unit: point, toss, rake pull, subsampling area, quadrat, transect segment, acoustic ping or track segment, image pixel, mapped polygon, harvested plot, or another controlled unit. Also name the reporting unit and intended estimator. Multiple rakes around one point may be subsamples within one unit rather than independent points; treating them as independent can overstate precision.

Objective-to-design questions to resolve before field layout
ObjectiveDesign questionBounded output
Community inventory or statusWhat lake area, depth zone, habitats, season, and plant groups form the sampling frame?Occurrence, richness, or method-defined abundance estimates for the stated frame and period.
Early detectionWhich introduction pathways and suitable habitats receive targeted effort, and how is search effort recorded?Detected or not detected under a named search design, never proof of lake-wide absence.
Bed or treatment-area delineationWhat defines the boundary, minimum mapping unit, positional tolerance, interior confirmation, and comparison area?A dated method-defined polygon with uncertainty and field-verification lineage.
Trend or effectivenessWhich baseline, repeat season, reference or comparison, endpoint, adverse endpoint, and analysis were fixed before action?Comparable estimates with method changes, confounders, and inconclusive outcomes visible.
Habitat or depth relationWhich stage datum, bathymetry, substrate, light or clarity, shoreline class, and depth reference accompany vegetation?Associations within the observed range, not an automatic causal or treatment claim.

Sources: [1], [2], [10]

Choose the method by the quantity it can observe

Intercept, plot, rake, visual, acoustic, imagery, and biomass methods measure different features and create different detection and comparability limits.

Match each objective to an observable quantity and estimator before selecting gear. Point-intercept observations are efficient for occurrence or method-defined relative abundance across a defined frame. Transects and quadrats can describe gradients, within-plot cover, or smaller comparison areas. Rakes retrieve taxa and support a controlled categorical index but sample a method-dependent footprint. Visual observations favor visible life forms and clear water. Harvested plots can estimate dry or wet biomass only through a controlled area, collection, sorting, and processing method.

Hydroacoustics can extend coverage of submerged-vegetation height, canopy, or biovolume-like signatures when configured and validated for the project. Aerial, satellite, or uncrewed imagery can map optically visible classes at the sensor's spatial and temporal scale. Neither technology automatically identifies species, sees through all depths or turbidity, or replaces field reference data. Combining methods is often defensible, but each layer must retain its own unit, detection process, date, and uncertainty.

Method families and common inference limits
Method familyUseful observationDo not silently infer
Point-interceptOccurrence or a controlled categorical observation at predefined points within a stated frame.Continuous bed boundaries, percent cover, biomass, or absence between points.
Transect or quadratChange along a gradient, plot-level cover, density, or composition under a fixed layout.Whole-lake condition unless the design and weighting support it.
Rake, toss, or grapnelRetrieved taxa and method-specific categorical load within an uncertain or controlled contact footprint.Absolute cover, biomass, rooted density, or equal capture probability among growth forms.
Visual, video, wading, or diving observationVisible cover, boundaries, structure, and taxa under documented viewing conditions and effort.Detection of hidden, sparse, deep, turbid, dormant, or look-alike taxa.
HydroacousticGeoreferenced acoustic structure such as bottom, canopy height, or vegetation-like return under a validated processing workflow.Species identity or transferable classification without local field verification.
Optical remote sensingSpectral or image classes and mapped surface or submerged features visible to the platform and conditions.Fine taxa, plants below optical detection, or an error-free boundary without accuracy assessment.
Harvested biomassMass per controlled collection area and processing basis.Cover, occurrence, or lake-wide biomass without a suitable sampling and scaling design.

Sources: [1], [2], [4], [5]

Freeze the frame, coordinates, depth datum, and effort

Repeatability depends on preserving where the survey could have sampled, where it actually sampled, how depth relates to water level, and how much effort each unit received.

Create and version the survey frame before mobilization. Preserve shoreline or basin source, bathymetry date, coordinate reference system, horizontal units, stage condition, exclusions, strata, randomization or systematic-origin rule, and point or transect generation code. Grid spacing and sample count must follow the objective, expected pattern, desired precision, positioning capability, resources, and approved analysis, not a universal lake-size table.

At each unit, retain planned and actual coordinates, positioning method and status, date and unambiguous time, observed water depth, depth reference, water-surface elevation or stage source when available, bottom or substrate notes, and the relation to the current shoreline. A depth value without units and datum cannot reliably be compared after drawdown, flooding, sediment change, or a revised bathymetric surface.

Define effort in method-relevant terms: attempted and completed points, subsamples, tosses, pulls, quadrats, transect length, search time, observer or diver time, acoustic track length and coverage, image footprint, ground-truth samples, and taxonomic processing effort. Preserve deviations and the reason a planned unit moved, was partly observed, could not be raked, fell on land, or was inaccessible. Never convert a navigation miss, unsafe unit, or equipment failure into a valid zero.

  • Objective, target population, frame version, strata, selection rule, and estimator are frozen.
  • Coordinate reference system, units, datum, planned locations, and positional-quality field are defined.
  • Depth reference, stage or water-surface source, bathymetry version, and land or dewatered-unit rule are defined.
  • Expected effort and completion rules are stated for every method and subsample.
  • Moved, inaccessible, unsafe, not-rakeable, and not-observed units remain distinguishable from plant non-detects.
  • Analysis denominators and weights are derived from the design, not chosen after viewing the vegetation pattern.

Sources: [1], [2], [3], [10]

Run point-intercept work as a controlled probability or systematic design

Point-intercept data are strongest when locations are fixed independently of field preference and each point receives the same defined observation protocol or a documented exception.

Preload planned identifiers and coordinates, then navigate without shifting toward visible vegetation, convenient water, or an expected bed. At the actual point, verify location, depth and stage context, unit status, observation order, subsampling geometry, rake or visual procedure, and effort. Record all included life forms using the same detection rules. A plant observed near the point but outside the defined unit can be retained as an incidental or additional observation without converting it into an intercept detection.

If a defined point cannot be reached or the protocol cannot be executed, use the project's explicit status and preserve the reason and boat-stop or nearest-safe coordinates. Do not substitute a nearby vegetated location unless the movement rule authorizes it and keeps the original and replacement relationship. Preserve points that are land, dry, outside the current waterline, too deep for the approved device, physically obstructed, or unsafe; these conditions may be analytically important.

Calculate occurrence and community summaries using the predeclared eligible denominator, strata, weights, and taxonomic resolution. Report both the sampling frame and the completed-point pattern. A frequency of occurrence is a design- and method-specific proportion of eligible sampled units with detection; it is not percent areal cover and cannot be compared directly to another survey with different point selection, detection method, season, or denominator.

  1. Navigate to the selected unit

    Confirm planned ID, actual position, positional status, water or land status, depth, and stage context before observing vegetation.

  2. Apply the frozen observation sequence

    Use the same project-defined visual, rake, subsample, life-form, effort, and ancillary-observation rules at each eligible point.

  3. Code detection and unit status separately

    Keep observed, not detected, not sampled, inaccessible, unsafe, unable to apply the method, and incidental detection as distinct states.

  4. Preserve the design denominator

    Apply declared inclusion, stratum, and weighting rules and report departures rather than removing difficult points after collection.

Sources: [1], [2], [3]

Use transects, quadrats, and boundary mapping for explicit spatial questions

Plot and line methods can resolve gradients and treatment-scale patterns, but their placement, dimensions, observation rules, and boundary criteria must be controlled.

Orient transects to the process of interest, for example a shoreline-to-depth gradient, exposure gradient, management edge, or reference comparison, and define their origin, bearing or endpoints, segment rule, plot or quadrat dimensions, spacing, and relocation method. If transects are intentionally placed in known beds, describe them as targeted rather than representative of the whole lake. Permanent and newly randomized transects answer different trend questions.

Within each quadrat or segment, define whether the record is presence, rooted stem density, visual cover, canopy cover, occurrence in subquadrats, harvested biomass, or another quantity. Calibrate cover estimation and define whether layers may sum above a full ground area. Keep species cover, total vegetation cover, exposed substrate, and floating or overhanging material distinct. A rake score collected beside a quadrat is supporting evidence, not automatically a quadrat-cover estimate.

For bed delineation, define the target class, boundary observation rule, direction and spacing of boundary searches, interior confirmation, gaps, islands, minimum mapping unit, positional tolerance, water level, imagery or acoustic support, and confidence class. Preserve raw boundary fixes and tracklogs rather than retaining only a smoothed polygon. A map edge is a method-defined interpretation, not a permanent biological line.

  • Transect placement is random, systematic, permanent, targeted, or judgmental by explicit design.
  • Origin, endpoints, bearing, dimensions, segments, plots, and relocation evidence are recoverable.
  • Cover, occurrence, stem density, rake index, and biomass fields have separate operational definitions.
  • Boundary detection, gap handling, interior checks, positional tolerance, and confidence class are defined.
  • Raw fixes, tracks, photos, depth, stage, and excluded or inaccessible areas remain attached to the derived polygon.

Sources: [1], [2], [10]

Treat hydroacoustic and remote maps as calibrated models

Broad-coverage technology expands observation, but every vegetation layer remains conditional on sensor configuration, water conditions, processing, training data, and independent validation.

For hydroacoustics, preserve transducer and positioning configuration, frequency or channel used, draft and offsets, calibration or verification evidence, ping and navigation settings, vessel speed control, track plan, depth and bottom-detection logic, vegetation-detection settings, raw acoustic files, software and version, analyst steps, exclusions, and field-reference samples. Separate measured or derived bottom depth, vegetation presence, canopy height, percent-volume-inhabited or similar products according to their exact algorithm. Do not label an acoustic return as a species without independent evidence supporting that classification.

For satellite, aircraft, drone, or surface imagery, retain platform and sensor, acquisition time, spatial and spectral resolution, georeferencing, radiometric and atmospheric processing, sun glint, cloud and shadow masks, water level, clarity, wave and wind condition, depth or optical-bottom limitation, training data, classifier and parameters, minimum mapping unit, and raw or source imagery rights. Emergent, floating, canopy-forming, and deeply submerged plants have different visibility.

Design field reference and accuracy assessment independently enough to evaluate omission and commission error. Preserve reference-point selection, class definitions, confusion matrix or other approved accuracy summaries, and uncertainty spatially where possible. A model tuned for one date or lake may not transfer when water color, turbidity, stage, species mix, bottom reflectance, canopy architecture, sensor, or processing changes.

Minimum lineage for a derived vegetation map
LayerEvidence to retainPrimary limitation to report
Acoustic track and derived canopyRaw acoustic and navigation files, offsets, calibration, track coverage, settings, processing version, exclusions, and reference observations.Only the insonified track and validated depth, bottom, canopy, and plant structures; species identity is usually unresolved.
Optical image classificationSource imagery, acquisition conditions, corrections, masks, training features, classifier, resolution, and field references.Optically visible classes under that date's depth, clarity, surface, atmosphere, and pixel-mixing conditions.
Mapped polygon or rasterRaw points or tracks, class schema, interpolation or segmentation, smoothing, minimum unit, uncertainty, and accuracy assessment.A model-derived boundary at a declared scale, not a direct census of every plant.

Sources: [4], [5], [10]

Control rake and visual observations, and never overstate absence

Rake retrieval and visual detection depend on gear, action, footprint, observer, water conditions, plant form, and effort; a zero is meaningful only when those controls were actually applied.

Freeze the rake or grapnel construction, dimensions and markings, handle or line, toss or placement procedure, contact and retrieval path, replicate or subsample layout, vegetation-folding or scoring rule, observation order, and cleaning step in the project method. Record actual gear ID, operators, completed effort, depth, substrate, snagging, sediment, loss of contact, retrieval failure, and fragments. A category from one rake design or technique is not interchangeable with another.

Define the visual search area, viewing platform, observation duration or path, observer, water clarity and surface condition, viewing aid, life forms, and rule for plants outside the unit. Visual detection can complement rake retrieval for emergent, floating-leaved, free-floating, sparse, or fragile taxa, but it cannot establish equal detectability. Underwater video, wading, snorkeling, and diving each require their own field of view, effort, position, and safety record.

Use distinct states for detected by visual, detected by rake, incidental detection, not detected after valid method effort, no submerged plants detected, no vegetation of included life forms detected, inaccessible, unsafe, on land, dewatered, outside frame, and unable to apply the method. Report "not detected in the sampled units with this method and effort" unless detection probability and design support a broader statement. Rare, small, dormant, fragmented, deep, hidden, or phenologically incomplete taxa can be missed.

Observation states that must not collapse into one zero
StateWhat it meansAnalysis warning
DetectedThe taxon or operational group met the stated visual, retrieval, voucher, or mapped-class rule.Retain detection method and confidence; methods have unequal selectivity.
Valid non-detectThe defined method and effort were completed in an eligible unit without detection.This is not proof of absence outside the unit, season, depth, or method.
Method-limitedThe unit was reached but depth, substrate, current, obstruction, visibility, gear, or another condition prevented valid observation.Do not include as a non-detect unless the analysis plan explicitly and defensibly models it.
Not sampledThe unit was inaccessible, unsafe, outside current water, missing, or otherwise not observed.Preserve the reason and spatial pattern; missingness may be nonrandom.
Incidental or outside unitA taxon was noticed outside the defined observation footprint or effort.Useful for inventory or follow-up, but not automatically an intercept detection.

Sources: [2], [1], [3]

Keep occurrence, cover, rake abundance, and biomass separate

These quantities describe different aspects of vegetation and cannot be converted into one another without a validated, method-specific relationship.

Occurrence records whether a taxon met the detection rule in an observational unit. Frequency of occurrence divides detected eligible units by the predeclared denominator, with design weights when required. Richness counts taxa at the chosen resolution and effort. Neither metric describes how much bottom or water column the plants occupy at each point.

Cover is the projected proportion of a defined horizontal area occupied by the target layer under a stated viewing and overlap rule. Canopy cover, bottom cover, species cover, total vegetation cover, emergent cover, and image-class area are not synonyms. Observer estimates require training and calibration; imagery cover depends on pixel, segmentation, and classification rules.

Rake fullness, plant density score, or relative abundance is an ordinal or categorical index tied to exact gear and retrieval procedure. Preserve the original category rather than treating it as a continuous mass. Biomass requires a known collection footprint and specified wet or dry processing, taxon sorting, inclusion of roots or fragments, drying or draining endpoint, balance checks, and scaling rule. A locally validated conversion model remains a model with stated applicability, not a universal equation.

  • Every metric has an operational definition, unit, eligible denominator, spatial frame, and season.
  • Observed, incidental, unknown, non-detect, and not-sampled states remain distinct before calculation.
  • Species and life-form resolution are consistent or changes are crosswalked without fabricating precision.
  • Rake categories remain tied to gear, effort, retrieval, and scoring version.
  • Cover records area, layer, overlap, observer or classifier, and viewing conditions.
  • Biomass records footprint, plant components, wet or dry basis, processing, balance, and scaling design.

Sources: [1], [2], [3]

Separate taxonomy, origin, invasiveness, and identification confidence

A scientific name, geographic origin, legal status, and evidence of harm are separate claims that require separate authorities and dates.

Use an adopted taxonomic reference and preserve the scientific name with authorship or taxon identifier when required, accepted name, field code, synonyms encountered, common name, resolution reached, reference version, determiner, determination date, and confidence. The USDA PLANTS Database provides standardized names, symbols, distribution, and broad native-status information, but a project's regional flora, herbarium, state list, Tribal authority, or specialist may be needed for local resolution and current status.

Native is relative to a particular ecosystem or geographic context. Nonnative, introduced, alien, or exotic describes origin outside that context; it does not automatically mean invasive. Under the federal definition, invasive status includes nonnative origin and actual or likely harm. Noxious weed, prohibited species, regulated invasive, watch-list species, nuisance plant, and undesirable plant are program or legal terms that can differ by jurisdiction and date. Cite the controlling list instead of assigning a label from appearance or abundance.

Record the finest defensible identification, including genus, species complex, hybrid suspicion, or unknown taxon. Do not force a species code to eliminate an unknown. Closely related aquatic plants, sterile material, juvenile shoots, hybrids, and environmentally variable forms may require flowers, fruits, winter buds, stem or leaf anatomy, microscopy, chromosome or genetic work, or specialist review. A field guess must remain provisional until the approved confirmation is complete.

Claims to keep separate in the species table
ClaimEvidence fieldDo not infer
Taxonomic identityName or unknown code, reference, diagnostic evidence, determiner, date, confidence, voucher or photo link.Origin, legal status, harm, or management need from the name alone.
Native or nonnative statusNamed ecosystem or jurisdiction, authoritative source, source date, and any population or lineage caveat.Invasiveness or treatment eligibility merely because a taxon is nonnative.
Invasive or regulated statusApplicable definition, jurisdiction or program, controlling list, effective date, and verified taxon resolution.Universal status across state, Tribal, federal, or local boundaries.
Nuisance or use conflictObserved location, extent, use, timing, impact evidence, reporter, and decision authority.Species diagnosis, ecological harm, or permission to control.

Sources: [6], [7], [2]

Build a traceable photo, voucher, and specimen chain

A consequential identification should be reviewable from georeferenced field evidence through specimen preparation, determination, repository, and any later taxonomic revision.

Assign an observation and specimen identifier before collection and link it to waterbody, survey unit, coordinates and datum, depth and stage context, habitat, date and unambiguous time, collector, field name, confidence, and collection authority. Photograph the plant in habitat when safe, then capture the full specimen, branching and leaf arrangement, attachment or roots when authorized, stem cross-section or other diagnostic structures, flowers, fruits or winter buds when present, and a scale and label. Preserve original image files and metadata; edited crops are derivatives.

Follow the receiving taxonomist or herbarium's instructions for the amount, life stages, wet holding, pressing, preservative, labels, duplicate material, and shipping. Maintain an attributable transfer record from collector to field custodian, taxonomist, laboratory, or repository, including dates, condition, specimen splits, destructive analysis, returned or retained material, determination history, accession, and disposal. Keep provisional field names and later determinations as a versioned history rather than overwriting them.

Obtain permission and required collecting, protected-species, landowner, park, Tribal, interstate, federal, or invasive-species transport authority before removing or moving material. Permit conditions can retain government ownership or require an approved repository and transfer agreement. Minimize collection and fragment escape; never transport a suspected prohibited species casually in an open boat, livewell, or unsealed field container.

  • Observation, photo, specimen, survey unit, and map feature IDs are linked without relying on filenames alone.
  • Photos show habitat, overall habit, diagnostic details, scale, and label while preserving original files and metadata.
  • Specimen label retains locality, coordinates and datum, depth or habitat, date, collector, field determination, and permit or authority reference.
  • Field confidence, taxonomic determiner, determination date, reference, revisions, and unresolved tests are versioned.
  • Transfers, splits, destructive work, accession, storage, return, or authorized disposal remain attributable.
  • Collection and transport comply with the specific landowner, jurisdiction, protected-species, and invasive-species rules.

Sources: [2], [8], [6]

Design around phenology and prove repeatability

Seasonal detectability and observer or method variability can look like ecological change unless timing, proficiency, duplicate work, and method versions are controlled.

Schedule the survey for the objective and expected phenology, then retain actual growing degree, weather, stage, clarity, recent disturbance, senescence, flowering or fruiting, treatment, drawdown, and other seasonal context available to the project. A single peak-season survey may characterize a community well yet miss early, late, ephemeral, sterile, or overwintering forms. Repeat surveys should target comparable phenological windows, not merely the same calendar date.

Before production work, train crews with the exact protocol, field forms, plant list, unknown codes, gear, cover or rake categories, photography, vouchers, GPS, depth reference, and safety controls. Conduct a calibration exercise in which observers independently score the same units, compare discrepancies, document resolution, and retain proficiency results. A species expert's availability and the escalation turnaround belong in the field schedule.

Use project-defined field duplicates, repeat observations, blind or known reference specimens, independent cover estimates, GPS and depth checks, data-entry verification, range and logic checks, taxonomic review, and map accuracy assessment. Predefine acceptance and corrective-action rules. When equipment, observer, season, taxonomy, frame, software, classifier, or protocol changes, preserve both versions and evaluate comparability instead of smoothing the break away.

Repeatability evidence to preserve
Variation sourceControl or checkRequired interpretation
Season and phenologyObjective-linked survey window, life-stage observations, stage and clarity context, and repeat-window rule.State which taxa or forms may be underdetected and whether years are phenologically comparable.
Observer and taxonomyTraining, shared-unit calibration, reference specimens, unknown codes, determiner review, and proficiency record.Report unresolved taxa and observer disagreement; do not manufacture species-level precision.
Field methodControlled gear, effort, duplicate units, position and depth checks, and deviation log.Bound conclusions when retrieval, visibility, access, or equipment differs.
Mapping and analysisVersioned code and settings, independent validation, data checks, taxonomic crosswalk, and reproducible denominator.Keep model, frame, and taxonomy changes visible in trend products.

Sources: [2], [3], [10]

Close the survey without harming people, spreading plants, or losing evidence

Safety, spread prevention, and raw-data preservation are completion criteria, not afterthoughts once the last planned point is visited.

Use a site- and task-specific safety plan for vessel operation, weather and lightning, traffic and wakes, launch and shoreline access, cold or hot exposure, wading, unstable substrate, deep or moving water, low visibility, HABs, wildlife, sharp tools, lines and rake entanglement, submerged structures, lifting, diving, and decontamination chemicals. Keep loose line controlled and away from propellers and people; do not wrap a retrieval line around a hand or body. Wading, snorkeling, and diving are separate operational modes with separate competence, communications, rescue, and stop-work requirements.

Diving is not an improvised way to finish units that a rake or camera cannot reach. Determine which occupational, scientific-diving, agency, employer, and permit rules apply. Use only an authorized dive program, qualified team, approved manual and project, pre-dive assessment, emergency and entanglement plan, surface support, communications, and required records. Harmful-bloom or unknown-contaminant water can create ingestion, inhalation, skin-contact, and aerosol risk; defer to the responsible health and safety authority.

Prevent spread between stations and waterbodies through the controlling jurisdiction and project procedure. Inspect and remove plants, fragments, sediment, organisms, and water from boats, trailers, anchors, rakes, ropes, cameras, waders, dive gear, bilges, pumps, and storage areas. Keep clean and dirty zones, containment, disposal, treatment, rinse, drying or disinfection, chemical safety, equipment compatibility, and completion logs explicit. Do not copy a chemical, concentration, temperature, or contact time from another species or jurisdiction.

Before closeout, reconcile planned units, completed effort, statuses, taxa, unknowns, photos, specimens, determinations, field duplicates, equipment, decontamination, and safety exceptions. Preserve the original field forms and exports, raw GPS and depth records, vessel tracks, acoustic files, imagery and licenses, photos and metadata, specimen and transfer records, taxonomic history, frame and bathymetry versions, processing code and settings, derived layers, validation, QA findings, edits, and final release package. A static map image is not a sufficient archive.

  1. Stop and code unsafe or invalid work

    Protect people first, retain the planned unit, record actual position and reason, and distinguish not sampled from a valid vegetation non-detect.

  2. Contain and decontaminate

    Follow the jurisdiction-approved sequence for debris removal, contained cleaning, treatment or drying, rinse and waste control, equipment compatibility, PPE, and completion evidence.

  3. Reconcile field and taxonomic inventory

    Account for every unit, observation, unknown, image, specimen, transfer, duplicate, deviation, and pending determination before release.

  4. Freeze the raw-to-map lineage

    Archive immutable raw files, controlled edits, processing versions, validation, derived features, exclusions, and release status under the project retention plan.

Sources: [11], [12], [13], [9], [10]

Evidence base

Sources and review notes

Educational survey-design, field-method, and evidence guidance only. This guide does not approve a sampling frame, grid spacing, transect, quadrat, rake or toss method, remote-sensing model, taxonomic determination, abundance threshold, treatment trigger, permit, specimen transfer, decontamination procedure, dive plan, or management action. The current project plan, jurisdiction, land or waterbody owner, approved method, taxonomic authority, permit conditions, safety program, and data-quality objectives govern. Plant distribution and detectability vary with water level, season, life stage, depth, clarity, substrate, method, and effort. A survey result or suspected identification alone does not authorize treatment or establish that a species is invasive in the relevant ecosystem.

  1. Aquatic Plant Control Technical Note MI-02: Point Intercept and Line Intercept Methods for Aquatic Plant ManagementU.S. Army Engineer Research and Development Center · field protocol
  2. Long Term Resource Monitoring Procedures, Aquatic Vegetation MonitoringU.S. Geological Survey · field protocol
  3. Aquatic Plant Information, Tools and ResearchWisconsin Department of Natural Resources · field protocol
  4. Hydroacoustic Surveys for Submersed Aquatic Vegetation, Lake Erie, 2016-2019U.S. Geological Survey · reference
  5. Introduction to Aquatic Remote SensingU.S. Geological Survey · reference
  6. PLANTS DatabaseU.S. Department of Agriculture Natural Resources Conservation Service · reference
  7. About Invasive SpeciesNational Invasive Species Information Center · agency guidance
  8. Investigator Collections TasksU.S. National Park Service · agency guidance
  9. Boat, Gear and Equipment Decontamination and Disinfection Manual Code 9183.1Wisconsin Department of Natural Resources · agency guidance
  10. Quality Assurance Project Plan StandardU.S. Environmental Protection Agency · agency guidance
  11. National Field Manual, Chapter A1: Preparations for Water SamplingU.S. Geological Survey · field protocol
  12. How People and Animals Are Exposed to HABs and Their ToxinsU.S. Environmental Protection Agency · agency guidance
  13. 29 CFR Part 1910 Subpart T: Commercial Diving OperationsOccupational Safety and Health Administration · agency guidance