You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 6, 2023. It is now read-only.
We have a layer called "MIV-Zählstelle" with an attribute "Anzahl Fahrstreifen". This attribute only contains numbers and is also stored as a number in the database. If I do a getFeature-request over a couple of them and sort "Anzahl Fahrstreifen", it is not recogniced as sorting numbers.
Instead of 0,1,2,4,6,7,10 it is 0,1,10,2,4,6,7.
We also tried with "gml_type" "auto", but it did not work. What can we do?
gml_types
(Optional) If this field is “auto” then some input feature drivers (ie. OGR, POSTGIS, ORACLESPATIAL and native shapefiles) will automatically populate the type, width and precision metadata for the layer based on the source file. Currently this is only used for OGR based output formats, not the WFS GML2/GML3 output.
We have a layer called "MIV-Zählstelle" with an attribute "Anzahl Fahrstreifen". This attribute only contains numbers and is also stored as a number in the database. If I do a getFeature-request over a couple of them and sort "Anzahl Fahrstreifen", it is not recogniced as sorting numbers.
Instead of 0,1,2,4,6,7,10 it is 0,1,10,2,4,6,7.
We also tried with
"gml_type" "auto"
, but it did not work. What can we do?see https://github.com/camptocamp/baselstadt_mapbs/issues/67
The text was updated successfully, but these errors were encountered: