Skip to content
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

Add query option for ?f=coveragejson #1801

Open
C-Loftus opened this issue Aug 27, 2024 · 2 comments
Open

Add query option for ?f=coveragejson #1801

C-Loftus opened this issue Aug 27, 2024 · 2 comments
Labels
enhancement New feature or request stale Issue marked stale by stale-bot

Comments

@C-Loftus
Copy link
Contributor

Describe the solution you'd like

In EDR some endpoints return either geojson or coveragejson.

  • For instance, /locations returns geojson but /locations/{id} returns coveragejson.

A user may want to get a different formatting of json output other than the default. However, it is my understanding that pygeoapi processes ?f= before it reaches the provider so it is not possible to switch on the value of the format and return a user-specified format.

  • We can get both json and jsonld just since it is hard coded as another option, but this is not possible for coveragejson

Describe alternatives you've considered

  • pass the format query param (f=) as an argument for the provider that the provider can optionally use to change the type of json
  • hard code covjson similar to json vs jsonld as another json option

Additional context

Similar to how having the option to output raw json is useful to debug jsonld, having the output to output geojson alongside covjson as another format is also useful for debugging.

SInce coveragejson is less common and more complicated, it is useful for a reference to be able to query both the geojson and coveragejson representation of the same resource and the differences in expressiveness.

cc @webb-ben

@C-Loftus C-Loftus added the enhancement New feature or request label Aug 27, 2024
@C-Loftus
Copy link
Contributor Author

C-Loftus commented Oct 1, 2024

Believe this is related to #1821

Copy link

github-actions bot commented Jan 5, 2025

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.

@github-actions github-actions bot added the stale Issue marked stale by stale-bot label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Issue marked stale by stale-bot
Projects
None yet
Development

No branches or pull requests

1 participant