Python AIS Tools Environment
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Added minimal sphinx version Aug 22, 2016
tests Resolves duplicate imports in test_aisparser May 31, 2016
.checkignore Ignore test folder in quantified code May 12, 2016
.gitignore ignore conf file Nov 9, 2017
.travis.yml issues with travis installing postgis Nov 9, 2017

Pyrate — the Python AIS Tools Environment

Documentation Status
Coverage Status Build Status Code Issues

Pyrate is a software architecture and suite of algorithms for the analysis of [AIS] ( data originating from ship-borne transceivers and collected by satellites and shore-based receivers. The different tools engage in an efficient and modular way, hence they are substitutable and extendable in a dynamic fashion. The primary goal is to validate and clean the dataset, extract information on shipping patterns and shipping routes. To make information easily discoverable, the data is stored in a variety of database types and formats.


  • Python-based
  • Parallel cleaning and writing of data files (.csv, .xml) into postgreSQL
  • Building of a vessel ID–transponder ID history for ship identification
  • Injection of artificial messages to ‘navigate’ vessel around land (coming soon)
  • Machine-learning module for passage/voyage discovery (coming soon)
  • Guide with cheat sheets (under construction)
  • Visualisation of shipping activity on map using this organisation’s repository shipviz (coming soon)


Pyrate requires an installation of Python 3, Postgresql 9.2+ and optionally Neo4j 2.1.7.


We're very happy receive contributions to our repository or integrate suggestions you may have. Please get in touch with us via github, or open an issue or pull request.

Further information

For further information please visit the pyrate wiki which contains full details of the architecture and algorithms, as well as guides for users and developers. For questions please visit the issue page.