OpenSeaMap-dev:Crowd Sourced Depth Data

dev: Water depth
depth-Website
Crowd Sourced Depth Data
Depth raw data
Depth meta data
Depth data processing
User login
Bordnetz
NMEA-Logger anschliessen
Hardware loggers - Specifications - NMEA-0183-2-Kanal-Logger - NMEA-2000-Logger - WLAN-NMEA-0183 mit TP-Link - NMEA-0183-Logger mit Arduino - WLAN-NMEA-2000-Logger mit Raspberry Pi
NMEA-0183-SW-Logger Jens
proprietäre Formate
Bus
Mess-Strategie
Mobiler Tiefenmesser
NMEA

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, shipping company
• 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)
• Improve data quality by a lot of other meta data about the ship and the measurement eqipment...
• 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

US100 Upload tracks

As a user I'd like to upload my 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 need a performant compression, and 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, togehter with my vessels data. Acceptance criteria Upload multiple tracks at the same time. Data compression > 1:50 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). Data compressor. Login on map (open discussion about client framework). Redesign map (open discussion about client framework).

US101 Manage vessels

US101 Manage vessels

As a user I'd like to manage my vessels via a web frontend. This allows me now (or 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 (ID). Acceptance criteria Add an new vessel by naming it. Each Vessel gets an unique ID. Set offset for echo sounder. Set distance between gps antenna and echo sounder (lengthwise and crosswise). Set all the other needed meta data... 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). Daten-Parameter.xls Results Daten-Parameter.xls (zur Prüfung bei der HCU)

US102 Assign tracks to vessels

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 my track on the map. Assign my 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

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 meta-data collection. Supports the collection of all necessary data (see US101) Dependencies Daten-Parameter.xls (zur Prüfung bei der HCU) Results german version (pdf) german version (odt) [actually not uploadable]

US104 HowTo for connecting devices

US104 HowTo for connecting devices

As a boater/boat owner I would like to contribute to openseamap with depth data, but I don't ave the equipment or don't know how to get the data from it. I would like to see documentation on the equipment necessary and the use of it. Acceptance criteria There is an overview on the wiki where the user can figure out whether the boat have the necessary equipment There is a section on what to look for when upgrading the equipment There is a HowTo for connecting HW-Logger and SW-Logger to my nautical devices and my computer. There are links to vendor manuals pointing to the exact pages describing the use of equipment along with openseamap specific usage comments. Results De:Bordnetz, Shipnetwork De:NMEA-Logger_anschliessen

Tasks

Links to SourceForge Feature-Requests:

• ...