Stefano Polloni
Stefano Polloni
I think this is related to https://github.com/pysal/libpysal/issues/474 in that here too the spatial weights class assumes the gdf index is always a default `RangeIndex` reflecting positional indices
> when creating a GeoDataFrame from any other object that a GeoDataFrame, we should create a copy. That is what pandas seem to do now. @martinfleis I initially followed this...
would love to have a fix or workaround for this behavior as well.
just sent those over. By the way, I managed to avoid this problem and successfully scan all the files using the entwine docker container.
using Conda. probably should have mentioned this earlier.
> Anyway, shouldn't that option be False by default to be consistent with the sync version? +1
thanks folks!
> Yeah thanks for the tip @agilgur5! Removing `serviceAccountName` and `executor.serviceAccountName` from my `WorkflowSpec` and adding `executor.serviceAccountName`s with different values to my step templates worked fine for me in Argo...
Hi folks, I'm arriving here after "accidentally" creating a whole new s3 bucket using pandas' `to_csv()` method and having a typo in the bucket name of my s3 uri. (see...