Get only the last result in a temporal filter about pg_tileserv HOT 5 CLOSED

The database is re-scanned every time you hit index.html or index.json. If it has the right signature, it'll be picked up.

from pg_tileserv.

pg_featureserv has the sortby and limit parameters (see here). These are standard parameters in the OGC API. Perhaps these could be added to pg_tileserv?

from pg_tileserv.

Yeah, tile format doesn't really have a use for an "order by" so it hasn't been done. That just leaves you the option of writing a function that returns tiles the way you want. Which isn't a bad option, since then you have the full power of SQL available.

from pg_tileserv.

Thanks for the answer.
I guess, you are referring to[this] (https://access.crunchydata.com/documentation/pg_tileserv/1.0.3/usage/function-layers/).
I have never used functions as layers. Is there anything else, I need to do, besides creating the function in postgres?
Will it be auto-discovered?

from pg_tileserv.

pg_featureserv has the sortby and limit parameters (see here). These are standard parameters in the OGC API. Perhaps these could be added to pg_tileserv?

I think, my request is a bit more complex, as it needs a DISTINCT as well.
So the function layer worked perfectly well for me and gives a lot of flexibility.
The only thing I struggled for some hours was the problem with the built-in UI and the visibility of function layers as discussed here.
It is said here, that the name has to be set to default, to be seen in the UI. But the official documentation doesn't state that...
When I named the layer default in the ST_AsMVT function, I saw the data in the UI as well.

from pg_tileserv.