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
Currently STID/Echo do not support calls to the API as application so we don't have a good way of having flotilla scheduling missions autonomously.
Have a dialog with STID and ECHO on what teh best solution here is.
Currently if the operator makes changes on a mission in the mission planner, it needs to manually fetch the mission from echo with the predefined mission button for the changes to take place in the auto scheduling of missions.
How will this change existing functionality?
Mission tasks are autonomously updated by flotilla when the mission is scheduled.
The text was updated successfully, but these errors were encountered:
Have asked ECHO Team to look into removing the call to STID from the endpoint. So we would get the STID coordinates for the target when creating/setting to ready a mission (since is this done by the user) and we would assume these coordinates don't change.
Therefore when reading in the missions these positions would be stored already and no need to be calling the STID API.
Describe the improvement you would like to see
Currently STID/Echo do not support calls to the API as application so we don't have a good way of having flotilla scheduling missions autonomously.
Have a dialog with STID and ECHO on what teh best solution here is.
Currently if the operator makes changes on a mission in the mission planner, it needs to manually fetch the mission from echo with the predefined mission button for the changes to take place in the auto scheduling of missions.
How will this change existing functionality?
Mission tasks are autonomously updated by flotilla when the mission is scheduled.
The text was updated successfully, but these errors were encountered: