Github user Omkar20895 commented on the issue:
https://github.com/apache/climate/pull/411
Hi @lewismc 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.
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, you wouldn't call the
granule_subset WS unless you want to subset the dataset granule right? So if
the user wants to download the whole dataset he can use the present
functionality we have in ocw or otherwise he can use the new function that we
can write(only if you agree with this).
> I also propose to utilize podaac.subset_status such that we can update
the user view console output how long their request is going to take...
something like what anaconda and pip do
For this we need to answer a basic question, how long does a granule subset
job submitted to PO.DAAC takes to complete? This is all that I have in my mind,
please let me know your thoughts.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
