Open MatthewJA opened 3 years ago
My guess it's because of this:
@MatthewJA note that importing geopandas BEFORE importing datacube would allow you to keep using .read_file
, so that's a work around. But it seems like an error in geopandas to be honest. It somehow decides to use normal http for s3 access
dodgy fix when import order can not be controlled is to do this before attempting to read s3 resources:
gpd.io.file._VALID_URLS.discard("s3")
Thanks for following this up with Geopandas!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
In a strange co-incidence, I just encountered this problem today, and can verify that it is still an issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is blocked on the geopandas side.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected behaviour
Actual behaviour
Note that without the datacube import, this code works fine.
Environment information
1.8.4.dev81+g80d466a2 on Sandbox