Support for GEDI v2.1 and integration with DeepTrees🌳 at Helmholtz-UFZ

[thisistaimur]

Hello there, I am from the Community Ecology department at Helmholtz-UFZ, where I am developing/maintaining the DeepTrees OSS python package (https://deeptrees.de) for individual tree crown segmentation. I have been thinking lately of including gediDB (also looking at icesat2DB) into the package as a dependency for grabbing structural and AGB data for post-segmentation analysis of tree individuals. This collaboration would open up a lot of powerful use cases.

My primary concern in this decision is whether the database is expected to be maintained at least in the medium term with newer dataset versions? I would even offer helping out with maintenance whenever possible.

I also wanted to ask wether there is any plan to support GEDI v2.1 data, which has a longer temporal coverage up till 07.2025? I was not able to see anything in the documentation or closed Github Issues
hinting at this. Longer temporal coverage would be crucial to avoid bigger temporal gaps between segmentation images and gedi data.

Thanks!

[simonbesnard1]

@thisistaimur Thanks for reaching out. Yes, the plan is to keep maintaining gediDB and icesat2DB. As for the data through July 2025, it has already been ingested. See the database documentation (https://gedidb.readthedocs.io/en/latest/user/tiledb_database.html)

Hope that helps!

[thisistaimur]

Thanks @simonbesnard1! Then everything is set for an initial integration test with DeepTrees. I will be in touch via email with some initial results in the coming weeks, perhaps its also interesting for you? I am also developing a TileDB-based ecological remote sensing product and perhaps we should align there under the Helmholtz TB we share. This work is together with Ingolf Kühn (UFZ), who works closely with Martin Herold (GFZ) within the TB.

[simonbesnard1]

@thisistaimur That sounds great. Feel free to reach out by email, and happy to help.