<?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: The Need for Breaklines</title>
	<atom:link href="http://lidarnews.com/the-need-for-breaklines/feed" rel="self" type="application/rss+xml" />
	<link>http://lidarnews.com/the-need-for-breaklines</link>
	<description>Laser Scanning Industry News</description>
	<lastBuildDate>Fri, 30 Jul 2010 13:46:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Harold Rempel</title>
		<link>http://lidarnews.com/the-need-for-breaklines#comment-365</link>
		<dc:creator>Harold Rempel</dc:creator>
		<pubDate>Tue, 07 Jul 2009 13:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=1109#comment-365</guid>
		<description>I actually remember working on this project in the screenshot. I worked for Fugro EarthData at the time. It is (roughly) from about 2003-2004 where we processed LiDAR and aerial photography over Mecklenburg County, NC. We ran several tests and found that the only way to get the contours to &quot;behave&quot; properly while crossing the highway was to introduce breaklines. No matter how dense the lidar is, it is still point data which never completely defines an &quot;edge&quot;.

To answer your question; NO, we should no longer be delivering contours from LiDAR given the methods available now to visualize terrain. Some of us have been arguing this point with customers for years now. The problem is that the culture has been slow to change. Maybe the solution is to start winning over minds in academia. Or maybe this problem will correct itself as the generation raised on contours begins to retire. Either way, it has been a matter of frustration since we know that contours from LiDAR seem to be a waste of time and resources when the LiDAR can yield such an accurate surface. Breaklines may still be needed in some cases to &quot;correct&quot; a surface such as in places where a retaining wall (for instance) affects the terrain. Gridding - Agree here as well - When you are forced to deliver contours from LiDAR, gridding the source data is practically a necessity in order to reduce the number of isolations and to &quot;smooth&quot; the appearance of the contours.</description>
		<content:encoded><![CDATA[<p>I actually remember working on this project in the screenshot. I worked for Fugro EarthData at the time. It is (roughly) from about 2003-2004 where we processed LiDAR and aerial photography over Mecklenburg County, NC. We ran several tests and found that the only way to get the contours to &#8220;behave&#8221; properly while crossing the highway was to introduce breaklines. No matter how dense the lidar is, it is still point data which never completely defines an &#8220;edge&#8221;.</p>
<p>To answer your question; NO, we should no longer be delivering contours from LiDAR given the methods available now to visualize terrain. Some of us have been arguing this point with customers for years now. The problem is that the culture has been slow to change. Maybe the solution is to start winning over minds in academia. Or maybe this problem will correct itself as the generation raised on contours begins to retire. Either way, it has been a matter of frustration since we know that contours from LiDAR seem to be a waste of time and resources when the LiDAR can yield such an accurate surface. Breaklines may still be needed in some cases to &#8220;correct&#8221; a surface such as in places where a retaining wall (for instance) affects the terrain. Gridding &#8211; Agree here as well &#8211; When you are forced to deliver contours from LiDAR, gridding the source data is practically a necessity in order to reduce the number of isolations and to &#8220;smooth&#8221; the appearance of the contours.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
