Pieter Roggemans
Pieter Roggemans
Indeed complicated. How about using the first row as heuristic? - if no timezone: assume no timezone for everything. If other rows would have a timezone, convert everything to the...
> > How about using the first row as heuristic? > > In some cases there might be performance implication even in just reading one row (thinking of datasets with...
@rouault thinking a bit further on this... would it be possible to instead of discovering the (lack of) timezone up-front per table/layer to rather do it when actually reading the...
> > hat will by default return values converted to UTC if there weren't stored as UTC in the GeoPackage > > was forgetting the case of unknown timezone or...
I can conform your findings @brendan-ward . If you install geopandas and its dependencies using conda-forge, it works fine as the LIBKML driver is being installed that way, and if...
>> Maybe linked to [#444](https://github.com/geopandas/pyogrio/issues/444) if I understand your answer correctly Yes, it seems to be the same underlying issue: the LIBKML GDAL driver not being available in the pyogrio...
As Kyle said, please try with `read_dataframe(..., use_arrow=True)`...
I had a further look into this, and it seems like the /vsizip/ file system handler obfuscates the ssl error. I opened an issue for this in the GDAL issue...
Has been fixed in https://github.com/OSGeo/gdal/pull/12602, so once GDAL 3.11.1 is released this kind of problem will give a clearer error message.
In the mean time GEOS 3.12.2 became available via conda, and the error is still the same.