OpenSeaMap-dev:Crowd Sourced Depth Data

Preface

OpenSeaMap plans to display contour lines on the map. Existing data from private companies or authorities mostly is not public domain respectively not compatible with the license of OpenSeaMap/OpenStreetMap. This is why OpenSeaMap tries to get this data with the help of the community. Nevertheless license free data from private companies or authorities is highly welcome.

Target Group

Different potential data contributors were identified.

• Vessel owner
• Charter broker
• Charterer
• Government
• Hydrographic institute

Goals

• Collect tracking data
• Improve data quality by adjusting depth (offset echo sounder)
• Improve data quality by adjusting positions (distance between gps antenna and echo sounder)
• Provide an easy to use web frontend which supports the user to upload and manage his tracks/vessels.

User Stories

The idea is to define necessary user stories, discuss them (on the mailing list) and then create resulting tasks in the tracker (SourceForge).

The use case diagram shown below summarizes the different user stories.

Use Case Diagram

US100 Upload tracks

As a user I'd like to upload tracks from one or more vessels via a web frontend. I should be able to upload multiple files at the same time. Because the files can contain a huge amount of data, I'd like to get informed about the upload progress. As an application (software logger, third party data source) I'd like to automatically upload tracks from different vessels. Acceptance criteria Upload multiple tracks at the same time. Upload progress visible while uploading. Backend realized in form of a project wide API. Only authorized users/applications can upload tracks. Dependencies API for authentication (work in progress). Login on map (open discussion about client framework). Redesign map (open discussion about client framework).

US101 Manage vessels

As a user I'd like to manage my vessels via a web frontend. This allows me later on to assign my tracks to the corresponding vessel, which allows the system to adjust the track data and thereby increase the data quality. To distinguish my vessels I'd like to name them. Acceptance criteria Add an new vessel by naming it. Set offset for echo sounder. Set distance between gps antenna and echo sounder (lengthwise and crosswise). Backend realized in form of a project wide API. Only authorized users can manage their vessels. Dependencies API for authentication (work in progress). Login on map (open discussion about client framework). Redesign map (open discussion about client framework).

US102 Assign tracks to vessels

As a user I'd like to assign my tracks to the corresponding vessel via a web frontend. This allows the system to adjust the track data and thereby increase the data quality. To distinguish between the tracks I'd like to display a track on the map. Acceptance criteria Display track on the map. Assign track to a vessel. Backend realized in form of a project wide API. Only authorized users can assign their tracks to their vessels. Dependencies API for authentication (work in progress). Login on map (open discussion about client framework). Redesign map (open discussion about client framework).

US103 Paper document for offline collecting

To collect vessels data I'd like to have a paper document which allows me to go on board without an electronic device which has to be online. Acceptance criteria Paper document (pdf, odt) for data collection. Supports the collection of all necessary data (see US101) Results german version (pdf) german version (odt) [actually not uploadable]