Le jeudi 29 novembre 2012 23:23:44, Jeremy Palmer a écrit :
> so just to confirm 64bit integers can not be implemented before 2.X or
> 1.XX?
I think (hope) that 1.10 will be the last of the 1.X series. Implementing
64bit integer involves ABI changes, so qualifies for 2.0.
so just to confirm 64bit integers can not be implemented before 2.X or 1.XX?
- Original Message -
From: Even Rouault
To: Jeremy Palmer
Cc: "gdal-dev@lists.osgeo.org"
Sent: 30/11/2012 11:15 AM
Subject: Re: [gdal-dev] 64bit integers
Le jeudi 29 novembre 2012 23:10:08, Jerem
-
> From: Even Rouault
> To: "gdal-dev@lists.osgeo.org"
> Sent: 30/11/2012 10:45 AM
> Subject: Re: [gdal-dev] 64bit integers
>
> Le jeudi 29 novembre 2012 22:36:54, Jürgen E. Fischer a écrit :
> > Hi Even,
> >
> > On Thu, 29. Nov 2012 at 20:53:57 +0100, Even
: Even Rouault
To: "gdal-dev@lists.osgeo.org"
Sent: 30/11/2012 10:45 AM
Subject: Re: [gdal-dev] 64bit integers
Le jeudi 29 novembre 2012 22:36:54, Jürgen E. Fischer a écrit :
> Hi Even,
>
> On Thu, 29. Nov 2012 at 20:53:57 +0100, Even Rouault wrote:
> > With late
Le jeudi 29 novembre 2012 22:36:54, Jürgen E. Fischer a écrit :
> Hi Even,
>
> On Thu, 29. Nov 2012 at 20:53:57 +0100, Even Rouault wrote:
> > With latest trunk, you can set the OGR_SETFIELD_NUMERIC_WARNING
> > configruation option to YES. This should generate a warning if the
> > conversion to in
Hi Even,
On Thu, 29. Nov 2012 at 20:53:57 +0100, Even Rouault wrote:
> With latest trunk, you can set the OGR_SETFIELD_NUMERIC_WARNING configruation
> option to YES. This should generate a warning if the conversion to int
> overflows.
Um, that was meant to produce a warning when a non-numeric (
Le jeudi 29 novembre 2012 05:34:11, Jeremy Palmer a écrit :
> Hi Brent,
>
> It's in PostgreSQL. We could convert the field to a string data type, but
> that's not the point. OGR is currently corrupting data without telling the
> user!
With latest trunk, you can set the OGR_SETFIELD_NUMERIC_WARNIN
9 November 2012 3:55 p.m.
To: gdal-dev@lists.osgeo.org; Jeremy Palmer
Subject: Re: [gdal-dev] 64bit integers
Hi Jeremy,
Outside of a GDAL solution, what format is the underlying data stored in?
I have resolved issues like this with Postgis data stores by doing the int64 to
string conversion in
approach, but one of the reasons a good spatial database
is a useful foundation for these sorts of systems.
Brent Wood.
--- On Thu, 11/29/12, Jeremy Palmer wrote:
From: Jeremy Palmer
Subject: [gdal-dev] 64bit integers
To: "gdal-dev@lists.osgeo.org"
Date: Thursday, November 29, 2012, 10:26
I have a WFS layer with a 64bit integer field (sufi):
http://wfs.data.linz.govt.nz/83de09e2215a4d0c914dbfe28bb71557/v/x1208/wfs?service=WFS
When using ogr this 64bit integer field gets truncated to 32bit without any
warning. E.g
ogrinfo -al
'wfs:http://wfs.data.linz.govt.nz/83de09e2215a4d0c914
10 matches
Mail list logo
