Hi,
2018-06-06 20:58 GMT+02:00 Even Rouault :
> You can use CPLGetValueType(str) == CPL_VALUE_INTEGER as an additional test to
> check if it is an integer (of arbitrary length)
great, I have improved error handling in VFK accordingly [1]. Ma
[1] https://github.com/OSGeo/gdal/issues/672#issuecomm
On mercredi 6 juin 2018 19:27:50 CEST Martin Landa wrote:
> Hi,
>
> 2018-06-05 11:16 GMT+02:00 Even Rouault :
> > For >= 19 characters, bigint cannot be used indeed. There isn't much other
> > choice than storing as a string.
>
> right. In [1] I switched at least to CPLAtoGIntBigEx(). BTW I would
Hi,
2018-06-05 11:16 GMT+02:00 Even Rouault :
> For >= 19 characters, bigint cannot be used indeed. There isn't much other
> choice than storing as a string.
right. In [1] I switched at least to CPLAtoGIntBigEx(). BTW I would
expect that a warning will be printed also on invalid character. But
*
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
>
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
th
