Open nicolas-sitylb opened 10 months ago
@3nids @tudorbarascu @kandre @tproduit is anyone actively using this handle_geometry attribute?
@nicolas-sitylb for your information this bother me since day one I got onto QWAT project :
This is my initial issue where you can find interesting workarounds but I think it should be tackled with the next release of QWAT.
@3nids @tudorbarascu @kandre @tproduit is anyone actively using this handle_geometry attribute?
Sorry for the late reply, but as the issue it is still open, I confirm that we are currently not using it.
Hello,
What is the purpose of the
handle_geometry
field in theqwat_od.valve
table: https://github.com/qwat/qwat-data-model/blob/d552ec9567a059155d2c1bd78c7425eacc7efbf3/ordinary_data/valve/od_valve.sql#L23 ?If the
geometry
field in theqwat_od.valve
table is intended to store the real geometry of the features and if the importance of thehandle_geometry
field is less than thegeometry
field in this table, I would suggest to place thegeometry
field BEFORE all other geometry fields.Why?
Because some software is unfortunately not able to deal with other than the very first geometry column encountered in a PostGIS table. Therefore, as that very first geometry column in the
qwat_od.valve
table is currentlyhandle_geometry
and because it occurs to be empty in most data sets which store the real geometry of features in thegeometry
column (and because such other software doesn't offer a solution to manually catch the real geometry), I would suggest to put thegeometry
field BEFORE all other geometry fields in theqwat_od.valve
table.Thanks.
Warm Regards.