Giovanni Manghi

> maybe also due to a lizmap cache issue. > the slowdown occurs mainly when all the caches are empty, that's when the project is loaded for the first time....

> On my local setup, GetLegendGraphic request is not cached and still very long even after first loading... And anyway in my opinion this is not a caching issue, requesting...

> but when I edit it in Lizmap, it doesn't work @Mavialle does it works in qgis?

> and not on TinInterpolation @Meibes this tool does not allow to use layers that are not loaded in the project even when used outside of a model, so this...

> is the limitation somewhere in interpolationdatawidgetbase.ui because the combobox cmbLayers has the class QgsMapLayerComboBox and is not filled like other layerComboboxes from other processing algorithms? is a question for...

> Nice to know. Do you think you can provide a pull request ? @cfsgarcia agree, this should go into LMWC code.

For tickets closed for missing feedback, can it be used a different label other than "not planned"? It is not really what is going on: a ticket can be perfectly...

> PostGIS layers can't be saved in cache, but vector layers can. @Oxsw1ng not sure I understand, can you elaborate? Sorry for asking, this is something that I think is...

> because when you generate capabilities for the project, you dont see the PostGis layers @Oxsw1ng I guess you mean this, right?  If the above script/command really does not...

@Oxsw1ng this adds up to my ticket https://github.com/3liz/lizmap-web-client/issues/3696 where I placed a few observations on caching along time, but that didn't get much attention.