Route Change Detection
Observed crossings, turnarounds, slower passages and changes from a vessel’s previous comparable route.
Open a vessel in Pelyr to explore its route events alongside its recorded track.
Explore vesselsFollow the track.
See the passage.
Replay recorded positions around an event to see where the vessel travelled and where reports are missing.
Explore vessels- 01AIS reports
- 02Recorded track
- 03Event context
Gaps in received positions remain visible.
- Gate crossingA named passage was observed.
- TurnaroundA vessel was observed turning back.
- Slower passageA passage took longer than usual.
- Route choice changedA different gate was observed.
Notice a change.
Read the event.
Review observed gate crossings, turnarounds, slower passages and changed route choices alongside the journey.
Compare journeys.
Keep the context.
Compare a vessel’s observed route with its previous comparable passage. An event is a starting point for investigation, not an explanation of intent.
Travel time alone does not establish which route a ship took.
Compare route choice when both passages can be classified.
Use via HTTPS API.
Route Change Detection is also available through the HTTPS API. Bring route events into your application alongside vessel positions and recorded tracks.
Questions & answers
Route events, track playback and notifications.
Open a vessel in Pelyr to review its route events. Crossings, turnarounds, slower passages and changes in route choice provide context alongside the recorded track.
Route Change Detection compares observed passages and journeys. Zone Alert notifies you when a vessel enters or leaves an area you define. A zone crossing does not necessarily mean a vessel has changed its route.
Yes. Use track playback to revisit the vessel’s recorded positions and examine the passage around an event. The track helps you understand the observation in context.