[gdal-dev] What are vector field width and precision good for?

Sean Gillies sean.gillies at gmail.com
Sat Oct 5 16:32:18 PDT 2024


Even,

Would the defaults result in overly large attribute files? By a small
amount or an excessive amount? Or would the defaults result in truncation
of values?

On Sat, Oct 5, 2024 at 4:48 PM Even Rouault <even.rouault at spatialys.com>
wrote:

> Sean,
>
> > What are vector field width and precision good for in 2024? These
> > concepts were inherited from MS Access via Shapefile, I believe. I've
> > been wondering if I can stop supporting them in my Fiona project
> > without breaking workflows badly. Numpy data types don't have width
> > and precision. Neither do, for example, Parquet and Arrow.
> >
> > Anybody using these for anything crucial?
>
> If Fiona had only a read side you could likely ignore them.  But writing
> all those formats (shapefile, mapinfo, etc.) require setting those
> properties. If you don't specify them, the OGR drivers will use some
> defaults, that might not always be appropriate.
>
> Even
>


-- 
Sean Gillies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20241005/b4c449ad/attachment.htm>


More information about the gdal-dev mailing list