Saijin-Naib

What would be needed to describe each scale constraint? XYZ and maybe a "constraint ID", so we know which two manual tie points are being used as a scale constraint...

I see you're calling out specifically non-georeferenced data, but they can still be incredible helpful in ensuring accurate scaling for georeferenced data. Would your proposal allow that as well?

How would that be managed if one wants to have both an inclusion and exclusion boundary? A field in the GeoJSON or other input file with a true/false (0/1) value...

> > > NodeODM already has progress bars that show upload progress? Or this is something WebODM should add? WebODM/Lightning clients in the Project/Task management screen. I wasn't sure if...

How about AVIF textures? We'd have very advanced compression that would outperform other lossy compression, support for arbitrary band numbers, and support for lossless alpha as well as optional lossless...

Seemingly a ```./webodm.sh rebuild``` resolved the missing icons, if that helps any.

Have you observed this behavior with Firefox or Epiphany on Linux as well?

I've fixed the file filter for another file, so I'll work on the same for this. It should just be transparent when I have it done right.

WebODM Docker (1369x768 host resolution:  

Would it be possible to have the progress bar divide into "bins" per step of the pipeline to sort of de-mystify the progress a bit? Similar in concept to this?...