Integration of elliptical ship domains and velocity obstacles for ship collision candidate detection

P. F. Chen, P. H.A.J.M. van Gelder, J. M. Mou

Research output: Contribution to journalArticleScientificpeer-review

6 Citations (Scopus)
62 Downloads (Pure)

Abstract

The maritime shipping industry has been making significant contributions to the development of the regional and global economy. However, maritime accidents and their severe consequences have been posing an incrementing risk to the individuals and societies. It is therefore important to conduct risk analysis on such accidents to support maritime safety management. In this paper, a modified ship collision candidate detection method is proposed as a tool for collision risk analysis in ports and waterways. Time‐Discrete Velocity Obstacle algorithm (TD‐NLVO) is utilized to detect collision candidates based on the encounter process extracted from AIS data. Ship domain model was further integrated into the algorithm as the criteria for determination. A case study is conducted to illustrate the efficacy of the improved model, and a comparison between the existing method and actual ship trajectories are also performed. The results indicate that with the integration of ship domain, the new method can effectively detect the encounters with significant collision avoidance behaviours. The choice of criteria can have a significant influence on the results of collision candidate detection.

Original languageEnglish
Pages (from-to)751-758
Number of pages8
JournalTransNav
Volume13
Issue number4
DOIs
Publication statusPublished - 2019

Keywords

  • Collision Avoidance
  • Elliptical Ship Domain
  • Ship Collision Candidate Detection
  • Time-Discrete Velocity Obstacle Algorithm (TD-NLVO)
  • AIS Data
  • Ship Trajectory
  • Collision Candidate Detection
  • Collision Candidate

Fingerprint

Dive into the research topics of 'Integration of elliptical ship domains and velocity obstacles for ship collision candidate detection'. Together they form a unique fingerprint.

Cite this