Add a small UI?

[spwoodcock]

• We went to great pains to make the API NodeODM compatible, so WebODM could use it as a backend.
• On reflection, running WebODM is maybe a bit heavy for simple interactions (triggering and viewing jobs), as WebODM has its own queue system etc bundled.
• A lightweight API for ScaleODM might be nice, maybe HTML with WebAwesome, or if more reactivity is needed, then Svelte?

[linear]

TECH-1136

[spwoodcock]

More info on this. While a small UI bundled could be useful, better would probably be to reuse DroneTM UI:

• We have a good imagery uploader already.
• Classify into 'chunks' (tasks) for processing if needed.
• Also removes 'bad' imagery via pre-processing.
• We then send off for processing and monitor the status.
  This is all what an ODM UI probably needs! The flight planning etc is a bonus too.

So within DroneTM, we could possibly divide the UI in two:

1. Drone flight specific portion
2. Imagery processing portion
   These UIs should be visually similar for user continuity, but the key caveat here is that the processing UI could in theory be run standalone with ScaleODM as an ODM UI.

---

Also somewhat related, we discussed an OAM plugin, which will be replaced by the OAM uploader functionality instead: hotosm/openaerialmap#268

[spwoodcock]

Done. We can refine it as needed. Will likely be replaced by hotosm/drone-tm#800 anyway.