Github user lewismc commented on the issue:
https://github.com/apache/climate/pull/411
@Omkar20895
> I don't think replacing extract_l4_granule is a good idea, because this
function is a real time function and it downloads the dataset right away to
create an ocw dataset.
OK, yes that sounds logical. I mean, if the user wants to download one
entire granule then they should be able to do exactly that... so retaining the
podaac.extract_l4_granule is good.
> One thing I can suggest is instead of replacing extract_l4_granule with
granule_subset, we can write and additional function that will make use of
granule_subset, in this way the user has a flexibility,
ACK
> you wouldn't call the granule_subset WS unless you want to subset the
dataset granule right?
Correct... or a slide of several granules e.g. do an aggregation.
> how long does a granule subset job submitted to PO.DAAC takes to
complete?
I am going to say that the time will increase in a linear fashion depending
on the number if granules submitted within the JSON request. The PO.DAAC
granule_subset webservice is using OPenDaP's aggregation functionality now so
we are one of the first primary consumers of data in this fashion. I suppose we
will find out once we use the service more... this is also information we can
provide back to the PO.DAAC team.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
