id summary reporter owner description type status priority milestone component version severity resolution keywords cc 1488 [PATCH] real-handling in .DBF-files jesper@… warmerdam "Hi There Think I found a bug in the ogr2ogr tool (from inside the windows FWTools1.2.0): when I try to convert an area that has large real-numbers, the sign is not treated as I expect. After convertion from source to targetfile (with only the affected area inside) the atribute-number 57520907013796 is ,. Same thing with FEATAREA. See the headers below (from ogrinfo): {{{ Sourcefile (largebug_region.shp): ID: Real (15.0) FEATTYP: Integer (4.0) FEATAREA: Real (15.0) FEATPERIM: Real (15.0) POSTCODE: String (10.0) OGRFeature(largeitem_region):0 ID (Real) = 57520907013796 FEATTYP (Integer) = 3136 FEATAREA (Real) = 11255420040 FEATPERIM (Real) = 1202210 POSTCODE (String) = 930 }}} but in the target (using ogr2ogr largebug_target.shp largebug_region.shp) data looks like this {{{ ID: Real (15.0) FEATTYP: Integer (4.0) FEATAREA: Real (15.0) FEATPERIM: Real (15.0) POSTCODE: String (10.0) OGRFeature(largeitem):0 ID (Real) = -1589981532 FEATTYP (Integer) = 3136 FEATAREA (Real) = -1629481848 FEATPERIM (Real) = 1202210 POSTCODE (String) = 930 }}} Thought you wanted to know. Let me know if you need the test-file. regards Jesper " defect closed normal OGR_SF 1.4.0 major duplicate shape driver