Thanks for sharing- particularly the Lonboard integration, python libraries converting to GeoJSON before rendering slows my workflows down so much. Often open geospatial data is supplied in formats other than GeoJSON- if you're planning to release more DuckDB geospatial content it would be cool to explore some of the other formats, particularly Shapefile and GeoPackage as the two other most common formats. Since GeoPackage is based on SQLite, DuckDB can attach the file as a database and read/write transactionally! I ❤🦆!!!!!!
Would we have full fledged projects as tutorials in the coming days? Maybe, integrating Duck DB with Spark, Kafka, Apache Druid, Apache Pinot, etc? I would love to see tutorials because, you're a genius tutor, I expect nothing less.
@@motherduckdb thank you, Mehdi is such a hero. But as a feedback, many people want tutorials from scratch and that's how technologies get popular. One example, is Web Development framework RedwoodJS, their developer came with the most unique idea to encapsulate React JS and condense it but for 3 years of consistently asking them to publish their tutorials instead of just live streams, with no courses or tutorials available, nobody even knows about that framework anymore and NextJS has almost taken all the share in the React world. I wish if such tutorials "from scratch" are developed so that even the novice ones take note and novice people turn professional and give suggestions about platforms to their respective teams for a stack. Thanks for responding.
Hello, let´s think about those organizations that have outputs in GEOPACKAGE. Would it be possible to see a video on how to perform a pipeline to convert geopackages to geoparquet efficiently, use basic spatial functions on DuckDB such as dissolve geometric features based on columns (group by, geometries), and store them on disk as geoparquets and geopackages ? Polygons geometries are challenging, as their geometry column can be huge. Exporting back to geopackage is important because , as mention before, organizations still use geopackage, thus, they expect geopackages . Maybe this is a good use case. Thank you.
Thanks for sharing- particularly the Lonboard integration, python libraries converting to GeoJSON before rendering slows my workflows down so much. Often open geospatial data is supplied in formats other than GeoJSON- if you're planning to release more DuckDB geospatial content it would be cool to explore some of the other formats, particularly Shapefile and GeoPackage as the two other most common formats. Since GeoPackage is based on SQLite, DuckDB can attach the file as a database and read/write transactionally! I ❤🦆!!!!!!
Thanks for the feedback, we'll look into this !
Thank you for the video. It’s so clear.
I signal that Lonboard has currently an issue (version 0.9 and 0.10) and it is impossible to see the maps.
Would we have full fledged projects as tutorials in the coming days?
Maybe, integrating Duck DB with Spark, Kafka, Apache Druid, Apache Pinot, etc?
I would love to see tutorials because, you're a genius tutor, I expect nothing less.
We'll do our best, certainly more projects based tutorial!
@@motherduckdb thank you, Mehdi is such a hero.
But as a feedback, many people want tutorials from scratch and that's how technologies get popular.
One example, is Web Development framework RedwoodJS, their developer came with the most unique idea to encapsulate React JS and condense it but for 3 years of consistently asking them to publish their tutorials instead of just live streams, with no courses or tutorials available, nobody even knows about that framework anymore and NextJS has almost taken all the share in the React world.
I wish if such tutorials "from scratch" are developed so that even the novice ones take note and novice people turn professional and give suggestions about platforms to their respective teams for a stack.
Thanks for responding.
Hello, let´s think about those organizations that have outputs in GEOPACKAGE. Would it be possible to see a video on how to perform a pipeline to convert geopackages to geoparquet efficiently, use basic spatial functions on DuckDB such as dissolve geometric features based on columns (group by, geometries), and store them on disk as geoparquets and geopackages ? Polygons geometries are challenging, as their geometry column can be huge.
Exporting back to geopackage is important because , as mention before, organizations still use geopackage, thus, they expect geopackages . Maybe this is a good use case. Thank you.
Thanks for the sharing the lonboard library. By the way, how to save the map as html file like folium
Lonboard has a CLI that you can use to export to static HTML : developmentseed.org/lonboard/latest/cli/
💖💖💖💖