Max Gabrielsson
Max Gabrielsson
Yes and no. We might add some utility functions in spatial to make it easier to integrate with H3 andI've briefly exchanged a few words with Isaac about DuckDB labs...
Hi! Thanks for reporting this issue. Documentation is still very much in progress, but it's a good idea to maybe add a special section to elaborate more on projections and...
Yes, but note that EPSG:4326 is the same as WGS84, so you don't need the extra projection. I don't know about any GIS tools that take altitude into account when...
Does it work if you export the entire original subquery? The export itself doesnt reallt have any knowledge of what its exporting in this case since there is no geometry,...
FWIW I'm going to look at better supporting this use case tomorrow.
Depending on how you plan to use OSM data you may or may not find the progress in duckdb/duckdb_spatial#90 useful. It's super fast, but it doesn't get you "all the...
I don't think this is possible right now, but it's actually a pretty intriguing idea. DuckDB has some reusable code used by the json/csv/parquet reader functions to handle multiple file...
Hi! Thanks for the nice test-case. We do use GEOS, however st_union_agg, is implemented by iteratively union:ing all the geometries into an accumulator one by one, while it seems to...
Sounds good! I agree the current implementation is a bit lacking due to laziness on my part - I've been meaning to revisit union ops in general to support other...