Hello, Great! It's a bit strange that you had linestrings with less than two vertices in your PstGIS DB. I think that's a bug in the application you used to load that table. It makes no sense to commit an invalid geometry.
Did you load those geometries into the database from gvSIG or from another application? If you did it with gvSIG, perhaps we should find out why the geometry was not validated before storing it in the database. Regards, Juan Lucas Domínguez Rubio --- Prodevelop SL, Valencia (España) Tlf.: 96.351.06.12 -- Fax: 96.351.09.68 http://www.prodevelop.es <http://www.prodevelop.es/> --- ________________________________ De: [email protected] en nombre de Klaus Schaefer Enviado el: jue 08/09/2011 13:39 Para: [email protected] Asunto: Re: [Gvsig_english] gvSIG 1.11 export layer to PostgreSQL/PostGIS Juan, you are a hero! That seem to have been exactly the case. I checked in the postgis table and delete these entries. Now it works like hell... gvSIG seems to be more sensible regarding postgis layers than with shape file layers. Since it never complained with the shape file... However - big THANKS again to you!!! Best regards from beautiful Moshi (at the foot of the Kilimanjaro) Klaus -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/gvSIG-1-11-export-layer-to-PostgreSQL-PostGIS-tp6761113p6771423.html Sent from the gvSIG users mailing list archive at Nabble.com. _______________________________________________ Gvsig_internacional mailing list [email protected] http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
_______________________________________________ Gvsig_internacional mailing list [email protected] http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
