Sorting Results

[SomethingCreativeStudios]

I might have missed it in the redoc or github, but it does appear there is a "sort" or "order" param for any of the resources.
Is this expected or is there a common query param object i am missing?

I can limit, and filter but i do not see a way to sort or order the results

[SpeckiJ]

You are correct that there is no standard-mandated way to sort or order the results.

This lack of a "sort"/"order" Parameter is indeed a quirk that we inherited from the OGC API Features Part 1: Core which just mandates a very limited set of parameters (e.g. the limit parameter is mandatory https://docs.ogc.org/is/17-069r4/17-069r4.html#_parameter_limit, but there is no strictly defined way on how pagination should be done).

In actual practice I would expect all Server implementations to enforce ordering based on some (possibly internal) property, at least all Implementations that support some form of Pagination need this to be able to create pages.

[SomethingCreativeStudios]

Okay that makes sense (at least in part to make it adhere to features part 1)

Interesting from a UI perspective as not all Connected System can then sort/order, and unlike pagination there is no common next/prev link to hide that custom implementation