<?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 LiDAR News</title>
	<atom:link href="http://lidarnews.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://lidarnews.com</link>
	<description>Laser Scanning Industry News</description>
	<lastBuildDate>Tue, 31 Aug 2010 22:47:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Laser Scanning and Machine Control by Neil Other</title>
		<link>http://lidarnews.com/laser-scanning-and-machine-control#comment-21151</link>
		<dc:creator>Neil Other</dc:creator>
		<pubDate>Tue, 31 Aug 2010 22:47:43 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3943#comment-21151</guid>
		<description>At the moment, our ability to capture data greatly exceeds our ability to process it.
You could theoretically generate a model of existing topography from a scanner mounted on the machine, but will this offer a significant benefit over a model generated by logging the position of the blade when in automatic? The latter can be done without adding any hardware.
Apart from the quite daunting computational challenges of using point clouds to determine blade position in real-time, this concept has one drawback compared to GNSS positioning: It turns the system into a line-of-sight system. The instant something obstructs the line of sight to the static reference, the system becomes inoperable.
I think scanners will first and foremost find their application in rapidly-deployed, easy-to-use and relatively cheap as-builts on large projects.</description>
		<content:encoded><![CDATA[<p>At the moment, our ability to capture data greatly exceeds our ability to process it.<br />
You could theoretically generate a model of existing topography from a scanner mounted on the machine, but will this offer a significant benefit over a model generated by logging the position of the blade when in automatic? The latter can be done without adding any hardware.<br />
Apart from the quite daunting computational challenges of using point clouds to determine blade position in real-time, this concept has one drawback compared to GNSS positioning: It turns the system into a line-of-sight system. The instant something obstructs the line of sight to the static reference, the system becomes inoperable.<br />
I think scanners will first and foremost find their application in rapidly-deployed, easy-to-use and relatively cheap as-builts on large projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LiDAR and Google Maps by Meharaj</title>
		<link>http://lidarnews.com/lidar-and-google-maps#comment-21142</link>
		<dc:creator>Meharaj</dc:creator>
		<pubDate>Fri, 27 Aug 2010 12:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3742#comment-21142</guid>
		<description>I believe Google is using the World elevation suite from Digital globe and not LiDAR. Photosat (http://www.photosat.ca/) has developed an innovative techinique for generating terrain data from satellite imagery. This technique that was used earlier in 3D geophysical siesmic studies has been deployed for automated generation of 3D data from satellite imageries. Photosat claims a 30 cm accuracy for their elevation data.</description>
		<content:encoded><![CDATA[<p>I believe Google is using the World elevation suite from Digital globe and not LiDAR. Photosat (<a href="http://www.photosat.ca/" rel="nofollow">http://www.photosat.ca/</a>) has developed an innovative techinique for generating terrain data from satellite imagery. This technique that was used earlier in 3D geophysical siesmic studies has been deployed for automated generation of 3D data from satellite imageries. Photosat claims a 30 cm accuracy for their elevation data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scanning Becoming Mainstream by Rob Mellis</title>
		<link>http://lidarnews.com/laser-scanning-becoming-mainstream#comment-21130</link>
		<dc:creator>Rob Mellis</dc:creator>
		<pubDate>Fri, 20 Aug 2010 14:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3849#comment-21130</guid>
		<description>Excellent article outling the various ways to apply laser scanning in a survey environment. I especially apprciate M.Pinkerton noting the drawbacks as well as the benfits. I agree with his observation that laser scanning in the survey community is approached in much the smae way as GPS applications were 20 years ago. While I believe it will gain acceptance as end users ask for data in to be collected using this methodolgy, I think the lack of cadastral applications will slow adoption of it by the survey community.</description>
		<content:encoded><![CDATA[<p>Excellent article outling the various ways to apply laser scanning in a survey environment. I especially apprciate M.Pinkerton noting the drawbacks as well as the benfits. I agree with his observation that laser scanning in the survey community is approached in much the smae way as GPS applications were 20 years ago. While I believe it will gain acceptance as end users ask for data in to be collected using this methodolgy, I think the lack of cadastral applications will slow adoption of it by the survey community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Comparison of Wind LiDARs and Mobile Project Planning by Stephen Clancy</title>
		<link>http://lidarnews.com/comparison-of-wind-lidars-and-mobile-project-planning#comment-21129</link>
		<dc:creator>Stephen Clancy</dc:creator>
		<pubDate>Thu, 19 Aug 2010 18:01:02 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3861#comment-21129</guid>
		<description>Gene:
Thanks for sharing our blog. There are a lot of things to consider when performing a Mobile LiDAR project - GPS only being one of the them.  Unlike the earlier days of GPS when it was common place to create obstruction diagrams for static base stations, our roving Mobile LiDAR unit presents a unique challenge with respect obstructions.  Our planning helps provide the framework for success and while keeping the back office processing (and staff) in mind.
Thanks again,
Stephen Clancy, PLS, GISP
Mobile LiDAR Technical Manager (and resident blogger)
Michael Baker Jr., Inc.</description>
		<content:encoded><![CDATA[<p>Gene:<br />
Thanks for sharing our blog. There are a lot of things to consider when performing a Mobile LiDAR project &#8211; GPS only being one of the them.  Unlike the earlier days of GPS when it was common place to create obstruction diagrams for static base stations, our roving Mobile LiDAR unit presents a unique challenge with respect obstructions.  Our planning helps provide the framework for success and while keeping the back office processing (and staff) in mind.<br />
Thanks again,<br />
Stephen Clancy, PLS, GISP<br />
Mobile LiDAR Technical Manager (and resident blogger)<br />
Michael Baker Jr., Inc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scan Data Exchange Format Website by lidar</title>
		<link>http://lidarnews.com/laser-scan-data-exchange-format-website#comment-21128</link>
		<dc:creator>lidar</dc:creator>
		<pubDate>Wed, 18 Aug 2010 15:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3839#comment-21128</guid>
		<description>If you join the beta test program you will get the spec.</description>
		<content:encoded><![CDATA[<p>If you join the beta test program you will get the spec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scan Data Exchange Format Website by Roland</title>
		<link>http://lidarnews.com/laser-scan-data-exchange-format-website#comment-21126</link>
		<dc:creator>Roland</dc:creator>
		<pubDate>Wed, 18 Aug 2010 14:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3839#comment-21126</guid>
		<description>I posted an answer, but was using the wrong button to reply. See below...</description>
		<content:encoded><![CDATA[<p>I posted an answer, but was using the wrong button to reply. See below&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scan Data Exchange Format Website by lidar</title>
		<link>http://lidarnews.com/laser-scan-data-exchange-format-website#comment-21125</link>
		<dc:creator>lidar</dc:creator>
		<pubDate>Wed, 18 Aug 2010 12:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3839#comment-21125</guid>
		<description>Full Waveform data is not yet covered by this version of the standard. What exactly do you expect to be standardized when saying &quot;Full Waveform&quot; data?</description>
		<content:encoded><![CDATA[<p>Full Waveform data is not yet covered by this version of the standard. What exactly do you expect to be standardized when saying &#8220;Full Waveform&#8221; data?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scan Data Exchange Format Website by Roland</title>
		<link>http://lidarnews.com/laser-scan-data-exchange-format-website#comment-21124</link>
		<dc:creator>Roland</dc:creator>
		<pubDate>Wed, 18 Aug 2010 12:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3839#comment-21124</guid>
		<description>The license used is the same as boost license (OSI approved). We used the same wording, but did not call it boost, since boost is something different.</description>
		<content:encoded><![CDATA[<p>The license used is the same as boost license (OSI approved). We used the same wording, but did not call it boost, since boost is something different.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scan Data Exchange Format Website by lidar</title>
		<link>http://lidarnews.com/laser-scan-data-exchange-format-website#comment-21123</link>
		<dc:creator>lidar</dc:creator>
		<pubDate>Wed, 18 Aug 2010 11:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3839#comment-21123</guid>
		<description>Paolo,

It is not the policy of the ASTM to publish the names, but we have representatives from many of the leading vendors. I believe the license is a standard license. The spec is going to be published by ASTM. You will have to purchase a copy once it is published. 

We look forward to your support.</description>
		<content:encoded><![CDATA[<p>Paolo,</p>
<p>It is not the policy of the ASTM to publish the names, but we have representatives from many of the leading vendors. I believe the license is a standard license. The spec is going to be published by ASTM. You will have to purchase a copy once it is published. </p>
<p>We look forward to your support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Laser Scan Data Exchange Format Website by Paolo Cignoni</title>
		<link>http://lidarnews.com/laser-scan-data-exchange-format-website#comment-21122</link>
		<dc:creator>Paolo Cignoni</dc:creator>
		<pubDate>Wed, 18 Aug 2010 06:28:02 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=3839#comment-21122</guid>
		<description>It would be nice to know who are the subcommittee members. I browsed the ASTM ( http://www.astm.org/COMMIT/COMMITTEE/E57.htm ) site for a list but I was not able to find any name...

BTW  I welcome an open standard in this field (particularly if it really become a &quot;STANDARD&quot;) and I want to see if we can add its support to the open source &lt;a href=&quot;http://meshlab.sourceforge.net&quot; rel=&quot;nofollow&quot;&gt;mesh processing&lt;/a&gt; and range scanning tool MeshLab .

A few comments/questions:
- why have you used a non standard the license? Adopting one of the standard OSI license (MIT, LGPL ?) would make MUCH clearer how free is the reference implementation.
- a draft of the spec? on the sourceforge site I have found just the api of the library, but no high level info on the format itself (what kind of compression?) 

Cheers
Paolo Cignoni</description>
		<content:encoded><![CDATA[<p>It would be nice to know who are the subcommittee members. I browsed the ASTM ( <a href="http://www.astm.org/COMMIT/COMMITTEE/E57.htm" rel="nofollow">http://www.astm.org/COMMIT/COMMITTEE/E57.htm</a> ) site for a list but I was not able to find any name&#8230;</p>
<p>BTW  I welcome an open standard in this field (particularly if it really become a &#8220;STANDARD&#8221;) and I want to see if we can add its support to the open source <a href="http://meshlab.sourceforge.net" rel="nofollow">mesh processing</a> and range scanning tool MeshLab .</p>
<p>A few comments/questions:<br />
- why have you used a non standard the license? Adopting one of the standard OSI license (MIT, LGPL ?) would make MUCH clearer how free is the reference implementation.<br />
- a draft of the spec? on the sourceforge site I have found just the api of the library, but no high level info on the format itself (what kind of compression?) </p>
<p>Cheers<br />
Paolo Cignoni</p>
]]></content:encoded>
	</item>
</channel>
</rss>
