Closed webb-ben closed 1 month ago
@webb-ben yes, that's the intended behaviour, since there is no way from a routing perspective to determine whether an .../items
endpoint is EDR or OGC API - Features without special handling (which would be too early in the codepath/lifecycle).
Perhaps this can be documented accordingly, then.
Description When executing EDR /items queries, the requests never reach the EDR provider because the /items Flask route always defaults to using an OAF provider instead of the intended EDR provider.
Steps to Reproduce
Expected behavior The /items query should be processed by the configured EDR provider, not the Features provider.
Screenshots/Tracebacks If applicable, add screenshots to help explain your problem.
Environment
Additional context Note I am able to seamless run both an EDR and Features provider by providing configurations for both providers, as such the EDR
/items
links are successfully resolved by the feature provider. @tomkralidis is this the intended behavior for pygeoapi?