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

query masked by WKT area #96

Closed
7yl4r opened this issue Oct 10, 2019 · 3 comments
Closed

query masked by WKT area #96

7yl4r opened this issue Oct 10, 2019 · 3 comments

Comments

@7yl4r
Copy link

7yl4r commented Oct 10, 2019

A common task is how to fetch data masked by an arbitrary region of interest (RoI) polygon.
Ideally the OPeNDAP standard & ERDDAP might allow for submission of a WKT, but masking could also be handled on the client side.

@ocefpaf : what are the first steps towards implementing RoI masking in erddapy?

Additional thoughts:

  1. Should efforts to implement RoI queries be focused on the server or is this client workaround worthwhile?
  2. Is this feature creep? Perhaps masking is a secondary task which should be kept separate from the core functionality of the API.
@ocefpaf
Copy link
Member

ocefpaf commented Oct 29, 2019

We need to implement the griddap URL parser first. Working on that. Let's keep this one open until then. Once we have that using any object that has a _geo_interface_ should be possible.

@MathewBiddle
Copy link

Possibly a server side function in the future.
xref: ERDDAP/erddap#55

@ocefpaf ocefpaf mentioned this issue May 23, 2022
@ocefpaf
Copy link
Member

ocefpaf commented Mar 31, 2023

Based on ERDDAP/erddap#55 looks like a server side function won't happen. However, we can do better with clients and I added an example in #246 to illustrate that. While it is not exactly a server-side precise shape query, it is a minimum data download with later trimming to be match the exact shape.

Closing this for now b/c I think this is the best we can do. Unless someone has a better idea for a PR.

@ocefpaf ocefpaf closed this as completed Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants