Olivier Courtin

Still an open ticket as i still need to: - handle namespace more strictly for property too (right now a property namespace prefix could be shared with other layers) -...

Thanks for this tip Thomas ! Will have to look at it... For now i don't feel the need to add a dependancy only for memory usage, but maybe this...

I don't get how the file provided is helpfull, could you provide a diff ?

After looking a bit further: - Right now a table without geometry/geography column is just ignored - Even a layer with geometry column but with an exclude_items on the geometry...

Thanks Thomas for this input, i close this ticket accordingly

Hi @jeanfeydy I hope first your thesis redaction is performing as well as possible... And as you replied that ImageLoss and VolumeLoss are WIP, could you publish them anyway -as...

Python API sounds like a good idea. And as long as we can, keeping the same interface and abilities for both PostGIS and Python API, too. For PostGIS, if new...

@remic Yeap the Pl/Python way is far better/clever than parsing back the chain SFCGAL side (i.e SF_SFCGAL_chained) Thanks Remi for this input !

@vmora @remic Humm, what kind of issue to not use Pl/Python in production ?

@remic GRANT EXECUTE give rights to use an already existing function GRANT CREATE FUNCTION give rights to create a function (inside schema/database...) So it could be safe in a DBA...