This is only in regard to the UI component! Processing with ODM + NodeODM + WebODM on Windows running natively will require quite more work and there’s no ETA for that (but we’d welcome attempts).
Allthough we claim on the README that WebODM can run on Windows natively, it’s been a while since I’ve tried to make it run there. Happy to say it still works (after some tweaks).
Something I’m attempting to figure out in parallel with trying to get ODM/WebODM working natively on Alpine Linux.
These tweaks look like they’ll help a lot!
GRASS engine and workers running natively.
Using OsGeo4W components? That might make it easy to hook into as I always have QGIS installed on any machine I touch.
Nop, piggy-backing on GRASS GIS python’s install.
Absolutely is a game-changer!
Try it out, let me know what you think: https://webodm.net/static/downloads/WebODM_Setup.exe
Looks amazing! Is the collapsed python environment restructure something you’re looking to carry into the other *ODM codebases to reduce complexity?
Probably not, it’s better to separate the Python environments and this was done out of necessity.
Does native WebODM for Windows - WebODM Lighting (from https://webodm.net/static/downloads/WebODM_Setup.exe) free for commerce use? Can I use this with nodeodm running on my own server for commercial purposses?
Yes, all the tools in the ecosystem are free for commercial use under the AGPL. The only obligation under the AGPL that you have is distribution of any changes to the software to your users.
(I am not a lawyer)
My previous question is about this:
it’s not AGPL, i think…
The installer program is not AGPL, but the software installed by it (WebODM) is.