You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the improvement you would like to see
It should be possible to update the map for a missionrun without having to change all past missionruns as well. One way is to link a missiondefinition to a MapMetadata instead of a missionRun. Another is to make MapMetadata not an owned property but instead its own table. Both of these options will make it much easier to rename maps or to change their boundaries of transformation matrices.
How will this change existing functionality?
It will make it much easier to update maps as they will not be tightly coupled to previous missionruns.
How will this improvement affect the current Threat Model?
N/A
The text was updated successfully, but these errors were encountered:
Describe the improvement you would like to see
It should be possible to update the map for a missionrun without having to change all past missionruns as well. One way is to link a missiondefinition to a MapMetadata instead of a missionRun. Another is to make MapMetadata not an owned property but instead its own table. Both of these options will make it much easier to rename maps or to change their boundaries of transformation matrices.
How will this change existing functionality?
It will make it much easier to update maps as they will not be tightly coupled to previous missionruns.
How will this improvement affect the current Threat Model?
N/A
The text was updated successfully, but these errors were encountered: