<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error</link><pubDate>Tue, 04 Nov 2014 15:28:47 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Jacquelyn Pettus</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Current Revision posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 11/4/2014 3:28:47 PM&lt;br /&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;width:680px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="font-size:150%;"&gt;&lt;span style="text-decoration:underline;"&gt;Question:&lt;/span&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="text-decoration:underline;"&gt;&lt;span style="font-size:150%;"&gt;Answer:&lt;/span&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits, but some testing yielded unofficial results that can be used as a base when determinng the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine, InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="text-decoration:underline;"&gt;&lt;span style="font-size:150%;"&gt;Possible Solutions:&lt;/span&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under&lt;strong&gt; Surface &amp;gt; Utilities&lt;/strong&gt;. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Go to &lt;strong&gt;Surface &amp;gt; Surface Properties&lt;/strong&gt; and see how many deleted points are in the model.&amp;nbsp; you may need to run the &lt;strong&gt;Surface &amp;gt; Utilities &amp;gt; Compress Surface&lt;/strong&gt; command to remove these deleted feature points to reduce the size of the DTM.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the &lt;strong&gt;Copy Portion of Surface&lt;/strong&gt; command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / laser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: InRoads, FAQ, Surface, error message, troubleshoot, SELECTsupport&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/8</link><pubDate>Tue, 04 Nov 2014 15:27:46 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Jacquelyn Pettus</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 8 posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 11/4/2014 3:27:46 PM&lt;br /&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;width:680px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads, MX, GEOPAK&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.09+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="font-size:150%;"&gt;&lt;span style="text-decoration:underline;"&gt;Question:&lt;/span&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style="text-decoration:underline;"&gt;&lt;span style="font-size:150%;"&gt;Answer:&lt;/span&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits, but some testing yielded unofficial results that can be used as a base when determinng the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine, InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under&lt;strong&gt; Surface &amp;gt; Utilities&lt;/strong&gt;. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Go to &lt;strong&gt;Surface &amp;gt; Surface Properties&lt;/strong&gt; and see how many deleted points are in the model.&amp;nbsp; you may need to run the &lt;strong&gt;Surface &amp;gt; Utilities &amp;gt; Compress Surface&lt;/strong&gt; command to remove these deleted feature points to reduce the size of the DTM.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the &lt;strong&gt;Copy Portion of Surface&lt;/strong&gt; command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / laser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: InRoads, FAQ, Surface, error message, troubleshoot, SELECTsupport&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/7</link><pubDate>Tue, 05 Aug 2014 17:11:29 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Jacquelyn Pettus</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 7 posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 8/5/2014 5:11:29 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0" align="left"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits, but some testing yielded unofficial results that can be used as a base when determinng the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine, InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under&lt;strong&gt; Surface &amp;gt; Utilities&lt;/strong&gt;. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Go to &lt;strong&gt;Surface &amp;gt; Surface Properties&lt;/strong&gt; and see how many deleted points are in the model.&amp;nbsp; you may need to run the &lt;strong&gt;Surface &amp;gt; Utilities &amp;gt; Compress Surface&lt;/strong&gt; command to remove these deleted feature points to reduce the size of the DTM.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the &lt;strong&gt;Copy Portion of Surface&lt;/strong&gt; command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / laser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: InRoads, FAQ, Surface, error message, troubleshoot, SELECTsupport&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/6</link><pubDate>Fri, 25 Apr 2014 17:20:49 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Jacquelyn Pettus</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 6 posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 4/25/2014 5:20:49 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large&lt;br /&gt;block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits but some testing yielded some unofficial results that can be used as a base when determing the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine), InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under Surface &amp;gt; Utilities. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Go to Surface &amp;gt; Surface Properties and see how many deleted points are in the model.&amp;nbsp; you may need to run the Surface &amp;gt; Utilities &amp;gt; Compress Surface command to remove these deleted feature points to reduce the size of the DTM.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the Copy Portion of Surface command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / lasser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: InRoads, FAQ, Surface, error message, troubleshoot, SELECTsupport&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/5</link><pubDate>Thu, 30 Jan 2014 19:29:31 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Jacquelyn Pettus</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 5 posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 1/30/2014 7:29:31 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large&lt;br /&gt;block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits but some testing yeilded some unofficial results that can be used as a base when determing the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine), InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under Surface &amp;gt; Utilities. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Go to Surface &amp;gt; Surface Properties and see how many deleted points are in the model.&amp;nbsp; you may need to run the Surface &amp;gt; Utilities &amp;gt; Compress Surface command to remove these deleted feature points to reduce the size of the DTM.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the Copy Portion of Surface command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / lasser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: InRoads, FAQ, Surface, error message, troubleshoot, SELECTsupport&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/4</link><pubDate>Tue, 06 Aug 2013 19:59:07 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Chris Key</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 4 posted to OpenRoads | OpenSite Wiki by Chris Key on 8/6/2013 7:59:07 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0" align="left"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large&lt;br /&gt;block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits but some testing yeilded some unofficial results that can be used as a base when determing the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine), InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under Surface &amp;gt; Utilities. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Go to Surface &amp;gt; Surface Properties and see how many deleted points are in the model.&amp;nbsp; you may need to run the Surface &amp;gt; Utilities &amp;gt; Compress Surface command to remove these deleted feature points to reduce the size of the DTM.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the Copy Portion of Surface command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / lasser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: InRoads, FAQ, Surface, error message, troubleshoot, SELECTsupport&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/3</link><pubDate>Tue, 06 Aug 2013 19:58:44 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Chris Key</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 3 posted to OpenRoads | OpenSite Wiki by Chris Key on 8/6/2013 7:58:44 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0" align="left"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large&lt;br /&gt;block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits but some testing yeilded some unofficial results that can be used as a base when determing the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine), InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under Surface &amp;gt; Utilities. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Go to Surface &amp;gt; Surface Properties and see how many deleted points are in the model.&amp;nbsp; you may need to run the Surface &amp;gt; Utilities &amp;gt; Compress Surface command to remove these deleted feature points to reduce the size of the DTM.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the Copy Portion of Surface command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / lasser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, InRoads, Surface, SELECTsupport, Troubleshoot, Error Message&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/2</link><pubDate>Tue, 06 Aug 2013 19:47:49 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Chris Key</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 2 posted to OpenRoads | OpenSite Wiki by Chris Key on 8/6/2013 7:47:49 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0" align="left"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;&amp;nbsp;&lt;/h1&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large&lt;br /&gt;block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits but some testing yeilded some unofficial results that can be used as a base when determing the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine), InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under Surface &amp;gt; Utilities. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Go to Surface &amp;gt; Surface Properties and see how many deleted points are in the model.&amp;nbsp; you may need to run the Surface &amp;gt; Utilities &amp;gt; Compress Surface command to remove these deleted feature points to reduce the size of the DTM.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the Copy Portion of Surface command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / lasser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, InRoads, Surface, SELECTsupport, Troubleshoot, Error Message&lt;/div&gt;
</description></item><item><title>Surface Size Limits (DTM) - 'Failed Allocating Memory' Error</title><link>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error/revision/1</link><pubDate>Tue, 06 Aug 2013 19:47:19 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f371b454-6d11-4cf5-a385-aa5b1750a891</guid><dc:creator>Chris Key</dc:creator><comments>https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7903/surface-size-limits-dtm-failed-allocating-memory-error#comments</comments><description>Revision 1 posted to OpenRoads | OpenSite Wiki by Chris Key on 8/6/2013 7:47:19 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0" align="left"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt; &lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To &lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;InRoads&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;08.11.07.615&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Surface&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea: &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chris Key, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt; &lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Question:&lt;/h1&gt;
&lt;p&gt;When working with InRoads on a 32bit OS versus a 64bit OS, are there any published limits in regards to surface size the program can process?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When working with larger datasets and processing surface information, there is an error message that can occur:&amp;nbsp; &amp;quot;Failed Allocating Memory&amp;quot; resulting in a program crash.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Answer:&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;memory allocation failure&amp;rdquo; is when the software begins storing a process in a block of memory on the user&amp;rsquo;s machine. When writing a large amount of information to the CAD platform this process requires a large&lt;br /&gt;block of memory.&amp;nbsp; If it cannot get through the process, the software returns with this message.&lt;/p&gt;
&lt;p&gt;There are no official limits but some testing yeilded some unofficial results that can be used as a base when determing the amount of information the InRoads program can process in a 32-bit Operating System versus a 64-bit system.&amp;nbsp; The main difference in the amount of data that can be processed is due to the amount of memory each Operating System allots to the applications.&amp;nbsp; Here are those numbers:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;32-bit&lt;/strong&gt; OS running InRoads V8.11,&amp;nbsp;the number of random points in a surface that can be processed is about &lt;strong&gt;9.1 million points&lt;/strong&gt;, which is about a &lt;strong&gt;340 +/- MB&lt;/strong&gt; file. On average it took 3.4 minutes to process this information on import.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;On a &lt;strong&gt;64-bit&lt;/strong&gt; machine), InRoads is&amp;nbsp;able to bring in &lt;strong&gt;22 million points&lt;/strong&gt; (approx. &lt;strong&gt;820 +/-&amp;nbsp;MB&lt;/strong&gt;)&amp;nbsp;in 2.42 minutes.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Solutions&amp;nbsp;for Memory Allocation Error:&lt;/h1&gt;
&lt;p&gt;Here is some additional information to troubleshoot &amp;#39;Failed Allocating memory&amp;#39; errors.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the mapping for the project is very dense you might have some latitude to thin the model.&amp;nbsp; If using InRoads 8.7+,&amp;nbsp;there is&amp;nbsp;an Application Add-In called Thin Random Points. It will appear under Surface &amp;gt; Utilities. This command is much faster than the normal thinning routine and it was developed for Lidar data. The Help has an explanation of the methodology used.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Go to Surface &amp;gt; Surface Properties and see how many deleted points are in the model.&amp;nbsp; you may need to run the Surface &amp;gt; Utilities &amp;gt; Compress Surface command to remove these deleted feature points to reduce the size of the DTM.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Copy portions of the large surface into separate DTM surfaces using the Copy Portion of Surface command.&amp;nbsp; This will allow you to work in a designated area for a project that may be confined to a small area within a larger surveyed / lasser scanned surface, greatly reducing the amount of information that is required to be opened in InRoads to perform your design tasks.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Another possibility is to&amp;nbsp;increase the virtual memory on the machine. &amp;nbsp;Use your Task Manager and set the column view to include/show the Virtual Memory size.&amp;nbsp; If&amp;nbsp;the physical memory used&amp;nbsp;exceeds the VM size, there are processes in Windows&amp;nbsp;which can be performed&amp;nbsp;to increase&amp;nbsp;the Virtual&amp;nbsp;memory.&amp;nbsp;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, InRoads, Surface, SELECTsupport, Troubleshoot, Error Message&lt;/div&gt;
</description></item></channel></rss>