<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Christian,<div><br></div><div>My guess here is that because you've told the geometry to be a MULTIPOLYGON, but you may have returned a POLYGON, you have indeed violated the check constraint on the geometry type.</div><div><br></div><div>try using st_multi() to get around it, as in :</div><div><br></div><div><blockquote type="cite"><div><div><div>update public.tl_2010_us_cd111 set simple_geom = ST_Multi(ST_SimplifyPreserveTopology(the_geom, 15));</div></div></div></blockquote><div><br></div>cheers</div><div><br></div><div>Ben</div><div><br></div><div><br><div><div><div><div><br></div></div></div></div><div><div>On 28/06/2011, at 11:23 PM, Christian Guirreri wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I get the following error:<div><div>ERROR: new row for relation "tl_2010_us_cd111" violates check constraint "enforce_geotype_simple_geom"</div><div>SQL state: 23514</div><div><br></div><div>Here's my SQL:</div>
<div><div>select addGeometryColumn('public', 'tl_2010_us_cd111', 'simple_geom', 4326, 'MULTIPOLYGON', 2);</div><div>update public.tl_2010_us_cd111 set simple_geom = ST_SimplifyPreserveTopology(the_geom, 15);</div>
</div><div><br></div><br><div class="gmail_quote">On Mon, Jun 27, 2011 at 2:07 PM, Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 6/27/2011 1:37 PM, Christian Guirreri wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm trying to do something fairly simple. I'd like to take the Tiger<br>
2010 Data - tl_2010_us_cd111 and tl_2010_us_county10 - and create shape<br>
files that are considerably smaller and more simplified. In the past<br>
I've just used MapShaper and been OK with that, but I was having trouble<br>
uploading tl_2010_us_county10 into it and I've decided its time to learn<br>
some GIS basics anyway.<br>
<br>
I've definitely successfully setup my environment - PostegreSQL 9 with<br>
PostGIS. I've used the shp2pgsql wizard included with pgadmin to import<br>
the data sets into their own databases, without the "Load Geography<br>
column" checked. I've been able to export this data back to shp<br>
using pgsql2shp and view the resulting shp in QuantumGIS and ACDSee Canvas.<br>
<br>
But when it comes to simplification - I'm not sure where to even<br>
start. I'm no database expert beyond some simple mysql so GIS is<br>
especially overwhelming. I only know that I want to<br>
use ST_SimplifyPreserveTopology() as I'm fairly certain a number of<br>
things will disappear if I don't.<br>
<br>
Would love if someone could provide me with the SQL to make this happen!<br>
</blockquote>
<br></div></div>
First you should understand that ST_SimplifyPreserveTopology() works on a single geometry at a time and not on multiple geometries in a coverage. The difference is in a coverage the the polygons that share a common edge that is simplified would continue to have a common simplified edge. When polygons are simplified individually with knowledge of the adjacent polygons it is possible for gaps and overlaps to occur along the simplified edge. ST_SimplifyPreserveTopology() is designed to try and minimize these effects but there are no guarantees.<br>
<br>
You might try something like:<br>
<br>
select addGeometryColum('myschema', 'mytable', 'simple_geom', 4326, 'MULTIPOLYGON', 2);<br>
update myschema.mytable set simple_geom = ST_SimplifyPreserveTopology(<u></u>the_geom, <tolerance>);<br>
<br>
where <tolerance> is replaces by an appropriate value. This will depend on the some trial and error. The above assume srid=4326 which is probably not a good projection for doing simplification so you might want to project your data into some other UTM or Mercator projection depending on your coverage area and tolerance needs to be set with respect to those units.<br>
<br>
-Steve W<br>
______________________________<u></u>_________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@postgis.refractions.net" target="_blank">postgis-users@postgis.<u></u>refractions.net</a><br>
<a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.<u></u>net/mailman/listinfo/postgis-<u></u>users</a><br>
</blockquote></div><br></div>
_______________________________________________<br>postgis-users mailing list<br><a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br><a href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br></blockquote></div><br></div></body></html>