On mardi 5 juin 2018 08:12:59 CEST Martin Landa wrote: > Hi, > > there is an issue with VFK driver when interpreting numeric values. > Attribute type in VFK data is defined by string like > > &BVLA;PODIL_CITATEL N30;PODIL_JMENOVATEL N30; > > where VLA is layer name, N -> numeric; 30 -> width > > Currently such data types are interpreted as bigint by the driver. But > the value can be apparently (tested almost on full Czech cadastre > dataset) larger that bigint in reality, eg. > > &DVLA;...109690709117941111470877379;221486618060854273218000000;... > > Such values are nonsense, but VFK driver has to read them. Currently > overflowed values are returned. > > I can see only one option: switch to strings. So N30 will be treated > as string(30) by GDAL. Unfortunately it will influences (due to few > non-sense values mentioned above) important attributes like ID which > will be converted from bigint to text attributes.
For >= 19 characters, bigint cannot be used indeed. There isn't much other choice than storing as a string. Even -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
