<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Using the same point shapefile to construct a Terrain and a TIN gives slightly different maps in 3D Questions</title>
    <link>https://community.esri.com/t5/3d-questions/using-the-same-point-shapefile-to-construct-a/m-p/563162#M3363</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Jonathan, the entire TIN dataset is always evaluated at once, whereas the terrain dataset has a tiling mechanism that's used in analysis operations. The default behavior utilizes a dynamic tile size but an environment setting is available to force the terrain to use&amp;nbsp;its own predefined tile size. This tiling process may potentially account for some discrepancy.&amp;nbsp; Using the environment setting to force the terrain tile size to be used would ensure the same results. If you see it doing otherwise, please share your results and let's see if we can figure out what's going on/&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Jul 2020 06:21:51 GMT</pubDate>
    <dc:creator>KhalidDuri1</dc:creator>
    <dc:date>2020-07-22T06:21:51Z</dc:date>
    <item>
      <title>Using the same point shapefile to construct a Terrain and a TIN gives slightly different maps</title>
      <link>https://community.esri.com/t5/3d-questions/using-the-same-point-shapefile-to-construct-a/m-p/563161#M3362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Building a Terrain and a TIN out of the same point shapefile produces two maps that look extremely similar, but when I run the results through the Surface Volume the Terrain and TIN give slightly different volume results. The volume of the Terrain also changes depending on whether Z Tolerance or Window Size is used as a pyramiding method even though the Surface Volume tool is analyzing the full resolution Terrain data.&amp;nbsp;Is there a specific set of parameters that will produce a Terrain that gives identical volume results to a TIN or are the two methods inherently different in some way?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jun 2020 13:27:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/3d-questions/using-the-same-point-shapefile-to-construct-a/m-p/563161#M3362</guid>
      <dc:creator>JonathanZieg</dc:creator>
      <dc:date>2020-06-09T13:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: Using the same point shapefile to construct a Terrain and a TIN gives slightly different maps</title>
      <link>https://community.esri.com/t5/3d-questions/using-the-same-point-shapefile-to-construct-a/m-p/563162#M3363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Jonathan, the entire TIN dataset is always evaluated at once, whereas the terrain dataset has a tiling mechanism that's used in analysis operations. The default behavior utilizes a dynamic tile size but an environment setting is available to force the terrain to use&amp;nbsp;its own predefined tile size. This tiling process may potentially account for some discrepancy.&amp;nbsp; Using the environment setting to force the terrain tile size to be used would ensure the same results. If you see it doing otherwise, please share your results and let's see if we can figure out what's going on/&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Jul 2020 06:21:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/3d-questions/using-the-same-point-shapefile-to-construct-a/m-p/563162#M3363</guid>
      <dc:creator>KhalidDuri1</dc:creator>
      <dc:date>2020-07-22T06:21:51Z</dc:date>
    </item>
  </channel>
</rss>

