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
Current behavior is that, if a granule name is provided through the --granule-name param, we don't provide the temporal range in the CMR query, even if given by the user. This did make sense previously, before --granule-name wildcards were introduced. Now, this is problematic because the temporal range is still relevant. For instance:
Current behavior is that, if a granule name is provided through the
--granule-name
param, we don't provide the temporal range in the CMR query, even if given by the user. This did make sense previously, before--granule-name
wildcards were introduced. Now, this is problematic because the temporal range is still relevant. For instance:podaac-data-downloader -c SWOT_L2_NALT_IGDR_1.0 -sd 2023-08-05T00:00:00Z -ed 2023-08-06T00:00:00Z -g "SWOT_IPR*" -d ./data
The above search returns way too many granules, because the provided temporal range is ignored.
The text was updated successfully, but these errors were encountered: