<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The magic bullet</title>
	<link>http://www.perrygeo.net/wordpress/?p=132</link>
	<description>Matt Perry's random adventures with geospatial technology and other tangentially related topics</description>
	<pubDate>Thu, 09 Sep 2010 16:20:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Carlos Grohmann</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47938</link>
		<dc:creator>Carlos Grohmann</dc:creator>
		<pubDate>Mon, 19 Apr 2010 20:36:42 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47938</guid>
		<description>I know this post is a bit old, but it really helped me.

I had a map of city limits in Brazil (thousands of entries) and I needed to make a dissolve opearation to get a map of states. Arc couldn't do it, alway returned and error (invalid data in the table). I tried the "check/fix geometry" in arc, but also got the same error. 

ogr2ogr worked perfectly, and with the new shape I could do all the operations I needed.

tks for this post, keep up the good work.</description>
		<content:encoded><![CDATA[<p>I know this post is a bit old, but it really helped me.</p>
<p>I had a map of city limits in Brazil (thousands of entries) and I needed to make a dissolve opearation to get a map of states. Arc couldn&#8217;t do it, alway returned and error (invalid data in the table). I tried the &#8220;check/fix geometry&#8221; in arc, but also got the same error. </p>
<p>ogr2ogr worked perfectly, and with the new shape I could do all the operations I needed.</p>
<p>tks for this post, keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-06-04 &#171; j03lar50n&#8217;s Blog</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47383</link>
		<dc:creator>links for 2009-06-04 &#171; j03lar50n&#8217;s Blog</dc:creator>
		<pubDate>Fri, 05 Jun 2009 07:59:54 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47383</guid>
		<description>[...] PerryGeo » The magic bullet (tags: shapefile solutions) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] PerryGeo » The magic bullet (tags: shapefile solutions) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: perrygeo</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47357</link>
		<dc:creator>perrygeo</dc:creator>
		<pubDate>Wed, 01 Apr 2009 16:28:51 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47357</guid>
		<description>John,

Why OGR instead of Repair geometry? Simply because it works better and more consistently for me. I typically don't have time to troubleshoot a variety of options so I go with the tool that works.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Why OGR instead of Repair geometry? Simply because it works better and more consistently for me. I typically don&#8217;t have time to troubleshoot a variety of options so I go with the tool that works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47356</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 01 Apr 2009 14:40:45 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47356</guid>
		<description>Not to knock OGR, but why would you use this over the "Repair Geometry" function in ArcToolbox?

http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=checking%20and%20repairing%20geometries

If OGR is able to fix problems that ESRI's built-in tool cannot, they should be aware of the issue. Considering ESRI is relying more on GDAL/OGR for some of its translation tasks, I doubt they would have reservations using OGR's method for fixing shapefiles, if that fix handles more issues than their own solution.

http://webhelp.esri.com/arcgisdesktop/9.2/body.cfm?tocVisable=1&#38;ID=2458&#38;TopicName=Supported%20raster%20dataset%20file%20formats

As Jamey mentions, Repair Geometry should take care of most of your problems. Asger's problem (null geom in shp) is handled by the Repair Geometry tool.</description>
		<content:encoded><![CDATA[<p>Not to knock OGR, but why would you use this over the &#8220;Repair Geometry&#8221; function in ArcToolbox?</p>
<p><a href="http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=checking%20and%20repairing%20geometries" rel="nofollow">http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=checking%20and%20repairing%20geometries</a></p>
<p>If OGR is able to fix problems that ESRI&#8217;s built-in tool cannot, they should be aware of the issue. Considering ESRI is relying more on GDAL/OGR for some of its translation tasks, I doubt they would have reservations using OGR&#8217;s method for fixing shapefiles, if that fix handles more issues than their own solution.</p>
<p><a href="http://webhelp.esri.com/arcgisdesktop/9.2/body.cfm?tocVisable=1&amp;ID=2458&amp;TopicName=Supported%20raster%20dataset%20file%20formats" rel="nofollow">http://webhelp.esri.com/arcgisdesktop/9.2/body.cfm?tocVisable=1&amp;ID=2458&amp;TopicName=Supported%20raster%20dataset%20file%20formats</a></p>
<p>As Jamey mentions, Repair Geometry should take care of most of your problems. Asger&#8217;s problem (null geom in shp) is handled by the Repair Geometry tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AsgerPetersen</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47355</link>
		<dc:creator>AsgerPetersen</dc:creator>
		<pubDate>Mon, 30 Mar 2009 07:47:55 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47355</guid>
		<description>GDAL (and OGR) is the Swiss Army Knife of geodata. But beware that using OGR to fix shape files does not always give you what you expect. Even when it looks like it at a first look.

For instance we recently came across a bug in ArcGIS where deleting a feature from a shapefile would result in the geometry being removed from the shp-file but the attributes would still be present in the dbf-file. And thus there would be a different number of records in the shp and the dbf files. ArcGIS crashes on such a shape file. OGR reads and translates it happily, BUT the geometries are not linked to the correct attributes. Depending on the type of data, this kind of error can be extremely difficult to check for.</description>
		<content:encoded><![CDATA[<p>GDAL (and OGR) is the Swiss Army Knife of geodata. But beware that using OGR to fix shape files does not always give you what you expect. Even when it looks like it at a first look.</p>
<p>For instance we recently came across a bug in ArcGIS where deleting a feature from a shapefile would result in the geometry being removed from the shp-file but the attributes would still be present in the dbf-file. And thus there would be a different number of records in the shp and the dbf files. ArcGIS crashes on such a shape file. OGR reads and translates it happily, BUT the geometries are not linked to the correct attributes. Depending on the type of data, this kind of error can be extremely difficult to check for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamey Rosen</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47351</link>
		<dc:creator>Jamey Rosen</dc:creator>
		<pubDate>Thu, 26 Mar 2009 17:29:47 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47351</guid>
		<description>Thanks, this is helpful. ESRI seemed very proud of their increased error reporting in geoprocessing with the 9.3 release, but I find that almost all of the errors I get are "999999".

I find my corrupt shapefiles tend to be those created by non-GIS applications (CADD, and the 3D visualization package EVS). In these cases, the "Repair Geometry" tool (in the ArcToolbox at the ArcView license) is generally enough to fix it.</description>
		<content:encoded><![CDATA[<p>Thanks, this is helpful. ESRI seemed very proud of their increased error reporting in geoprocessing with the 9.3 release, but I find that almost all of the errors I get are &#8220;999999&#8243;.</p>
<p>I find my corrupt shapefiles tend to be those created by non-GIS applications (CADD, and the 3D visualization package EVS). In these cases, the &#8220;Repair Geometry&#8221; tool (in the ArcToolbox at the ArcView license) is generally enough to fix it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Howard Butler</title>
		<link>http://www.perrygeo.net/wordpress/?p=132#comment-47349</link>
		<dc:creator>Howard Butler</dc:creator>
		<pubDate>Thu, 26 Mar 2009 03:58:23 +0000</pubDate>
		<guid>http://www.perrygeo.net/wordpress/?p=132#comment-47349</guid>
		<description>Don't forget the -skipfailures switch which will toss out null geometries or other funkiness that might be causing troubles.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t forget the -skipfailures switch which will toss out null geometries or other funkiness that might be causing troubles.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.119 seconds -->
