<?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: Symbol Z Offset weirdness in ArcGIS10 in 3D Questions</title>
    <link>https://community.esri.com/t5/3d-questions/symbol-z-offset-weirdness-in-arcgis10/m-p/420893#M2499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I did not experience the same thing but something similar. I had a line feature class and I set the base height to a TIN. Then I extruded the line which looked fine like a fence. I then wanted to make this a multipatch so I saved and exported the Layer file to Multipatch. When I brought the multipatch into the scene it was way above the surface. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So&lt;/SPAN&gt;&lt;STRONG&gt; in my case the fix was to interpolate the feature class shapes into true 3D features &lt;/STRONG&gt;&lt;SPAN&gt;using the same TIN.&amp;nbsp; I then repeated the process with the 3D lines and it worked "as advertized".&amp;nbsp; I think there something funky going on if you set base height an existing surface and then tinker around with the 3D properties and symbology.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Try interpolating your shapes to 3D then try symbolizing again.&amp;nbsp; You are right that this should work especially because many people use symbology to create globes, cubes and other 3D symbols then convert to multipatch and calculate volume, etc.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Oct 2011 13:05:41 GMT</pubDate>
    <dc:creator>JakubSisak</dc:creator>
    <dc:date>2011-10-27T13:05:41Z</dc:date>
    <item>
      <title>Symbol Z Offset weirdness in ArcGIS10</title>
      <link>https://community.esri.com/t5/3d-questions/symbol-z-offset-weirdness-in-arcgis10/m-p/420892#M2498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In ArcGIS9x, if you have a 3D symbol (lets say a cone) and set it's Z Offset to 10 (lets say real world units of metres used), then it would place it 10m above the terrain.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, in ArcGIS10, it seems to be a ratio of the symbol size. So if my cone size is 8, and I set a z offset of 10, it puts the cone 80m above the terrain. Put the z offset to 2, and it places it 16m above the ground.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It gets even weirder if you have a multi-layer symbol. If I have a cylinder of size 10, and a cone of on top of size 8, the z offset of the cone now gets applied from the cylinder size. So in this scenario, the cone is 10m off the ground with a z offset of 1. Remove the cylinder from the multi-layer symbol, and the cone goes back to being 8m off the ground.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Anways, if everyone is still with me, is this by design in Arc10, is it a bug, is there any way to return some normaility to it all? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If by design, can the documentation be updated, as it gives the impression it should behave the same as in 9x.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2011 12:15:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/3d-questions/symbol-z-offset-weirdness-in-arcgis10/m-p/420892#M2498</guid>
      <dc:creator>AnthonyFarndon</dc:creator>
      <dc:date>2011-10-26T12:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: Symbol Z Offset weirdness in ArcGIS10</title>
      <link>https://community.esri.com/t5/3d-questions/symbol-z-offset-weirdness-in-arcgis10/m-p/420893#M2499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I did not experience the same thing but something similar. I had a line feature class and I set the base height to a TIN. Then I extruded the line which looked fine like a fence. I then wanted to make this a multipatch so I saved and exported the Layer file to Multipatch. When I brought the multipatch into the scene it was way above the surface. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So&lt;/SPAN&gt;&lt;STRONG&gt; in my case the fix was to interpolate the feature class shapes into true 3D features &lt;/STRONG&gt;&lt;SPAN&gt;using the same TIN.&amp;nbsp; I then repeated the process with the 3D lines and it worked "as advertized".&amp;nbsp; I think there something funky going on if you set base height an existing surface and then tinker around with the 3D properties and symbology.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Try interpolating your shapes to 3D then try symbolizing again.&amp;nbsp; You are right that this should work especially because many people use symbology to create globes, cubes and other 3D symbols then convert to multipatch and calculate volume, etc.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Oct 2011 13:05:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/3d-questions/symbol-z-offset-weirdness-in-arcgis10/m-p/420893#M2499</guid>
      <dc:creator>JakubSisak</dc:creator>
      <dc:date>2011-10-27T13:05:41Z</dc:date>
    </item>
  </channel>
</rss>

