You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Using application/geo+json as the media type (the correct media type for GeoJSON) in an Accept: header results in a 500 error (with Skymantics Aviation API deployment).
Steps to Reproduce
Steps to reproduce the behavior:
pygeopai hardcodes the media type as application/json instead of application/geo+json. So when you query specifying the media type as application/geo+json, pygeoapi does not recognize it as a valid media type and returns an error. You can see the piece of code in api.py, line 101:
The solution can be as simple as replacing application/json with application/geo+json but it might generate issues with existing applications. I think it is a good idea to open the debate in the broader community.
Description
Using
application/geo+json
as the media type (the correct media type for GeoJSON) in anAccept:
header results in a 500 error (with Skymantics Aviation API deployment).Steps to Reproduce
Steps to reproduce the behavior:
and
both result in a 500 internal server error.
However, these requests from demo.pygeoapi.io work fine:
Expected behavior
Negotiating
application/geo+json
should work fine, as it is the correct media type for GeoJSON.Screenshots/Tracebacks
Environment
Skymantics Aviation API ( Powered by pygeoapi logo 0.11.dev0 )
Additional context
In the context of Testbed 18 / SWIM task.
@skyNacho provided this additional feedback:
pygeopai hardcodes the media type as
application/json
instead ofapplication/geo+json
. So when you query specifying the media type asapplication/geo+json
, pygeoapi does not recognize it as a valid media type and returns an error. You can see the piece of code in api.py, line 101:The solution can be as simple as replacing
application/json
withapplication/geo+json
but it might generate issues with existing applications. I think it is a good idea to open the debate in the broader community.@tomkralidis
The text was updated successfully, but these errors were encountered: