<?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 on: SHM ArcView Importer</title>
	<atom:link href="http://www.chromecow.com/downloads/lscript/shm-arcview-importer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chromecow.com</link>
	<description>Game designer, mad scientist and tinkerer</description>
	<lastBuildDate>Thu, 08 Oct 2009 18:58:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sean Hyde-Moyer</title>
		<link>http://www.chromecow.com/downloads/lscript/shm-arcview-importer/comment-page-1/#comment-77</link>
		<dc:creator>Sean Hyde-Moyer</dc:creator>
		<pubDate>Fri, 03 Mar 2006 14:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.chromecow.com/shm-arcview-importer/#comment-77</guid>
		<description>A couple of notes I forgot to mention.

When Lightwave builds a polygon, it uses the first three points to determine the direction of the surface normal (which way the polygon is &quot;flipped&quot;).

Unfortunately, the GIS Data has a fairly large number of cases (evidently) where the first 3 or more points in the shape are co-linear, all lined up in a row. 

When this happens, Lightwave can&#039;t figure out the direction of the flip, and just chooses one.

What this means, pragmatically, is that of the hundreds of counties in a US map, some will be flipped the wrong direction.

So, the best way to fix the problem is to use an LScript like James Jones &lt;a href=&quot;http://home.comcast.net/~jgj252/LW/plugins.htm&quot; rel=&quot;nofollow&quot;&gt;DSelect&lt;/a&gt; to select the backwards facing polygons, then flip them.

Safety tip: The boundaries are made with two-point polys, and these will cause the select-direction plugins to fail (because two-point polys don&#039;t have a facing direction).

So select all the two-point polys and cut-and-paste them to a separate layer before running DSelect. 

These problems should be addressable some day, but who knows when that day is.</description>
		<content:encoded><![CDATA[<p>A couple of notes I forgot to mention.</p>
<p>When Lightwave builds a polygon, it uses the first three points to determine the direction of the surface normal (which way the polygon is &#8220;flipped&#8221;).</p>
<p>Unfortunately, the GIS Data has a fairly large number of cases (evidently) where the first 3 or more points in the shape are co-linear, all lined up in a row. </p>
<p>When this happens, Lightwave can&#8217;t figure out the direction of the flip, and just chooses one.</p>
<p>What this means, pragmatically, is that of the hundreds of counties in a US map, some will be flipped the wrong direction.</p>
<p>So, the best way to fix the problem is to use an LScript like James Jones <a href="http://home.comcast.net/~jgj252/LW/plugins.htm" rel="nofollow">DSelect</a> to select the backwards facing polygons, then flip them.</p>
<p>Safety tip: The boundaries are made with two-point polys, and these will cause the select-direction plugins to fail (because two-point polys don&#8217;t have a facing direction).</p>
<p>So select all the two-point polys and cut-and-paste them to a separate layer before running DSelect. </p>
<p>These problems should be addressable some day, but who knows when that day is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
