Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A aisdb
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • aisdb
  • Issues
  • #30

Closed
Open
Created Sep 14, 2022 by Gabriel Spadon@gabrielspadon

Trajectory visualization from live AIS data stream

Hi there, I was wondering if it's possible to add a new feature for showing streaming AIS data on the web interface of AISDB. The idea would be to use this feature to integrate with vessel tracking machine learning models. This way, we could see the true vessel trajectory and compare it with the predicted one.

Ideally, I believe we need asynchronous communication between the model and the interface. The model will probably output faster than what's reasonable for the interface to handle. We need a pool to store the model's output in this case. The output is sets of NumPy arrays where each row is a vessel, and each column is a pair of coordinates (lat and long). Another possibility of output would include the depth with the coordinates. The positioning of the vessel will be sorted by time.

Another feature would be showing the trajectory improvement over the network's training. As the model improves over the training, the outputs will change for the forecasting and not for the true data. This means we will plot the same data repeatedly, but hopefully, the forecasting will be closer to the true data behavior after every iteration.

In Fig 8 and 9 of this Article, there's an example of contrasting trajectories. Our case, however, would be shown in a Mercator projection.

Let me know if that's possible to be implemented. Thanks for the help!

Edited Sep 15, 2022 by Matthew
Assignee
Assign to
Time tracking