MobileEventLog

A cross plattform project for android and ios to log events offline everywhere and sync them to sensor. Developed with flutter. A short how to use can be found below documentation/README.md

Concept

• Config page: Select a collection, mission or user and get corresponding devices and all event types. Store all this to a local persistent configuraion.
• Add Event Page: Allow selection of a device and adding a new event with all details. Add button adds the event to the staged events. Fields are not cleared but kept as they are.
• Staged Event: Show all entered and not yet uploaded events. Allow modification of all fields here. Alternatively show all events including uploaded once.

Local Data Concept

• The configuration widget is used to get the online available information for available devices and event creation.
• This includes: All collections, All devices part of a selected collection, Event operation types
• This "base data" is required to provide the dropdown menu options on the addevent page.
• This "base data" is stored persistently, so that it is also available offline!

Add Event Page

• Use Switch for automatic GNSS and Time update.
• Show "now" time button only if GNSS is disabled. This button shall fill the timestamp with the current utc time.
• Add stores the event to a local sql database
• A slide switch activates GNSS locationing. A field shall signal the GNSS status "no fix" or "x m presision". The fields lat, long, elevation and timestamp are updated automatically if GNSS is enabled.
• Input validation is done according sensor.awi.de Free Text: "a-z , A-Z , _ , 0-9 , ,(Comma) , ( , ) , + , - , . , :" -90 => Latitude <= +90 -180 => Longitude <= +180 Elevation: any numer

View & Sync Page

• Events added on the addevent page are stored persistently (sql database). They can be displayed in the view events widget. Each event has a flag which shows if the event is already exported to sensor. A slide switch allowes to show all events?

Configuration Page

• Radio Button to select if Mission, Contact or Collection based item selection.
• Dropdown to select a collection or mission
• Button "Set" to get Items from Registry and store them locally
• Button "Export Events" to export a JSON file locally with all the stored events for a backup in the field.
• Username und Passwort. A token generated here https://o2a-data.de/auth/settings can be used instead of legacy account passwords.

TODOs

• Allow adding an event to more than one device (urn)! "make UrnId => UrnIds" sync a event to every listed urn. ? Really needed?
• Compile an Apple iOS version.
• Add Git Tags as version information and show in app.

UI Feedback

• Desired Colors
  DAM Arctic: #00afb9 DAM Ocean: #0f1e50

Feedbackpopups: Background: #CEEDEB Text: #57827E

Add Event

• Show * next to lable for required fields.
• Set in configuration: Label on Add Event is beeing cleared but GNSS data is not. Harmonize this.

Wishlist:

• Allow upload of pictures check interface how to upload with sensor.
• How to log events for a device which does not exist yet? Dummy device in app and assign befor upload?
• Collection im Feld auswähle, Collection - Arbeitsgruppenzugehörigkeit.
• URN Dropdown filter by character. ~500 Geräte Verankerungsgeräte. Mission Sub Subcollecction/ Submission z.B. Verankerung oder Eisarbeiten oder Bojen?
• unique labels are desired by PANGAEA. Is adding the MissionName as a prefix to label usfull?
• Document taken sample via IGSN number QR Code? Scan a QR code.