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
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:
Should efforts to implement RoI queries be focused on the server or is this client workaround worthwhile?
Is this feature creep? Perhaps masking is a secondary task which should be kept separate from the core functionality of the API.
The text was updated successfully, but these errors were encountered:
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.
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.
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:
The text was updated successfully, but these errors were encountered: