<?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"
	>
<channel>
	<title>Comments on: FWTools &#38; MySQL leaves ArcGIS geoprocessor in the dust</title>
	<atom:link href="http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/feed/" rel="self" type="application/rss+xml" />
	<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/</link>
	<description>The (mis)Adventures of a self-taught developer</description>
	<pubDate>Fri, 04 Jul 2008 06:33:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: priour</title>
		<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3623</link>
		<dc:creator>priour</dc:creator>
		<pubDate>Thu, 13 Mar 2008 19:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3623</guid>
		<description>@Tripp
I honestly don't know how you would go about forcing ArcGIS to use BBOX intersection and not spatial intersection. I'm sure it is possible but probably not through any pre-installed tools or scripts.</description>
		<content:encoded><![CDATA[<p>@Tripp<br />
I honestly don&#8217;t know how you would go about forcing ArcGIS to use BBOX intersection and not spatial intersection. I&#8217;m sure it is possible but probably not through any pre-installed tools or scripts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tripp</title>
		<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3622</link>
		<dc:creator>Tripp</dc:creator>
		<pubDate>Thu, 13 Mar 2008 18:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3622</guid>
		<description>Instead of trying to mimic the ArcGIS intersection in MySQL, can you mimic the MySQL intersection in ArcGIS (do the intersection in ArcGIS using the bounding box instead of the actual geometry)?  Do you think that would make a difference?</description>
		<content:encoded><![CDATA[<p>Instead of trying to mimic the ArcGIS intersection in MySQL, can you mimic the MySQL intersection in ArcGIS (do the intersection in ArcGIS using the bounding box instead of the actual geometry)?  Do you think that would make a difference?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petz</title>
		<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3599</link>
		<dc:creator>Petz</dc:creator>
		<pubDate>Wed, 23 Jan 2008 10:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3599</guid>
		<description>Interesting benchmark, altough it's broken because MySQL uses bounding boxes instead of the actual geometry. Would be interesting to compare processing times on this with more spatial databases and GIS such as Oracle Spatial, IBM DB2, MS SQL Server 2008 and even maybe Manifold? 

Does anyone know if someone has done benchmark tests for basic GIS operations like this somewhere?</description>
		<content:encoded><![CDATA[<p>Interesting benchmark, altough it&#8217;s broken because MySQL uses bounding boxes instead of the actual geometry. Would be interesting to compare processing times on this with more spatial databases and GIS such as Oracle Spatial, IBM DB2, MS SQL Server 2008 and even maybe Manifold? </p>
<p>Does anyone know if someone has done benchmark tests for basic GIS operations like this somewhere?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dylan</title>
		<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3598</link>
		<dc:creator>dylan</dc:creator>
		<pubDate>Tue, 22 Jan 2008 20:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3598</guid>
		<description>Ok- it would be interesting to see how MySQL compares to the other spatial databases once it has proper geometry operators.

Good luck!</description>
		<content:encoded><![CDATA[<p>Ok- it would be interesting to see how MySQL compares to the other spatial databases once it has proper geometry operators.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: priour</title>
		<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3597</link>
		<dc:creator>priour</dc:creator>
		<pubDate>Tue, 22 Jan 2008 17:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3597</guid>
		<description>You are right that this operation is actually on MBR and not the specific geometeries so it is faster and less acurate than using PostGIS or ArcGIS. I didn't try it on PostGIS, just because I didn't already have the data in a table like I did for MySQL. However, I am certain than PostGIS, Oracle Spatial, or SQL Server 2008 would all perform this query in less than 1/4 the time it took ArcGIS.

There is a beta or RC revision of the MySQL database which actually test geometries and not just MBR. However, I don't have it installed yet.</description>
		<content:encoded><![CDATA[<p>You are right that this operation is actually on MBR and not the specific geometeries so it is faster and less acurate than using PostGIS or ArcGIS. I didn&#8217;t try it on PostGIS, just because I didn&#8217;t already have the data in a table like I did for MySQL. However, I am certain than PostGIS, Oracle Spatial, or SQL Server 2008 would all perform this query in less than 1/4 the time it took ArcGIS.</p>
<p>There is a beta or RC revision of the MySQL database which actually test geometries and not just MBR. However, I don&#8217;t have it installed yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dylan</title>
		<link>http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3596</link>
		<dc:creator>dylan</dc:creator>
		<pubDate>Tue, 22 Jan 2008 16:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://priour.wordpress.com/2008/01/22/fwtools-mysql-leaves-arcgis-geoprocessor-in-the-dust/#comment-3596</guid>
		<description>Nice post Matt. This closely mirrors my findings using GDAL, PostGIS, etc. for automated tasks on large datasets. It would be a good idea to verify that the intersects() operator is operating on geometries and not bounding boxes. Up until recently MySQL geometry operations were only performed on so-called MBR, or bounding boxes [1]. I think that they have updated this functionality, but haven't tried it- I have since moved on to PostGIS.

1. http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html</description>
		<content:encoded><![CDATA[<p>Nice post Matt. This closely mirrors my findings using GDAL, PostGIS, etc. for automated tasks on large datasets. It would be a good idea to verify that the intersects() operator is operating on geometries and not bounding boxes. Up until recently MySQL geometry operations were only performed on so-called MBR, or bounding boxes [1]. I think that they have updated this functionality, but haven&#8217;t tried it- I have since moved on to PostGIS.</p>
<p>1. <a href="http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
