qwat-data-model
qwat-data-model copied to clipboard
proposal: maybe we shouldn't create alternative geometries all the time
Hello
Logic:
- We only make use of the alternative geometries in very few cases (for us at least) but we create the alternative geometries for each pipe etc.
- There's a performance penalty, storage penalty etc., attribute table penalty to load all those extra geometries
Python actions could replace that so that the geometries are created per features.
Maybe your usage differs, and I got this wrong, but I'm keen on finding out your thoughs.
Best regards and thanks
I agree with you.
I think it's a good idea in theory, but too complicated to be really usable and used. And as you point out it is too expensive.
Follow-up. For attribute table opening over WAN .. but with great speed, setting to NULL the alt geometries decreased the opening of the attribute table from 4 seconds to 3 seconds for 27k pipes.
Maybe what we miss here is an edit view for pipes? Loading alternative geometries as additionnal columns in QGIS is a bit useless and slows probably the whole process.
Concerning alternative geometries generation and handling, there's probably some reflexion to have more generally. (bad integration with FME, risk of user error when removing entity and not entity part)
@kandre how is it working with schematic data in QWAT using alternate geometries in your entity?