Currently, submitting a form does not clear fields, does not validate data, and automatically adds new logs to the database.
Suggestions for improvements:

• Add a confirm button when adding new logs, indicating that the recorded log fields will be cleared and the new log will be added
• Clear the recorded logs when a new log is added
• Validate that the data makes sense, eg altitude is positive, and the start time is before the end time

Implement all necessary fields from the fly-ops template to be recorded in the app

• Maximum altitude (in feet)
• GSO (Ground Station operator)
• VO (Visual Observers)
• Terrain (Optional Text Entry)
• Bystanders nearby
• Airspace Class
• PIC (Pilot in command)

Mobile layout needs to be fixed to look better

• Make the delete logs buttons only show in dev environment
• Detect production vs development mode and reference the correct database

Review Dependencies

Problem

We need to run through the installed dependencies and verify that they are actually being used or will be useful in the near future.

Solution

Review packages installed by @Lmyszka4

We need a way for a lead to verify that the information on the log is all sound.
We need a signature field for a lead, whether it be a drawn signature or a "virtual" typed signature field.

Rewrite about page to be more guide-focused explaining how to use the compakt app

Add Drone Information

Problem

EHS requires flight logs to have the drone's FAA registration number in the logs. Also, we will need to record Remote ID with the new regulations.

Solution

Add a text input field, or expand the field in #7

When adding a new log and attempting to see details in log page, the wrong log is expanded
Steps to replicate:

• Create new log
• Go to logs and expand most recent log

• Ask user for app permission to access location data
• Pull from phone gps data to get location and relevant weather info

Load data from database on app startup, regardless of which page gets loaded first

Make inputs required for the following fields:

• Date
• Time (Start + End)
• Location
• Weather
• Pilot ID
• Remote ID

Export Flight Data

Problem

The flight data from the app must be extracted from the site in some capacity, so it can be passed to EHS.

Solution

Write a function to export all flight recordings in CSV file

Currently, pages access is set up for all @mst.edu addresses. This should be changed to only include multirotor-specific email addresses.

Add Pilot Information

Problem

flight information must have a pilot in command for EHS's records.

Solution

Add a selection or text input for FAA registration number for the primary pilot in command for a given flight

Create checklist displaying flight day to-do information

• Call hospital
• Call university police
• Start flight (automated)
• Stop flight (automated)

Sort logs screen by dates, where most recent is displayed at the top.

Add documentation about the cloudflare deployment, specifically:

• How to access branch deployments and the database
• How to use features of the dev console (adding new users, pompting the database, seeing deployments)
• Database schema for reference

• Make the delete logs buttons only show in dev environment
• Ideally only works with the test database from #35

Add authentication so that only mst students/multirotor flight ops can log in to the Compakt application.

Make fonts look good and fix transition to non-copyright font

Add Installation instructions to README so users can download and install compakt on their own devices.

Add docstrings to functions within svelte and typescript files.

If a mistake is made when pressing the time buttons, it cannot be reverted. Suggestion is to add undo/redo button and form history system so that mistakes can be reverted more easily. Target form fields would be start time, stop time, and weather.

When downloading the csv file, the info should not include the v_props column

• Insert into database method not working properly
• Add method to remove target logs from the database

Save all Flight Recordings to File

Problem

we need to be able to save each flight recording to a readable file, an Excel spreadsheet or CSV.

Solution

Utilize Javascript code or outside libraries to save flight recordings

Add an authorization system to access the logs database more securely.

Currently the database being used when testing is the production database, but future testing should detect dev mode and use a separate database reference.