Boat landings are infrastructure too, even when nobody marked them

At sunrise, a boat landing looks ordinary. By 8am it is moving children, farm produce, and medicine boxes in and out before the river traffic picks up. If the bank has no shared reference, the same place can be described three different ways by three different people. The first family might call it the old landing. The driver might call it the bend after the mangrove. The clinic runner might just say "the jetty" and assume everyone knows which one. By noon, one shipment is waiting on the wrong side of the river because the message was clear to the person who sent it and vague to the person who had to drive there.

Along river systems, not every critical access point is a road junction. Sometimes it is a muddy bank where boats dock, children board transport, and goods are handed over. That bank may be the only practical connection a village has to school transport, deliveries, and emergency care, which makes the lack of a common reference a real operational problem instead of a naming inconvenience. When the river rises, the path changes. When the sandbag wall moves, the landing point changes. The code has to be the one thing that stays.

Why this point needs a code

Boat landings matter for: - school transport - supply runs - emergency evacuation - rural clinic access

Using SBKG.0298.456, the landing can be documented and shared as one exact place instead of "the riverbank near the big tree." If a place is operationally important, it deserves a location reference people can trust. Once the code is consistent, boat drivers, parents, health workers, and suppliers can all aim for the same point without relaying a story each time. That saves time on ordinary mornings and even more time when the river is high and everyone is trying to move fast.