Jorge Samuel Mendes de Jesus

I also had the same with `depths` that were in `cm` with 100 being first and not 20. The only solution was to disable `` and rely on the SQL...

@AndyLicht Thank you for the tips: I had already: `"gml_types" "auto"` Made a test with setting my `upper_depth` attribute (the one being sorted on by `SortBy`) `"gml_upper_depth_type" "Integer"` But no...

@pka: - Any updated on sqlite3/mbtiles implementation ?

workflow guidelines and code structure recommendations: https://github.com/geopython/pygeoapi/wiki/Code-development-workflow

@jkreft-usgs From your last comment, then the idea would be for a generic RBDMS dataprovider based on SQLAlchmey (or another ORM).

On the [OGC feature core standards - collections](https://docs.opengeospatial.org/is/17-069r3/17-069r3.html#_collections_), we have an indication of TRS on the json response. I see on the code https://github.com/geopython/pygeoapi/blob/6d1dcece0e9a40ef072b0e2b7828636090193c7f/pygeoapi/api.py#L374 that we set TRS, if present...

@tomkralidis refactored the code https://github.com/geopython/pygeoapi/commit/8a65087eefce7da8b2b2f52169cb96dfae8f82a3

This requires changes on the `wsgi.py` file, part has been implemented here: https://github.com/bird-house/flyingpigeon/issues/240

I have tested and tried to understand as maximum as I could, as far as could understand and IMHO. I have some comments concerning this PR - We should keep...

During my initial tests the docker containers where created. I will make a more extensive check to determine why they are not connecting