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
{{ message }}
This repository has been archived by the owner on Jun 14, 2021. It is now read-only.
Hi everyone, really enjoy the project, very useful!
There seems to be a bug in the default argument of the start_date in the sentinel2 search function:
To reproduce:
>>>fromaws_sat_api.searchimportsentinel2>>>utm=16>>>lat='S'>>>grid='DF'>>>full_search=False>>>level='l1c'>>>s2_meta=sentinel2(utm, lat, grid, full_search, level)
Traceback (mostrecentcalllast):
File"<stdin>", line1, in<module>File"c:\users\mark.boer\documents\git\aws-sat-api-py\aws_sat_api\search.py", line183, insentinel2raiseValueError(f"Start date out of range {start_date.year} < 2015.")
ValueError: Startdateoutofrange2014<2015.
Probable solution:
I live in the Netherlands, I think this problem lies in the fact that live in a timezone with a positive timezone offset.
I think this issue can be solved by adding a tzinfo=timezone.utc to search.py line 172
start_date = start_date or datetime(2015, 1, 1, tzinfo=timezone.utc)
I'll create a PR later today :)
The text was updated successfully, but these errors were encountered:
Hi everyone, really enjoy the project, very useful!
There seems to be a bug in the default argument of the start_date in the sentinel2 search function:
To reproduce:
Probable solution:
I live in the Netherlands, I think this problem lies in the fact that live in a timezone with a positive timezone offset.
I think this issue can be solved by adding a
tzinfo=timezone.utc
to search.py line 172I'll create a PR later today :)
The text was updated successfully, but these errors were encountered: