> Usually new data is generated regularly
This part was not obvious. In a lot of cases geodata is mostly stable and reads/searches dominate over appends. And that’s why we keep this in DB (usually postgis, yes).
So DuckDB is optimised for very different use case and it is not always obvious when it’s mentioned
But DuckDB works just as well with static data.
This is the more trivial use case (static data, heavy reads) and DuckDB is absolutely optimized for this use case.
DuckDB also provides a vectorized, parallelized engine. When I run a query all of my 32 cores light up on htop.