Anita,
OGR's shapefile driver is reading the large values correctly is able to
display them with ogrinfo.
However, newly created .dbf files get the value -2147483648.
You can track further development regarding this at
http://trac.osgeo.org/gdal/ticket/3982
On Fri, Feb 25, 2011 at 3:04 AM, Anita
Anita,
Is it possible to send a small sample data to my email for testing? Doesn't
matter if the ID field values are wrong.
On Tue, Feb 22, 2011 at 9:21 PM, Anita Graser wrote:
> Hi,
>
> I used the following ogr2ogr command:
>
> ogr2ogr -sql "select * from nw where NAME = 'Am Johannesberg'" new
Hi,
I used the following ogr2ogr command:
ogr2ogr -sql "select * from nw where NAME = 'Am Johannesberg'" new.shp
nw.shp
The resulting shp contains correct geometries, but the values in ID,N,15,0
fields are broken.
I guess that shows that it's a GDAL/OGR problem.
Thanks, best wishes,
Ani
Am 22.02.2011, 14:49 Uhr, schrieb Barry Rowlingson
:
On Tue, Feb 22, 2011 at 12:37 PM, Anita Graser
wrote:
You can extract just one record, and share that one.
How? If I use QGIS, the values will be broken.
ogr2ogr on the command line?
ogr2ogr results in the same broken values. Loo
Anita,
First, let us isolate the source of this error. QGIS or GDAL/OGR.
Use ogr2ogr to clip the part you did with QGIS. See the extents of the
clipped shapefile using ogrinfo and use it with the ogr2ogr utility.
http://www.gdal.org/ogr2ogr.html
On Tue, Feb 22, 2011 at 6:07 PM, Anita Graser wrot
Am 22.02.2011, 13:19 Uhr, schrieb Paolo Cavallini :
Il giorno mar, 22/02/2011 alle 13.16 +0100, Anita Graser ha scritto:
I have a shapefile containing fields of type REAL15. I'd like to cut an
area of interest out of this shapefile using QGIS "Save as ..."
function.
The resulting shapefile st
