On Fri, Jun 15, 2007 at 11:01:06AM +0100, Mark Cave-Ayland wrote: > On Fri, 2007-06-15 at 13:31 +0400, дорофеев александр wrote: > > I took this shapefile (Arc) and uploaded it into postgis using standart > > shp2pgsql > > Then I tryed to download this data into shapefile using my own dumper and > > I`ve got an error with spliting string on feature with FID=7. Then i dumped > > this geometry string into textfile and got this (brokenstring.txt) > > then i made biggeom.sql and run it in psql to see if a string will be > > broken and all was fine > > The Developers said than it is a bug of ODBC driver. I checked this > > sugggestion by addind text field to postgis table and run such sql UPDATE > > testtable SET testfield=ASTEXT(the_geom) and the string in this field > > became broken (maybe not finished) on small objects the value of this field > > looked well > > Everything looks fine here.
Here too. I notice that brokenstring.txt becomes broken at right around 8192 (0x2000) bytes, which seems like a "neat" number. Buffer size in the driver or application? 00001fe0 35 2e 30 33 33 32 33 34 2c 33 34 2e 30 30 34 35 |5.033234,34.0045| 00001ff0 38 35 20 34 35 2e 30 33 30 32 33 39 2c 33 20 20 |85 45.030239,3 | 00002000 20 20 20 20 04 20 20 20 01 20 20 20 20 20 20 20 | . . | 00002010 20 20 20 20 04 20 20 20 1e 02 20 20 20 20 20 20 | . .. | 00002020 20 20 20 20 10 20 20 20 3f 69 3f 3f 3f 3f 3f 3f | . ?i??????| 00002030 3f 3f 3f 3f 3f 3f 3f 3f 20 20 20 20 20 |???????? | -- Michael Fuhr _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
