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 notes on limitations of OpenSearch Geo & Time #5

Open
letmaik opened this issue Jan 31, 2016 · 0 comments
Open

Add notes on limitations of OpenSearch Geo & Time #5

letmaik opened this issue Jan 31, 2016 · 0 comments

Comments

@letmaik
Copy link
Contributor

letmaik commented Jan 31, 2016

OpenSearch Geo & Time has a very broad scope and is meant for describing the URL structure of search engines with spatial and/or temporal filtering functions. The terms defined in that spec are restricted to WGS84 coordinates and RFC3339 Gregorian times. In coverage APIs there may be different requirements such as:

  • using spatial coordinates in the native CRS of the coverage (or the reprojection CRS as in W*S)
  • searching for times beyond the 4-digit year limit (paleoclimate datasets)
  • having more than one time dimension (model time and forecast time in weather forecasts)

The OpenSearch Geo & Time terms may be used directly for collection filtering if the above restrictions do not apply. However, for subsetting a coverage, the terms may only be used indirectly as the syntax for (currently) custom terms, since filtering in general is not subsetting and both operations may be used in a single API query, hence the need to differentiate between them. As noted in #4, the distinction between filtering and subsetting is not always clear though (correct me if I'm wrong).

The above notes should be added to the spec to guide implementers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant