Inland Waterway and
Ferry Tracking
A ferry tracking system that follows passenger vessels along river channels, counts people boarding and leaving, holds the published timetable, and drives the displays at every jetty. Scope covers the onboard device, the river corridor geofences, and the public information layer end to end.
THE CHALLENGEA River Is Not a Road, and a Ferry Is Not a Bus
Road tracking platforms snap a vehicle to the nearest street and call it done. A ferry on a river has no road network to snap to, the channel meanders, cellular coverage drops between bends, and the operator needs a verified passenger count at every jetty, rather than a dot on a map. The tracking layer follows the navigable channel as a corridor geofence, detects arrival and departure at each landing, reconciles boarding counts from BLE and RFID sensors against the timetable, and keeps the public displays honest even when the link to the vessel goes quiet for a few minutes.
Sits inside the Telematics and GPS Tracking stack and shares hardware and platform building blocks with Vessel and Fishing Boat Tracking.
WHAT'S INCLUDED
Onboard Hardware, River Geofences, and Passenger Information
Onboard Vessel Tracker
The onboard unit is built around an STM32 controller with a Quectel EC200 or BG95 modem and a u-blox NavIC and GPS receiver. It runs FreeRTOS, logs position to flash when the link drops, and reports over MQTT with TLS once coverage returns. The enclosure is rated IP67 for deck mounting.
Passenger Count and Boarding Sensors
Passengers boarding and leaving are counted with BLE beacon gates or RFID ticket reads at the gangway, with integration into turnstiles where the jetty already has them. Counts are timestamped against the docking event so each sailing carries a verified load figure rather than an estimate.
River Corridor Geofences
The navigable channel is modeled as a corridor geofence that follows the river centerline with a configurable width, instead of forcing the vessel onto a road network. The device flags when a ferry strays outside the channel corridor, which a road-snapping platform cannot represent.
Jetty and Landing Detection
A geofence is placed around each jetty and landing so the device emits a clean arrival and departure event as the ferry docks and casts off. These events drive the timetable comparison, the passenger count reconciliation, and the public arrival predictions.
Timetable and Schedule Integration
The published timetable is ingested and every departure and arrival is compared against it, so the operations team sees which sailings ran on time and which slipped. The system raises a schedule deviation alert when a ferry leaves a jetty outside its planned window.
Public Passenger Information
The passenger information displays at each jetty are driven from the same data that feeds a public app showing the next sailing, the live position along the river, and the predicted arrival. The display logic buffers gracefully so it never shows a vessel frozen mid-channel during a coverage gap.
HOW IT WORKS
From Deck Sensor to Jetty Display
The chain runs from the NavIC fix and the boarding gate on the deck to the timetable engine in the cloud and back out to the display on the jetty. Each stage is designed to stay correct when the river coverage drops, so a passenger waiting at a landing always sees a sensible next sailing.
Sense and Buffer
The onboard unit takes a NavIC and GPS fix, reads BLE and RFID boarding events, and buffers everything to flash. When the cellular link drops between bends in the river, nothing is lost and the device backfills once the modem reconnects.
Match Channel and Schedule
The cloud places each fix against the river corridor geofence and the jetty geofences, derives arrival and departure events, and compares them to the published timetable to score route adherence and on-time performance.
Inform and Predict
Verified position, passenger count, and predicted arrival flow to the jetty displays and the public app over MQTT. The display logic smooths over short coverage gaps so the information stays steady rather than flickering.
STANDARDS AND COMPLIANCE
Built for Indian Inland Waterways
NavIC and GPS Positioning
Positioning combines u-blox NavIC and GPS together, which gives a more reliable fix on Indian rivers where regional augmentation helps in valleys and near banks where the open-sky view is partial.
Inland Vessel Operations
Tracking, jetty event logging, and passenger count records are aligned with inland vessel operating practice so the data supports operator reporting and authority oversight on notified waterways.
Secure Transport and Data
Telemetry travels over MQTT with TLS, firmware updates are signed, and passenger count data is kept aggregated so the public feed never exposes individual ticket or device identifiers.
FAQ
Common Questions
How is a ferry tracking system different from a road vehicle tracker?
A road tracker snaps the vehicle to the nearest street on a road network. A river has no such network, so the navigable channel is modeled as a corridor geofence that follows the centerline with a set width. The vessel is matched to the channel rather than to a road, which is why a generic fleet platform misrepresents inland waterway movement.
How do you count passengers boarding and leaving the ferry?
Counting happens at the gangway using BLE beacon gates or RFID ticket reads, with integration into turnstiles where a jetty already has them. Each count is timestamped against the docking event, so every sailing carries a verified load figure rather than an estimate.
What happens when the cellular link drops between bends in the river?
The onboard STM32 unit logs position and boarding events to flash while the Quectel modem is out of coverage, then backfills the buffered data once it reconnects. The jetty displays buffer the last known state and predicted arrival, so they stay steady instead of showing a vessel frozen mid-channel.
How does the system detect arrival and departure at a jetty?
A geofence is placed around each jetty and landing. When the ferry enters or leaves that geofence, the device emits a clean arrival or departure event. Those events drive the timetable comparison, the passenger count reconciliation, and the public arrival predictions.
Can you check sailings against your published timetable?
Yes. The published timetable is ingested and every departure and arrival event is compared against it. The operations team sees which sailings ran on time and which slipped, and the system raises a schedule deviation alert when a ferry leaves a jetty outside its planned window.
What do passengers at the jetty actually see?
The passenger information displays at each jetty are driven from the same data that feeds a public app. Passengers see the next sailing, the live position along the river, and the predicted arrival. The display logic smooths over short coverage gaps so the information does not flicker.
Does positioning use NavIC?
Yes. Positioning uses a u-blox receiver with NavIC and GPS together. On Indian rivers, where banks and valleys can block part of the sky, the regional augmentation from NavIC gives a more reliable fix than GPS alone.
Ready to Build Your Ferry Tracking System?
Share your routes, your jetties, and how you sell tickets today to get a tailored approach to the river corridor geofencing, the passenger count sensors, and the public display layer, along with a realistic timeline.
Schedule a Free Consultation