851EB851EB85240418F5C28..."
Any idea to get the entire value ?
This should return this value normally :
0e3d70a3d70a3d40228f5c28f5c28fc0605d1eb851eb853ff851eb851eb85240418f5c28f5c28f40520ef9db22d0e5400e3d70a3d70a3d40228f5c28f5c28f0001000440372e147ae147aec041251eb851eb85bff4f5c28f5c28f6c01270a3d70a3d71400b47a
. 16 déc. 2020 à 22:28, Even Rouault a
écrit :
> Guilhain,
>
> On mercredi 16 décembre 2020 21:52:41 CET Guilhain Averlant wrote:
> > I wrote a ticket on gis.stackexchange.combut I didn't get a satisfactory
> > answer, so I ask my question here.
> >
> > I&
ar const
*,int,int,int,int,int,float,int)
Link to question on Stack Exchange :
https://gis.stackexchange.com/questions/382119/ogr-python-write-binary-data-in-layer
--
Guilhain AVERLANT
119 rue Manin
75019 PARIS
06 28 22 83 05
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
tting the precison when you create
>> the new fields, so it is defaulting to precision zero (integer).
>>
>> You will need a call something like:
>>newField.SetPrecision( 11 )
>>
>> Best regards,
>>
>> On Mon, Sep 26, 2011 at 9:09 AM, Gui