This would enable easier briefing/debriefing.

The action buttons are already there (on the flight page) but the feature is not implemented.
Quite easy to do, but requires some coding...

Gestures
Add gestures to

• rotate the map
• add steerpoints from finger location ("direct to")

Buttons
Add action buttons to

• orient the map (North or aircraft heading)
• control which layers are displayed

Layers
From the database, add

• icons representing airports, VRPs and navigational aids
• polygon representing airspace boundaries

Base Map
Add base (OpenStreetMaps) maps, on which navigational data from the database would be drawn. The tiles can be obtained from OpenMapTiles servers.

The NOTAMs used to be fetched from PilotWeb, which is now deprecated and has been replaced by FNS Notam Search from the FAA.

The query URL and parameters are quite simple, but requires a recaptcha token. If there is no way to obtain a valid token, then consider using another service (SWIM, EAD, ...).

Only one map can be loaded at a time in the current version of the code. When the map is changed using the dropdown menu or via the settings page, the tiles that are already loaded remain. They need to be cleared and the map needs to be refreshed.
Note that the only way to change the map right now is to via the setting page and restart the app.

There are several issues and PR (619, 584) opened in the flutter_map repository that could solve this issue. If that does not work, consider to load all the maps using a list of layers.

For now, the database needs to be generated by every single user, who should first download the navigational data from openAIP, then process them, and finally re-compile the app. This should be done as often as AIRAC changes, that is every month, and is not practical.

Storing and processing the navigational data on a server, and allowing the app to connect to that server to fetch the database would considerably alleviate the process. It would also allow users (and not only developers) to use the app.

This issue prevents the project from moving froward, and has not been dealt with mainly due to cost issues.

Screen-off tracking would allow the pilot to switch off the screen and preserve battery, while still receiving and recording GPS data.

For Android, this features is currently implemented using a permanent (ongoing) notification. However, it does not work as expected. Not solution is envisioned for iOS.

Visual Reporting Points (VRPs) are useful, if not mandatory, for VFR flights. They should be added in the database.