<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Strk&#039;s Blog</title>
	<atom:link href="http://strk.keybit.net/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://strk.keybit.net/blog</link>
	<description>Free Thoughts</description>
	<lastBuildDate>Sat, 28 Jan 2012 13:13:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>Comment on A walk on the wild side by strk</title>
		<link>http://strk.keybit.net/blog/2012/01/28/a-walk-on-the-wild-side/comment-page-1/#comment-12550</link>
		<dc:creator>strk</dc:creator>
		<pubDate>Sat, 28 Jan 2012 13:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=330#comment-12550</guid>
		<description>And here we go, after fixing the last bugs: http://trac.osgeo.org/postgis/changeset/8957</description>
		<content:encoded><![CDATA[<p>And here we go, after fixing the last bugs: <a href="http://trac.osgeo.org/postgis/changeset/8957" rel="nofollow">http://trac.osgeo.org/postgis/changeset/8957</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Topology cleaning with PostGIS by strk</title>
		<link>http://strk.keybit.net/blog/2011/11/21/topology-cleaning-with-postgis/comment-page-1/#comment-8941</link>
		<dc:creator>strk</dc:creator>
		<pubDate>Mon, 21 Nov 2011 20:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=309#comment-8941</guid>
		<description>An addendum for the braves. 

Remove the longest edge bounding faces with area &lt; 0.1:

  WITH small_faces AS (
    SELECT face.face_id   
    FROM small_sample_topo.face 
    WHERE face.face_id &gt; 0 
       AND st_area(st_getfacegeometry(&#039;small_sample_topo&#039;::character varying, face.face_id)) &lt; 0.1 
  ), alldata AS (
    SELECT f.face_id, e.edge_id, st_length(e.geom), 
            max(st_length(e.geom)) over (partition by f.face_id) as mlen
    FROM small_sample_topo.edge_data e, small_faces f 
    WHERE e.left_face = f.face_id or e.right_face = f.face_id 
  ) 
  SELECT st_remedgemodface(&#039;small_sample_topo&#039;, edge_id) 
  FROM alldata WHERE st_length = mlen;

Drop dangling edges:

  SELECT st_remedgemodface(&#039;small_sample_topo&#039;, edge_id) 
  FROM small_sample_topo.edge_data 
  WHERE left_face = right_face;

Remove isolated nodes:

  SELECT st_remisonode(&#039;small_sample_topo&#039;, node_id)
  FROM small_sample_topo.node
  WHERE containing_face is not null;</description>
		<content:encoded><![CDATA[<p>An addendum for the braves. </p>
<p>Remove the longest edge bounding faces with area < 0.1:</p>
<p>  WITH small_faces AS (<br />
    SELECT face.face_id<br />
    FROM small_sample_topo.face<br />
    WHERE face.face_id > 0<br />
       AND st_area(st_getfacegeometry(&#8216;small_sample_topo&#8217;::character varying, face.face_id)) < 0.1<br />
  ), alldata AS (<br />
    SELECT f.face_id, e.edge_id, st_length(e.geom),<br />
            max(st_length(e.geom)) over (partition by f.face_id) as mlen<br />
    FROM small_sample_topo.edge_data e, small_faces f<br />
    WHERE e.left_face = f.face_id or e.right_face = f.face_id<br />
  )<br />
  SELECT st_remedgemodface(&#8216;small_sample_topo&#8217;, edge_id)<br />
  FROM alldata WHERE st_length = mlen;</p>
<p>Drop dangling edges:</p>
<p>  SELECT st_remedgemodface(&#8216;small_sample_topo&#8217;, edge_id)<br />
  FROM small_sample_topo.edge_data<br />
  WHERE left_face = right_face;</p>
<p>Remove isolated nodes:</p>
<p>  SELECT st_remisonode(&#8216;small_sample_topo&#8217;, node_id)<br />
  FROM small_sample_topo.node<br />
  WHERE containing_face is not null;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by Topology cleaning with PostGIS &#171; Strk&#039;s Blog</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-8938</link>
		<dc:creator>Topology cleaning with PostGIS &#171; Strk&#039;s Blog</dc:creator>
		<pubDate>Mon, 21 Nov 2011 17:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-8938</guid>
		<description>[...] early tester of the new PostGIS Topology submitted an interesting dataset which kept me busy for a couple of weeks fixing a bunch of bugs [...]</description>
		<content:encoded><![CDATA[<p>[...] early tester of the new PostGIS Topology submitted an interesting dataset which kept me busy for a couple of weeks fixing a bunch of bugs [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ming 0.4.4 released by Sandro Santilli &#8211; Sviluppatore Gnash &#171; fedora-os.org</title>
		<link>http://strk.keybit.net/blog/2011/10/26/ming-0-4-4-released/comment-page-1/#comment-8925</link>
		<dc:creator>Sandro Santilli &#8211; Sviluppatore Gnash &#171; fedora-os.org</dc:creator>
		<pubDate>Mon, 21 Nov 2011 13:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=291#comment-8925</guid>
		<description>[...] [1] http://strk.keybit.net/blog/2011/10/26/ming-0-4-4-released/ [...]</description>
		<content:encoded><![CDATA[<p>[...] [1] <a href="http://strk.keybit.net/blog/2011/10/26/ming-0-4-4-released/" rel="nofollow">http://strk.keybit.net/blog/2011/10/26/ming-0-4-4-released/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by strk</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-7639</link>
		<dc:creator>strk</dc:creator>
		<pubDate>Wed, 19 Oct 2011 15:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-7639</guid>
		<description>Agreed on design/specification needs. Not that easy to find the time. If you start it please report the url back here and I&#039;ll take a look.</description>
		<content:encoded><![CDATA[<p>Agreed on design/specification needs. Not that easy to find the time. If you start it please report the url back here and I&#8217;ll take a look.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by Luís Ferreira</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-7638</link>
		<dc:creator>Luís Ferreira</dc:creator>
		<pubDate>Wed, 19 Oct 2011 14:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-7638</guid>
		<description>A drafting design / specification, on qgis wiki, would be essential.

Something analogous to ArcSomething topology tools: a (1) topology layer (in memory or else), where we can define the intervening layers/postgis tables,  (2) rules (overlaps, gaps, covers, contains), (3) a list of errors, and (4) tools to merge/subtract/create feature/mark as exception or error.

This would a plus (++++) if created. Add this to (fast) raster reprojection and good cartographic production tools and say good bye to proprietary software.</description>
		<content:encoded><![CDATA[<p>A drafting design / specification, on qgis wiki, would be essential.</p>
<p>Something analogous to ArcSomething topology tools: a (1) topology layer (in memory or else), where we can define the intervening layers/postgis tables,  (2) rules (overlaps, gaps, covers, contains), (3) a list of errors, and (4) tools to merge/subtract/create feature/mark as exception or error.</p>
<p>This would a plus (++++) if created. Add this to (fast) raster reprojection and good cartographic production tools and say good bye to proprietary software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by Mateusz Loskot</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-7567</link>
		<dc:creator>Mateusz Loskot</dc:creator>
		<pubDate>Mon, 17 Oct 2011 14:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-7567</guid>
		<description>Sandro,

This is a great news.
Congratulations!</description>
		<content:encoded><![CDATA[<p>Sandro,</p>
<p>This is a great news.<br />
Congratulations!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by strk</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-7521</link>
		<dc:creator>strk</dc:creator>
		<pubDate>Sun, 16 Oct 2011 09:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-7521</guid>
		<description>There&#039;s a ticket on qgis tracker about unifying the topological editing toolbar here: http://hub.qgis.org/issues/3483

I&#039;m not sure the GRASS toolbar would be appropriate for PostGIS topology editing.
A toolbar oriented toward ISO SQL/MM editing functions would allow:
adding an isolated node, adding an edge, splitting an edge, modifying an edge, removing an edge, removing a node. Topologies constructed through such functions would always be valid as invalidity would be caught by the functions themselves. 

Such editing would need to be in sync with DB in order to make use of the functions, so would benefit from some locking and possibly versioning support.

I guess the next step here would be drafting design on a qgis wiki page...</description>
		<content:encoded><![CDATA[<p>There&#8217;s a ticket on qgis tracker about unifying the topological editing toolbar here: <a href="http://hub.qgis.org/issues/3483" rel="nofollow">http://hub.qgis.org/issues/3483</a></p>
<p>I&#8217;m not sure the GRASS toolbar would be appropriate for PostGIS topology editing.<br />
A toolbar oriented toward ISO SQL/MM editing functions would allow:<br />
adding an isolated node, adding an edge, splitting an edge, modifying an edge, removing an edge, removing a node. Topologies constructed through such functions would always be valid as invalidity would be caught by the functions themselves. </p>
<p>Such editing would need to be in sync with DB in order to make use of the functions, so would benefit from some locking and possibly versioning support.</p>
<p>I guess the next step here would be drafting design on a qgis wiki page&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by Jeremy</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-7503</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Sat, 15 Oct 2011 21:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-7503</guid>
		<description>Have the ability to construct and edit topology objects, modify and reshape edges, validate and preview topology errors. Wrapped up into a nice topology editing toolbar :)</description>
		<content:encoded><![CDATA[<p>Have the ability to construct and edit topology objects, modify and reshape edges, validate and preview topology errors. Wrapped up into a nice topology editing toolbar <img src='http://strk.keybit.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostGIS topology ISO SQL/MM complete by strk</title>
		<link>http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/comment-page-1/#comment-7498</link>
		<dc:creator>strk</dc:creator>
		<pubDate>Sat, 15 Oct 2011 19:34:04 +0000</pubDate>
		<guid isPermaLink="false">http://strk.keybit.net/blog/?p=223#comment-7498</guid>
		<description>There&#039;s very basic support in the db_manager plugin to open a set of layers which help you visualize your topology, but nothing more than that yet at time of writing.

What kind of management features would you like to see exposed ?</description>
		<content:encoded><![CDATA[<p>There&#8217;s very basic support in the db_manager plugin to open a set of layers which help you visualize your topology, but nothing more than that yet at time of writing.</p>
<p>What kind of management features would you like to see exposed ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

