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
To support data that does not have time and vertical extents OGC-API EDR defines the datetime and Z parameters as optional.
When querying large data sources which have time and vertical dimensions, client application requests which don't specify the time and vertical query parameters can sometimes only be handled by returning a HTTP 413 error (request entity too large) .
Suggested Resolution
Enhance the EDR specification to use the OpenAPI response to allow individual collections the ability to advertise that query parameters are mandatory when necessary. This would allow client applications to check if a query parameter was required before making a request.
The text was updated successfully, but these errors were encountered:
To support data that does not have time and vertical extents OGC-API EDR defines the
datetime
andZ
parameters as optional.When querying large data sources which have time and vertical dimensions, client application requests which don't specify the time and vertical query parameters can sometimes only be handled by returning a HTTP 413 error (request entity too large) .
Suggested Resolution
Enhance the EDR specification to use the OpenAPI response to allow individual collections the ability to advertise that query parameters are mandatory when necessary. This would allow client applications to check if a query parameter was required before making a request.
The text was updated successfully, but these errors were encountered: