OpenSeaMap-dev:Crowd Sourced Depth Data - Versionsgeschichte

Kannix: category:Depth-DB added

2015-01-05T16:19:12Z

category:Depth-DB added

Markus am 29. November 2012 um 23:25 Uhr

2012-11-29T23:25:11Z

Markus am 29. November 2012 um 21:17 Uhr

2012-11-29T21:17:45Z

Markus: uff - meine Ergänzungen sind nicht gespeichert...

2012-09-24T20:56:27Z

uff - meine Ergänzungen sind nicht gespeichert...

Dom: Die Seite wurde neu angelegt: „== Preface == OpenSeaMap plans to display contour lines on the map. Existing data from private companies or authorities mostly is not public domain respective…“

2012-09-20T20:35:57Z

Die Seite wurde neu angelegt: „== Preface == OpenSeaMap plans to display contour lines on the map. Existing data from private companies or authorities mostly is not public domain respective…“

Neue Seite

== 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.

[[File:Water-depth.png|frame|none|Use Case Diagram]]

{| class="wikitable"
| '''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).
|}

{| class="wikitable"
| '''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).
|}

{| class="wikitable"
| '''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).
|}

{| class="wikitable"
| '''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'''
* [[Media:Vessel_info_de.pdf|german version (pdf)]]
* german version (odt) [actually not uploadable]
|}

← Nächstältere Version		Version vom 5. Januar 2015, 16:19 Uhr
Zeile 136:		Zeile 136:

	* ...		* ...
		+
		+	[[Kategorie:Depth-DB]]

← Nächstältere Version		Version vom 29. November 2012, 23:25 Uhr
Zeile 1:		Zeile 1:
−	{{Vorlage:Water_depth}}	+	{{Vorlage:dev:Water_depth}}

	== Preface ==		== Preface ==

← Nächstältere Version		Version vom 29. November 2012, 21:17 Uhr
Zeile 1:		Zeile 1:
		+	{{Vorlage:Water_depth}}
		+
	== Preface ==		== Preface ==

@@ Zeile 8: / Zeile 8: @@
 * Vessel owner
-* Charter broker
+* Charter broker, shipping company
 * Charterer
 * Government
@@ Zeile 18: / Zeile 18: @@
 * 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.
@@ Zeile 28: / Zeile 29: @@
 [[File:Water-depth.png|frame|none|Use Case Diagram]]
 {| class="wikitable"
 | '''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 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.
+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.
 * Upload progress visible while uploading.
 * Backend realized in form of a project wide API.
@@ Zeile 43: / Zeile 46: @@
 '''Dependencies'''
 * API for authentication (work in progress).
 * Login on map (open discussion about client framework).
 * Redesign map (open discussion about client framework).
 |}
 {| class="wikitable"
 | '''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.
+| 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.
 * 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.
@@ Zeile 63: / Zeile 70: @@
 * Login on map (open discussion about client framework).
 * Redesign map (open discussion about client framework).
 |}
 {| class="wikitable"
 | '''US102 Assign tracks to vessels'''
@@ Zeile 71: / Zeile 83: @@
 '''Acceptance criteria'''
-* Display track on the map.
+* Display my track on the map.
-* Assign track to a vessel.
+* 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.
@@ Zeile 82: / Zeile 94: @@
 |}
 {| class="wikitable"
 | '''US103 Paper document for offline collecting'''
@@ Zeile 88: / Zeile 101: @@
 '''Acceptance criteria'''
-* Paper document (pdf, odt) for data collection.
+* Paper document (pdf, odt) for meta-data collection.
 * Supports the collection of all necessary data (see US101)
 '''Results'''
@@ Zeile 95: / Zeile 111: @@
 * german version (odt) [actually not uploadable]
 |}