FIELD INTELLIGENCE · PRELAUNCH

One field record. Two responsible destinations.

LFE is designing a field workflow that separates operational evidence from the official public record—then makes the handoff clear, traceable, and useful.

Open filtered lionfish mapStart an LFE field record

Species reference: Pterois volitans/miles. Public records remain subject to USGS review and revision.

LIVE REFERENCE LAYER

Start with the public evidence.

These verified USGS resources provide the current reference layer for planning, field checks, and responsible reporting.

01
PUBLIC REFERENCE

SIREN multi-species hotspots

Explore broader invasive-species occurrence density and regional patterns. This SIREN layer is not lionfish-filtered.

Open general SIREN layer
02
SPECIES MAP

Filtered USGS lionfish map

View collection records for the consolidated Pterois volitans/miles species profile.

Open filtered lionfish map
03
SOURCE RECORD

USGS species profile

Review occurrence records, references, distribution context, and the limits of interpreting record counts.

Review species profile
DATA NOTE

USGS describes NAS records as preliminary or provisional. Collection-record counts do not measure abundance and may not represent the complete established distribution.

RESPONSIBLE ROUTING

Record once. Route with intent.

The workflow keeps LFE operating evidence distinct from the official government occurrence record while preserving a path to reconciliation.

1

Observe

Capture location, date, depth, counts, effort, habitat, and supporting evidence at the point of work.

2

Log in LFE

Create an operational record for a sighting, capture, survey effort, or other field event.

3

Verify

Check coordinates, evidence, species identification, permissions, and completeness before external use.

4

Submit or reconcile

Use the official USGS report form now; pursue automated reconciliation only through an approved interface.

LFE FIELD RECORD

Build the operational evidence base.

This prelaunch intake is structured for sightings, removals, and survey effort. It is an LFE operational record—not an official USGS submission.

Need the official record?

Submit the sighting through the USGS NAS form after checking the record for accuracy and upload permissions.

Open official USGS form

Do not submit protected-location information or another person’s contact details without authority and consent.

Submission creates an LFE operational intake only. It does not create a USGS occurrence record.

By submitting, the sender acknowledges LFE’s Privacy & Data Use notice and Participation Terms. This is a non-binding prelaunch inquiry.

Field record received. LFE will review it before any external use or reconciliation.
The record could not be submitted. Check the required fields and try again.
MINIMUM DATA STANDARD

Make every record useful.

A strong field record can support operational learning, scientific review, partner coordination, and future model validation.

01Date, time, and defensible location
02Observed and removed counts kept separate
03Depth, effort, method, and habitat context
04Evidence link and reachable observer
05Permissions checked before external sharing
INTEGRATION ROADMAP

Useful now. Expandable by agreement.

NOW

Public map + internal intake

Operators can reference live public maps, log structured LFE records, and route official sightings to USGS.

NEXT

Read-only occurrence dashboard

The documented NAS API can support verified occurrence-history queries and comparison against LFE field activity.

PARTNER GATE

Approved reconciliation

Automated submission or bidirectional exchange requires an approved USGS interface, data agreement, and validation protocol.

Review NAS API documentation Discuss field-data collaboration