<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16608" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Trebuchet MS">
<DIV>I agree with Rob - pgadmin can hide the geometry.</DIV>
<DIV> </DIV>
<DIV>Try: </DIV>
<DIV>select char_length(asText(the_geom)) from <TABLE> where gid = <MISSING_GEOM_GID>;<BR>On a test here, the select returned 137999 even though pgadmin looked blank.</DIV>
<DIV> </DIV>
<DIV>
<DIV>Or double-click the "missing" the_geom cell in pgadmin.</DIV>
<DIV> </DIV></DIV>
<DIV>Regards,</DIV>
<DIV>Tom</DIV>
<DIV> </DIV>
<DIV><BR>>>> "Rob Tester" <robtester@gmail.com> 3/12/2008 12:32 PM >>><BR>Is it that the geometry is actually null? <BR><BR>Don't rely on pgadmin and the data view to believe the field is null. For<BR>large geometries when viewing with pgadmin, they can appear to be null<BR>because of the way strings are handled in the extensions and not show a<BR>value in the pgadmin data view.<BR><BR>Does "select * where wkb_geometry is NULL;" Return the records that you<BR>believe are null from the insert?<BR><BR>I have geometries with more than 1400 points stored without any problems,<BR>but I use ogr2ogr to import geometry files.<BR><BR>Rob.<BR><BR>-----Original Message-----<BR>From: postgis-users-bounces@postgis.refractions.net<BR>[mailto:postgis-users-bounces@postgis.refractions.net] On Behalf Of Paul<BR>Ramsey<BR>Sent: Wednesday, March 12, 2008 10:14 AM<BR>To: PostGIS Users Discussion<BR>Subject: Re: [postgis-users] Does geometry field type have a size limit?<BR><BR>There is no limit to the geometry field size (well, no practical limit<BR><A href="http://www.postgresql.org/about/,">http://www.postgresql.org/about/,</A> 1Gb) .<BR><BR>Send me your shape file to confirm if your problem is repeatable.<BR><BR>P.<BR><BR>On 3/12/08, davidj2k <davidj2k@yahoo.com> wrote:<BR>><BR>> I am trying to convert several of my .shp files to the PostGIS database<BR>and<BR>> when it inserts some of the larger polygons it fails to insert the<BR>geometry<BR>> field value.<BR>> I tried it using the shp2pgsql and I tried it using my own code in C# and<BR>I<BR>> have even tried executing the SQL in the pgAdmin III Query function and<BR>all<BR>> three have the exact same results the record gets inserted but the<BR>geometry<BR>> field is null and it only happens on those records that have a lot of<BR>points<BR>> that make up the polygon, I created several test to try and determine how<BR>> many points were too much for it and I hit upon 1365 seemed to be the<BR>amount<BR>> that was too many.<BR>> Does anybody know if there is a limitation to the geometry field and if<BR>> there is how can I increase it?<BR>><BR>> Thank You<BR>><BR>> --<BR>> View this message in context:<BR><A href="http://www.nabble.com/Does">http://www.nabble.com/Does</A>-geometry-field-type-have-a-size-limit--tp16006438<BR>p16006438.html<BR>> Sent from the PostGIS - User mailing list archive at Nabble.com.<BR>><BR>> _______________________________________________<BR>> postgis-users mailing list<BR>> postgis-users@postgis.refractions.net<BR>> <A href="http://postgis.refractions.net/mailman/listinfo/postgis">http://postgis.refractions.net/mailman/listinfo/postgis</A>-users<BR>><BR>_______________________________________________<BR>postgis-users mailing list<BR>postgis-users@postgis.refractions.net<BR><A href="http://postgis.refractions.net/mailman/listinfo/postgis">http://postgis.refractions.net/mailman/listinfo/postgis</A>-users<BR><BR>_______________________________________________<BR>postgis-users mailing list<BR>postgis-users@postgis.refractions.net<BR><A href="http://postgis.refractions.net/mailman/listinfo/postgis">http://postgis.refractions.net/mailman/listinfo/postgis</A>-users<BR></DIV></BODY></HTML>