Skip to content

Conversation

rouault
Copy link
Contributor

@rouault rouault commented Sep 18, 2025

Overview

Cf

Dependency policy (RFC2)

  • I have ensured that this PR meets RFC2 requirements

Updates to public demo

Contributions and licensing

(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)

  • I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution
  • I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines

Cf

- OGC API Features - Part 1 (https://docs.ogc.org/is/17-069r4/17-069r4.html#_api_definition_path_rootapi_link)
  para 7.3.1, permission 1: "it MAY be hosted as a sub-resource to the
  base path of the API, for example, at path /api"

- OGC API Common Part 1 (https://docs.ogc.org/is/19-072/19-072.html#_6f30c0b2-ff4c-4c38-8d51-bd124f4b76cc)
  para 9.2, Recommandation 15.A: "The server SHOULD support the HTTP GET operation on the URI {root}/api."
@tomkralidis tomkralidis self-requested a review September 18, 2025 10:27
@tomkralidis
Copy link
Member

@rouault is /openapi breaking any functionality (given the recommendations and permissions [but not requirements] from OGC API - Features / OGC API - Common)?

@tomkralidis tomkralidis added the OpenAPI OpenAPI label Sep 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OpenAPI OpenAPI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants