Is the output produced by the sensor RGB or a single value per pixel?
Is the output produced by the sensor RGB or a single value per pixel?
Is it really that stable and flawless in terms of updates?
Because I'm sat here with ZFS, snapshotting and replication configured and wondering why people scare others off of it when the tools to mitigate issues are all free and should be used anyway as part of a bog-standard self-hosted stack.
I myself am one of them, but I attribute that to the fact that this is a graduate version of an undergrad class I took two years ago (but have to take the grad version for degree requirements). Instead, I've been skimming the posted exercises and assessing myself which specific topics I need to brush up on.
With a bit of digging, I believe this is the source Google Doc: https://docs.google.com/document/d/1BUCGdZCe8JevGYF3pJ4ZjPqp...
Been working on this as a new way to find, explore, and view old historical maps and aerials of my area. Still heavily in development but have been surprised by some early traffic stats (1-2K organic uniques / mo and growing 200%+ m/m right now)
Hoping to add in more advanced map tooling within the next week or 2, including new basemap options, 3d terrain view, and then a proper search box which I've been pushing off for far too long
i wonder if what im after is like some kinda dead simple easy to use declarative front end api that can be built from a backend, something like streamlit or nicegui that has great ergonomics and is easy to maintain but scales better and has better state mgmt than streamlit & puts all the power of a general purpose programming language right there with it. i love compiled things i hate setting up environments with runtimes and stuff.