RV waterway database RIVERATLAS
The actual Guanzhou waterway structure, with a gold grid relating position and mileage

RV WATERWAY DATABASE / YANGTZE EDITION

Understand the waterway.Follow the voyage.

LenTack built the RV waterway database.
Waterway zones and mileage-based cells link information to position.
A shared reference for displays, calculations and decisions.

Why build our own database?

GUANZHOU REACH · WATERWAY GRID · BASEMAP © AMAP

01 / WHY BUILD OUR OWN DATABASE

Help devices understand
where the vessel is.

Wherever the vessel travels, what to display, how to calculate distance and which strategy applies all need a shared location reference.

So we built RV: divide the waterway into zones, create mileage-based cells and link channels, places and strategies to them. Once a device matches its position, it can find the relevant data for that location.

Detailed organization makes information clearer and device decisions better grounded.

  1. 01
    Zone

    Identify the reach and channel

  2. 02
    Grid

    Create finer position units

  3. 03
    Link information

    Support display, calculation and decisions

02 / HOW DETAILED IS THE DATABASE

100 m along the route.
Four zones across it.

Using public channel layouts and official kilometer points, we divide the main-stem mileage into 100 m intervals and combine them with four cross-channel zones to organize space. Finer divisions let different positions link to their own information.

01 / MILEAGE BASIS2,689Official kilometer points

Retain reach-specific mileage references

02 / FINER INTERVALS26,870100 m mileage references

Divide positions along the mileage axis

03 / SPATIAL STRUCTURE107,480Main-stem grid cells

100 m intervals × Four cross-channel zones

One YangtzeThree mileage references
Upper reachFrom Yichang
Middle reachFrom Wuhan
Lower reachFrom Wusongkou

Keep familiar official mileage while linking positions across the waterway, providing a basis for voyage calculations across reaches.

Counts are based on RV Yangtze v1.8. The 100 m figure describes mileage intervals, not satellite positioning accuracy.

From a waterway to each cell.

Connect the channels, establish intervals, then associate information with the grid.

Gold main channels join cyan branches, showing main and branch channel connections
01 / ORGANIZE CHANNELS

Connect the waterways first

Retain main channels, branches and junctions so positions belong to a channel and distances follow its course.

Official kilometer points along a channel, subdivided into 100 m mileage references
02 / ESTABLISH INTERVALS

Give each position a reference

Subdivide between official kilometer points. Retain segmented mileage while building continuous relationships along the waterway.

Along-channel intervals and four cross-channel zones form a grid, with one position cell highlighted in cyan
03 / LINK INFORMATION

Give every cell context

Along-channel intervals and cross-channel zones organize the space together. A vessel's cell links it to relevant information.

Local waterway visualization. Grid and associations are schematic. Gold shows channels and mileage references; cyan shows position and linked information.

INSIDE A CELL / ORGANIZING INFORMATION

Put data in cells.
Connect the relationships.

Use the grid as a position index linking different types of data. Devices read what they need, with a common basis for display and calculation.

Location context
Reach, channel and cross-channel zoneIdentify where the vessel is
Mileage reference
Official mileage and continuous along-channel relationshipsSupport progress and distance calculations
Information along the route
Cities, wharves, navigation marks, anchorages and other featuresFind relevant information by position
Regional strategies
Strategy data linked to the current areaProvide a basis for automatic device decisions

03 / WHAT THE DATABASE ENABLES

Position brings up information.
Information informs decisions.

Matching the vessel to a grid cell links its channel, mileage and nearby information. These can determine what is displayed, support voyage calculations and give the Hub Terminal a basis for automatic decisions。

ONE POSITION · THREE LAYERSGUANZHOU REACH · LAYERS EXPANDED
Three data layers linked to an actual river reachThe same river segment is shown as channel, mileage-grid and route-information layers. Select an item to highlight its layer. Association points are schematic.01Channel structure02Mileage grid03Information along the routeOne position · Linked layersBasemap © Amap
Position matches a cell and links information across layers · Schematic

First, know which channel you're on.

Place GNSS coordinates within the waterway structure to identify the channel while retaining main and branch connections. The channel gives position its context.

This becomes “Current channel” in the App

Give position a calculable distance.

Subdivide official kilometer points into 100 m intervals, then organize them as a spatial grid. Relate the start, current position and destination to calculate traveled, remaining and relative distances.

This answers “How far have we gone, and how far is left?”

Give more information its place.

Link shipping cities, wharves and route features to the same position reference. Turn coordinates into familiar place names and find voyage endpoints by city.

This supports location descriptions and place selection

One location reference. Multiple functions.

From reading position and calculating voyages to retrieving regional strategies, the database organizes the relationships. The Hub Terminal processes them using live state and function rules.

01 / POSITION

Position gains a name

Link coordinates to channels, shipping cities and official mileage, turning numbers into a familiar location description.

LOCATION · KNOW WHERE YOU ARE
02 / VOYAGE

Voyages gain a reference

Place the start, current position and destination in the same along-channel relationship to calculate total, traveled and remaining distance.

PROGRESS · KNOW HOW FAR IS LEFT
03 / DISTANCE

Places become connected

Relate destinations and waypoints to the current position, calculating relative distances along the waterway.

DISTANCE · KNOW WHAT COMES NEXT
04 / DESTINATION

Endpoints gain a clear basis

Organize shipping cities, wharves and official kilometer points into an endpoint directory for setting up voyages.

VOYAGES · START WITH FAMILIAR PLACES
05 / HISTORY

Positions connect to voyage records

RV supplies the position reference. The Hub Terminal records the journey, organizing speed and distance changes by time and voyage.

HISTORY · FOLLOW THE JOURNEY BACK
06 / DECISION

Device decisions gain a basis Future extension

Link regional network strategies to position so the Hub Terminal can evaluate them alongside live network conditions and apply function rules.

AIM · FEWER MANUAL ADJUSTMENTS ALONG THE ROUTE

IN PRACTICE / DATA THROUGHOUT A VOYAGE

One position.
Part of a whole voyage.

For a voyage, the database provides the position reference. The Hub Terminal combines positioning, voyage information and records to calculate. “Where are we? How far is left? How did we travel?” Different data works together to answer these questions.

POSITION → VOYAGE → RECORDSVoyage relationship schematic
The start, current position and destination are connected along the channel, distinguishing traveled distance, remaining distance and the recorded track
Channel & Mileage referenceCurrent position & ProgressTrack recorded by the device
01 / DESCRIBE POSITION

Official mileage answers “Where?”

Distances from Yichang, Wuhan and Wusongkou each use their own reference. Keeping both the reach and mileage in the display gives a complete location.

Familiar descriptions help confirm and communicate position.
02 / UNDERSTAND PROGRESS

Along-channel distance answers “How far?”

Connect positions across the waterway to support calculations between different mileage references, then relate them to voyage endpoints and progress.

Let the device handle mileage conversions, with less mental arithmetic.
03 / REVIEW THE JOURNEY

Track records answer “How did we travel?”

Organize successive positions and times into records. Review actual speed and distance changes by time or voyage.

Position references and navigation records complete the picture.

Along-channel mileage provides a voyage-progress reference. Track distance comes from device records; the two use different calculation bases. This diagram explains data relationships and is not for navigation decisions.

04 / WHAT THIS MEANS FOR YOU

Less searching.Less mental arithmetic.
A clearer voyage.

Zones, grids and linked information become everyday conveniences: read position in words, see progress visually and review the journey with statistics. Open the LenTack App to find the answers that matter on this voyage.

UNDERSTAND YOUR LOCATION

“Where are we now?”
Open the App. Find the answer.

Shipping city, current channel and official mileage appear together. Spend less time looking up your position and communicate voyage progress more clearly.

City & Channel
Understand the context of your position
Mileage & Reference
Keep familiar shipping location descriptions
HOW THE DATA WORKS

Satellite position → Grid match → Channel, city and mileage

Position & VoyageLenTack App
Current positionYizhengYizheng Channel
From Wusongkou302.5 km
Official mileageLower Yangtze

Position, channel and mileage. Read together.

SEE YOUR PROGRESS

“How much farther?”
Progress, clearly displayed.

Set voyage endpoints to give total, traveled and remaining distance a shared reference. A progress bar connects the numbers, with less mental arithmetic.

One voyage
View total, traveled and remaining distance together
One progress view
Place the current position between start and destination
HOW THE DATA WORKS

Endpoints + Current position → Along-channel distance → Voyage progress

Current voyageUnder way
DepartureNanjing
DestinationZhenjiang
Total distance86.4 km
Traveled51.6 km
Remaining34.8 km

Start, current position and destination. One voyage.

A JOURNEY YOU CAN REVIEW

“How did this voyage go?”
Look back with charts and statistics.

View speed history for today or the current voyage, alongside average speed, maximum speed and cumulative distance. Individual changes become records you can review.

By time
See the day's changes and fluctuations
By voyage
Review average and maximum speed with total distance
HOW THE DATA WORKS

Terminal records → Organized by time and voyage → App charts and statistics

Speed historyCurrent voyage
km/h
2412008:0010:0012:00
Voyage average16.8 km/h
Maximum speed21.6 km/h
Cumulative distance Official mileage51.6 km

Screens evolve with App and device releases. Actual information depends on device records, data coverage and positioning conditions.

FROM DATABASE TO EVERYDAY USE

Data provides the basis.
Technology joins the voyage.

We built our database to give devices a basis for calculations and decisions, make information easier to understand and lay the groundwork for future automation.

01 / DATA

RV waterway database

Organize position, mileage, route information and strategies.
Provide a basis for display, calculation and decisions.

02 / COMPUTE

Hub Terminal

Calculate and record using live state.
Evaluate and act according to released function rules.

03 / EXPERIENCE

LenTack App

Readable positions. Clear progress.
History in charts. Voyages on record.

LenTack · 凌台科技

HARDWARE

Hardware

LENTACK / MARINE INTELLIGENCESmart marine terminals and connected systems