Skip to content

[ENH] Put the geometry field of the qwat_od.valve table BEFORE all other geometry fields. #380

@nicolas-sitylb

Description

@nicolas-sitylb

Hello,

What is the purpose of the handle_geometry field in the qwat_od.valve table:

ALTER TABLE qwat_od.valve ADD COLUMN handle_geometry geometry(PointZ,:SRID);
?

If the geometry field in the qwat_od.valve table is intended to store the real geometry of the features and if the importance of the handle_geometry field is less than the geometry field in this table, I would suggest to place the geometry 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 currently handle_geometry and because it occurs to be empty in most data sets which store the real geometry of features in the geometry column (and because such other software doesn't offer a solution to manually catch the real geometry), I would suggest to put the geometry field BEFORE all other geometry fields in the qwat_od.valve table.

Thanks.

Warm Regards.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions