Is your feature request related to a problem? Please describe.
When performing a CQL query you need to know the column names in postgres, however pygeoapi hides these from end users, and calls them geometry & id
Describe the solution you'd like
@volcan01010 found SQL Alchemy can do the renaming of reflected columns: https://docs.sqlalchemy.org/en/14/orm/mapping_columns.html#automating-column-naming-schemes-from-reflected-tables
Also @ximenesuk suggested ID's should be integers
Then when doing CQL can use geometry & id without having to know the actual column names
Is your feature request related to a problem? Please describe.
When performing a CQL query you need to know the column names in postgres, however pygeoapi hides these from end users, and calls them geometry & id
Describe the solution you'd like
@volcan01010 found SQL Alchemy can do the renaming of reflected columns: https://docs.sqlalchemy.org/en/14/orm/mapping_columns.html#automating-column-naming-schemes-from-reflected-tables
Also @ximenesuk suggested ID's should be integers
Then when doing CQL can use geometry & id without having to know the actual column names