Hopp til hovedinnhold

GILLI · · 4 min read

Live GPS Depth Is the Next Lake Map Step

The same point-depth endpoint that powers tap-to-depth can later answer the boat-position question: how deep is the mapped water under me right now?

Tap-to-depth is only the first use case.

The same lake depth system can support live GPS depth for mapped lakes.

Not live sonar. Not a real-time measurement. But a chart-derived estimate at the boat's current position, sampled from the published bathymetry surface.

For anglers, that is useful.

The Endpoint Is the Same

The core question is simple:

Given latitude and longitude, is this point inside a mapped lake with depth available? If yes, return sampled depth from the lake surface. If no, return fallback or no coverage.

That works whether the coordinate comes from a long press on the map or from the phone's current GPS position.

The backend should not care.

Boat Position Adds Field Value

When drifting, trolling, anchoring, or scanning a bank, anglers often ask where they are relative to structure.

If Gilli can show estimated chart depth under the current position, the bathymetry layer becomes more than a planning map. It becomes field context.

The language must stay honest: this is chart-derived depth, not sonar.

Accuracy Has Dependencies

Live GPS depth depends on several things:

  • phone GPS accuracy
  • quality of the source chart
  • georeferencing quality
  • interpolation surface
  • lake version
  • whether the point is inside valid mapped water

The app should avoid pretending that a chart-derived estimate has centimeter precision.

Rounded, clearly sourced output is better.

It Connects to Ecology

Live mapped depth becomes more powerful when paired with fish ecology.

If the app knows the likely usable depth band for a species, it can help the angler compare current position against that band. If oxygen or thermocline context suggests deep water is less usable, the same depth number gets a different meaning.

Depth becomes guidance when paired with species ecology.

Build the Contract First

The right order is clear.

First, make point-depth reliable. Then preserve source type and lake version. Then expose tap depth. Then consider live GPS display.

A feature like this should grow from a clean backend contract.

lake-depthgpsbathymetrygilli