<?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: 64 Bit Dilemma</title>
	<atom:link href="http://lidarnews.com/64-bit-dilemma/feed" rel="self" type="application/rss+xml" />
	<link>http://lidarnews.com/64-bit-dilemma</link>
	<description>Laser Scanning Industry News</description>
	<lastBuildDate>Fri, 19 Mar 2010 09:13:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: R.Mandli</title>
		<link>http://lidarnews.com/64-bit-dilemma/comment-page-1#comment-949</link>
		<dc:creator>R.Mandli</dc:creator>
		<pubDate>Wed, 04 Nov 2009 21:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=1604#comment-949</guid>
		<description>As I was reading this discussion, I couldn&#039;t contain my desire to share an alternative solution that works very well for us.  We made the decision a while back that Windows was not the best environment for development of our cutting edge LIDAR product line.  We have been developing our software in the 64 bit Apple Macintosh environment for the last 2 years using OS X and Java.  We can run on everything from the lowliest Mac mini to the high end Xserves.  Most of our data reduction is done on 24 inch iMacs with a second 24 inch monitor connected for increased workspace real estate at cost of about $2K per hardware seat.

Speed of point cloud display has never been a major issue as it is instantaneous. We focus mostly on processing point clouds to extract assets and to create database files for the analysis of structural clearances.  This past summer we collected mobile lidar that included over 3 trillion points.  The point cloud is viewable immediately after capture and post processing is used only to clean up the slight GPS issues.

Of course, there are those times that we have to use Windows for checking our deliverables, but we have PC emulators on our Macs that do a great job of that.  Our software is based on Java 6 so it works well in Windows too, but it is quite a bit slower.

The path we have chosen isn&#039;t for everyone but it has worked well for us.  Our priority is productivity and this configuration of hardware and software has allowed us to accomplish that.</description>
		<content:encoded><![CDATA[<p>As I was reading this discussion, I couldn&#8217;t contain my desire to share an alternative solution that works very well for us.  We made the decision a while back that Windows was not the best environment for development of our cutting edge LIDAR product line.  We have been developing our software in the 64 bit Apple Macintosh environment for the last 2 years using OS X and Java.  We can run on everything from the lowliest Mac mini to the high end Xserves.  Most of our data reduction is done on 24 inch iMacs with a second 24 inch monitor connected for increased workspace real estate at cost of about $2K per hardware seat.</p>
<p>Speed of point cloud display has never been a major issue as it is instantaneous. We focus mostly on processing point clouds to extract assets and to create database files for the analysis of structural clearances.  This past summer we collected mobile lidar that included over 3 trillion points.  The point cloud is viewable immediately after capture and post processing is used only to clean up the slight GPS issues.</p>
<p>Of course, there are those times that we have to use Windows for checking our deliverables, but we have PC emulators on our Macs that do a great job of that.  Our software is based on Java 6 so it works well in Windows too, but it is quite a bit slower.</p>
<p>The path we have chosen isn&#8217;t for everyone but it has worked well for us.  Our priority is productivity and this configuration of hardware and software has allowed us to accomplish that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave F.</title>
		<link>http://lidarnews.com/64-bit-dilemma/comment-page-1#comment-867</link>
		<dc:creator>Dave F.</dc:creator>
		<pubDate>Sat, 17 Oct 2009 22:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=1604#comment-867</guid>
		<description>I have to concur with the switch to the 64bit version of QT. We are running on a Dell T7500 workstation with 36GB of Ram running Vista and the difference between the 32 bit version and the 64bit is not even comparable. What would make the difference is if the hardware vendors would make the switch as well as vendors such as TerraSolid.</description>
		<content:encoded><![CDATA[<p>I have to concur with the switch to the 64bit version of QT. We are running on a Dell T7500 workstation with 36GB of Ram running Vista and the difference between the 32 bit version and the 64bit is not even comparable. What would make the difference is if the hardware vendors would make the switch as well as vendors such as TerraSolid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Newcomb</title>
		<link>http://lidarnews.com/64-bit-dilemma/comment-page-1#comment-851</link>
		<dc:creator>Doug Newcomb</dc:creator>
		<pubDate>Fri, 16 Oct 2009 17:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=1604#comment-851</guid>
		<description>I processed multiple return lidar point data for the State of North Carolina for forest canopy heights about a year ago.  The entire data set is about 800 GB as ASCII x,y,z.  I processed it in 5 chunks, the largest chunk was 379 GB and took overnight to process.  Processing a 90 GB file takes about 2 hours.  The software and OS? 64 bit GRASS running on 64 bit Centos Linux.  Cost: $0  Native 64 bit GRASS has been available on 64 bit Linux since 2004-2005.  

If you install a 64-bit variant of linux (Fedora, Ubuntu , Red Hat, etc), about 99% of the software is already 64-bit.   The Openoffice.org suite went 64-bit a couple of years ago.  The only software that I can think of on a 64 bit linux system are proprietary things like the Flash plugin to Firefox.   

I guess my point is, if you step out of the Windows/commercial software world 64-bit computing is already commonplace.</description>
		<content:encoded><![CDATA[<p>I processed multiple return lidar point data for the State of North Carolina for forest canopy heights about a year ago.  The entire data set is about 800 GB as ASCII x,y,z.  I processed it in 5 chunks, the largest chunk was 379 GB and took overnight to process.  Processing a 90 GB file takes about 2 hours.  The software and OS? 64 bit GRASS running on 64 bit Centos Linux.  Cost: $0  Native 64 bit GRASS has been available on 64 bit Linux since 2004-2005.  </p>
<p>If you install a 64-bit variant of linux (Fedora, Ubuntu , Red Hat, etc), about 99% of the software is already 64-bit.   The Openoffice.org suite went 64-bit a couple of years ago.  The only software that I can think of on a 64 bit linux system are proprietary things like the Flash plugin to Firefox.   </p>
<p>I guess my point is, if you step out of the Windows/commercial software world 64-bit computing is already commonplace.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jarlath O'Neil-Dunne</title>
		<link>http://lidarnews.com/64-bit-dilemma/comment-page-1#comment-850</link>
		<dc:creator>Jarlath O'Neil-Dunne</dc:creator>
		<pubDate>Fri, 16 Oct 2009 14:56:39 +0000</pubDate>
		<guid isPermaLink="false">http://lidarnews.com/?p=1604#comment-850</guid>
		<description>We are running QT Modeler 64-bit version on both Vista x64 and Windows 7 x64.  The performance difference is huge.  The 64-bit versions of both operating systems are very stable and seem to be superior to the 32-bit versions.  When we migrated to the 64-bit version of QT Modeler went from loading in hundreds of thousands of points to billions of points, and fly through the point cloud with performance equal to Google Earth.  It cost us less than $2000 to upgrade our Dell T7500 to 48GB of RAM, and it was worth every penny.  We have noticed only performance improvements (albeit minor ones) with other 32-bit geospatial software packages, such as ArcGIS, ENVI (they have cursory 64-bit support), ERDAS IMAGINE, and Definiens eCognition.  Given that high-end workstations from manufactures such as Dell ship by default with 64-bit operating systems I hope it is only a matter of time before 64-bit is the new standard.  Let&#039;s hope the software vendors can migrate everything over.  I just noticed that even Office 2010 is going to be 64-bit.</description>
		<content:encoded><![CDATA[<p>We are running QT Modeler 64-bit version on both Vista x64 and Windows 7 x64.  The performance difference is huge.  The 64-bit versions of both operating systems are very stable and seem to be superior to the 32-bit versions.  When we migrated to the 64-bit version of QT Modeler went from loading in hundreds of thousands of points to billions of points, and fly through the point cloud with performance equal to Google Earth.  It cost us less than $2000 to upgrade our Dell T7500 to 48GB of RAM, and it was worth every penny.  We have noticed only performance improvements (albeit minor ones) with other 32-bit geospatial software packages, such as ArcGIS, ENVI (they have cursory 64-bit support), ERDAS IMAGINE, and Definiens eCognition.  Given that high-end workstations from manufactures such as Dell ship by default with 64-bit operating systems I hope it is only a matter of time before 64-bit is the new standard.  Let&#8217;s hope the software vendors can migrate everything over.  I just noticed that even Office 2010 is going to be 64-bit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
