Right, so what you are seeing is an artefact of PgAdmin, not a problem with PostGIS. PgAdmin doesn't like displaying fields of more than a certain length.
P. On Thu, Oct 9, 2008 at 9:04 PM, <[EMAIL PROTECTED]> wrote: > See attached. I viewed it fom PgAdmin UI. Did the queries you suggested, > the_geom was not NULL. > > The sql below returns nothing: > select gid, the_geom from city where the_geom is null; > > The sql below returns npoints = 218: > select gid, npoints(the_geom) from city where polygon_id=35665106; > > Thanks, > CYW > > ----- Original Message ----- From: "Paul Ramsey" <[EMAIL PROTECTED]> > To: "PostGIS Users Discussion" <postgis-users@postgis.refractions.net> > Sent: Thursday, October 09, 2008 10:12 PM > Subject: Re: [postgis-users] TRANSFORM failures with some multiploygons - > datasample attached > > >>>> It ran without any error. But some of the resulted values in the_geom >>>> column became null or empty. >> >> How did you check this? >> >> select gid from thetable where the_geom is null? >> select gid from thetabel where npoints(the_geom) = >> >> P >> _______________________________________________ >> postgis-users mailing list >> postgis-users@postgis.refractions.net >> http://postgis.refractions.net/mailman/listinfo/postgis-users >> > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > > _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
