Skip to content

Align Sort extension with DRAFT OGC API - Records - Part 1: Core #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
philvarner opened this issue Oct 6, 2022 · 2 comments
Closed
Assignees
Milestone

Comments

@philvarner
Copy link
Contributor

https://docs.ogc.org/DRAFTS/20-004.html#sorting-parameter-sortby

Primary issue is the "sortables" endpoint.

@philvarner philvarner added this to the v1.0.0-rc.3 milestone Oct 6, 2022
@philvarner philvarner self-assigned this Jun 6, 2023
@aaime
Copy link

aaime commented Sep 19, 2024

In addition to sortables, the schema for sortby is different, it's a plain list of strings, mimicking the GET syntax:

https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/ogcapi-records-1-building-blocks.yaml#L113

    sortby:
      name: sortby
      in: query
      required: false
      schema:
        type: array
        minItems: 1
        items:
          type: string
          pattern: '[+|-]?[A-Za-z_].*'

@m-mohr
Copy link
Contributor

m-mohr commented May 9, 2025

The schema is not different, it is defined in Recordy for query strings and we use the same schema.
We also define it for POST JSON bodies, which I couldn't find in Records.

Sortables is targeted in #7

@m-mohr m-mohr closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants