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
Currently, http://coverageapi.org/ns#api is used as a generic term for interfacing with a server API with the help of URL templates, as used by Hydra. Hydra itself currently defines only the "search" term and possibly in the near future "filter" (subproperty of "search"), however this doesn't fit to all coverage API use cases, since we also have operations like "embedding" and "subsetting". Looking at WCS as a reference, there are many more parameters that a server could offer like reprojection and interpolation.
It would be better to have a more concrete term than just "api". Maybe "query"? The term must be able to capture most concepts offered by common coverage data APIs, which are filtering, subsetting, transformation, ...
The text was updated successfully, but these errors were encountered:
Currently,
http://coverageapi.org/ns#api
is used as a generic term for interfacing with a server API with the help of URL templates, as used by Hydra. Hydra itself currently defines only the "search" term and possibly in the near future "filter" (subproperty of "search"), however this doesn't fit to all coverage API use cases, since we also have operations like "embedding" and "subsetting". Looking at WCS as a reference, there are many more parameters that a server could offer like reprojection and interpolation.It would be better to have a more concrete term than just "api". Maybe "query"? The term must be able to capture most concepts offered by common coverage data APIs, which are filtering, subsetting, transformation, ...
The text was updated successfully, but these errors were encountered: