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 Graser <anitagra...@gmx.at> wrote: > Hi, > > Thanks for your help. I've attached a sample with faulty values > > Best wishes, > > Anita > > > Am 22.02.2011, 17:39 Uhr, schrieb Chaitanya kumar CH <chaitanya.ch@ > gmail.com>: > > > 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 <anitagra...@gmx.at> wrote: >> >> 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, >>> Anita >>> >>> >>> Am 22.02.2011, 16:33 Uhr, schrieb Chaitanya kumar CH <chaitanya.ch@ >>> gmail.com>: >>> >>> >>> 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 >>>> >>>> >>>> >>> _______________________________________________ >>> gdal-dev mailing list >>> gdal-dev@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/gdal-dev >>> >>> >> -- Best regards, Chaitanya kumar CH. /tʃaɪθənjə/ /kʊmɑr/ +91-9494447584 17.2416N 80.1426E
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
