Army Corps
From: Michael Smith
Date: Saturday, July 26, 2025 at 3:53 PM
To: Even Rouault ,
Subject: Re: [gdal-dev] Timestamp cast error in GDAL Parquet Directory with
sqlite dialect
It is the same schema but writing the different files with must be optimizing
the timestamps and adj
error just reading with pyarrow and geopandas.
Mike
--
Michael Smith
RSGIS Center – ERDC CRREL NH
US Army Corps
From: Even Rouault
Date: Saturday, July 26, 2025 at 3:42 PM
To: Michael Smith ,
Subject: Re: [gdal-dev] Timestamp cast error in GDAL Parquet Directory with
sqlite
Michael,
are you sure this is the *same* schema ? From the error messages (which
comes from libarrow-compute itself), it would seem there's a mix of
timestamp in microsecond and timestamp in nanosecond, and that the
algorithm in libarrow tries to homogenize things and an overflow occur.
If 23
I have a collection of parquet files all with the same schema, different stac
collections written using geopandas to parquet.
When I query at the cli or in python for a directory of parquert files using
sql I get timestamp casting errors
gdal vector info -i PARQUET:s3://mybucket/stac/mds/r
