This device has no WebGL, so the 3D view cannot run.
The map works without it.
Millinocket Lake. Offline. Nothing leaves this phone unless you join a lake code below.
72% of the hazard map is unverified, and that is a measurement, not a disclaimer. Aerial imagery on this lake was tested against the 260 MDIFW soundings and cannot tell 10 ft of water from 25 ft — AUC 0.507, a coin flip. The water is too stained to see the bottom through. Submerged hazards are not reliably mapped and, from imagery, cannot be.
What this shows you is where we have driven and where we know rocks are. It does not show you everywhere a rock is.
| Tier | Count | What it means |
|---|---|---|
| confirmed | -- | Above the waterline, cross-checked at 0.3 m |
| likely | -- | Returns infrared — a dry surface breaking the water |
| unverified | -- | Persistent across six flights. Meaning unknown |
The map shows the first two by default. Every candidate in Layers adds the third — useful if you know the lake and are looking for something specific, misleading if you do not.
All of them alarm regardless of what is drawn. Hidden from view is not the same as hidden from the alarm.
Every contour and every shade of blue comes from MDIFW, August 1954: 12 east–west transects, sounded by lead line. Up to 660 m between lines, all of it interpolated. Survey reach in Layers fogs everything more than 120 m from a real measurement — that is 42% of the lake, and in places 1.9 km.
Until a lake code is set, nothing leaves this phone. Joining means boat positions and reports go to a server — that is a decision for the people being tracked, not for whoever set the phone up.
Rock candidates from NAIP aerial persistence (6 flights, 2011–2023, quality-weighted) plus Sentinel-2 and hand-mapped rock. Depth from MDIFW 1954. Camps and piers © OpenStreetMap contributors (ODbL); hollow rings are Maine E911 addresses — a camp is there, its outline is untraced.