Overview
What this step does: state the job, the Navy sections covered, and the path through the tool.
Monitoring survey data arrives from many sources with duplicates and errors. The Navy needs it clean, mapped, and submitted on schedule.
From messy intake to Navy-ready package
OBIS, GBIF, and survey CSVs come in together. QA drops bad rows. Clean points become SDS layers, quick-look figures, and a versioned submittal.
What Heimdall Marine does
- Intake monitoring records from OBIS, GBIF, and survey CSVs.
- QA every row with pass/fail reasons (duplicates, on-land points, bad dates, taxonomy).
- Map clean sightings as SDS-style GIS layers (Section C 3.7).
- Report and submit quick-look tables/figures (3.1.3) and versioned SEAMAP/ATN-ready packages (3.1.2).
For AECOM: biologists stay on surveys. Draft and final reports go out on time. Data packages pass Navy checks the first time.
Workflow
Use the guided walkthrough after sign-in, or click a step to jump. Next and Back move through the path.
Contract frame: NAVFAC Pacific Marine Resources Technical Services, N6274227R1801, Section C 3.1.2, 3.1.3, and 3.7.
Step 1 of 5 · Monitoring data
Monitoring intake
What this step does: show how much raw monitoring data came in, and from which sources, before cleaning.
Occurrence records for cetaceans, Hawaiian monk seal, and sea turtles from OBIS and GBIF. Review volume and sources before QA, SDS layers, and Navy data submittals.
By source
| Source | Records | Role |
|---|
By species group
| Group | Records |
|---|
Survey effort here is public occurrence density, not ship hours. Use it to size QA and report tables.
Step 2 of 5 · Monitoring data
QA review
What this step does: flag bad or repeated records and show why, so clean counts hold up in review.
Each record is pass or fail with a reason code. Select a rule to map the flagged points. Cross-source duplicates are the largest class for this pull.
Failure rules
Flagged locations
Duplicate merge
Same species, date, and location (~100 m). Keep one; flag the repeat.
·
| Source | ID | Result |
|---|
Clean counts use the kept OBIS row. The GBIF copy stays in the QA log.
Step 3 of 5 · Monitoring data
Map layers · Section 3.7
What this step does: put the clean sightings on a map as the GIS layer the Navy expects (Section C 3.7).
Clean sightings after QA. Filter by group, species, year, and source. Toggle flagged points only when you need to show residual risk. Keep them out of the deliverable layer.
Step 4 of 5 · Reporting
Quick-look · Section 3.1.3
What this step does: draft the quick-look tables and figures for Section C 3.1.3.
Summary for the installation package: counts, QA rate, species table, and figures. Download the PDF for the leave-behind.
Clean records by year
Records by source
Step 5 of 5 · Reporting
Data submittals · Section 3.1.2
What this step does: hand off the versioned Section C 3.1.2 package (SEAMAP CSV and GIS files).
Versioned package for Navy delivery: OBIS-SEAMAP CSV, SDS-style GeoPackage and shapefile, plus the field dictionary. Hash and row counts travel with the version.
Version
| Version ID | |
|---|---|
| Created (UTC) | |
| SHA-256 | |
| Rows | |
| By source |
Changelog
Import · Survey CSV
Import survey CSV
What this step does: run the same QA rules on a local survey CSV before it enters the package.
Run the same QA rules on a local survey export. No server. Use the sample file, or drop your own.
scientific_name, event_date, decimal_latitude, decimal_longitude, individual_count, species_group
QA result
| Rule | Count |
|---|
Mapped rows
Passed points use group colors. Failed points are red; open a popup for the reason.