Skip to content

support the profile parameter for detailed info on the requested encoding #2383

Closed as not planned

Description

@pvgenuchten

Is your feature request related to a problem? Please describe.

for some specialised formats such as jsonfg, ogc suggests to reuse the application/geo+json encoding, but extend it with a profile parameter to indicate the json flavour.

Describe the solution you'd like

pygeoapi would parse the profile to understand which json to return. This functionality will also be relevant for other json flavour, such as stac, ogcapi-records, cov-json, etc

the profile can also de introduced as query parameter, to override the accept header, ?f=geojson&profile=jsonfg, however a shortcut f=jsonfg also makes sense.

Additional context

https://docs.ogc.org/is/21-045r1/21-045r1.html#_using_a_json_fg_client

This came up as part of #2376

Activity

  1. github-actions commented on Sep 27, 2026

    @github-actions

    This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.

  2. github-actions commented on Oct 4, 2026

    @github-actions

    As per RFC4, this Issue has been closed due to there being no activity for more than 90 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requeststaleIssue marked stale by stale-bot

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions