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
The Kaggle python environment currently pins geopandas==v0.14.4 which is now 16 months old, saying the learntools are broken with higher versions. Is this still true? Has anyone checked lately?
It also uses pyarrow==19.0.1 but the most recent version is 21.
Motivation
This is starting to impact the ability to use new geospatial functionality. E.g. PyArrow v21 has added native support for geospatial data types in Parquet:
OSError: Error creating dataset.
Could not read schema from 'pudl.catalyst.coop/nightly/out_censusdp1tract__states.parquet'.
Is this a 'parquet' file?: Could not open Parquet input source 'pudl.catalyst.coop/nightly/out_censusdp1tract__states.parquet': Metadata contains Thrift LogicalType that is not recognized
While the same expression with geopandas 1.1.1 + pyarow 21.0.0 works fine.
However, if the geoparquet output is generated using pyarrow v20.0.0 (before native geoparquet support) + custom b"geo" metadata, the older geopandas & pyarrow setup is able to read them.
Activity
[-]Update to geopandas 1.x[/-][+]Update to geopandas 1.1.x[/+][-]Update to geopandas 1.1.x[/-][+]Update to geopandas v1.1.x, pyarrow v21[/+]Revert to pyarrow v20 for compatibility with stale Kaggle geopandas
Revert to pyarrow v20 for compatibility with stale Kaggle geopandas (#…
zaneselvans commentedon Feb 27, 2026
It looks like a newer Kaggle environment has updated to a modern version of geopandas (v1.1.2):
However, the pyarrow version seems to have been rolled back even further to v18.1.
zaneselvans commentedon Jun 20, 2026
Kaggle updated their environment a while ago, and this is no longer an issue.