<?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>idea Automatically Set Elevation of KMZ 3D Model from Loaded Source in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/automatically-set-elevation-of-kmz-3d-model-from/idi-p/940341</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;KML/KMZ is a common format for sharing geopositioned 3D models.&amp;nbsp; My office publishes a large amount of this content.&amp;nbsp; Some of it we create; some we receive from partners - so simply removing KML/KMZ from the business process is not a possibility.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that importing and publishing KML/KMZ 3D models is tedious, but I know it could be made much easier with only a few simple changes on Esri's part!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently, when a KMZ model is loaded into a 3D scene in ArcGIS Pro (imported into a 3D multipatch), the analyst must go through a process of determining the objective elevation of the multipatch, and then perform a manual move by editing the Z-value.&amp;nbsp; If this is not done prior to publication as a 3D web scene in Portal, the service will render the model at a 0/MSL altitude, causing it to draw "under" the elevation source in the web scene.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the current, bad workflow is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Analyst imports 3D KMZ model into ArcGIS Pro local/global 3D scene as multipatch.&lt;/LI&gt;&lt;LI&gt;Analyst asks, huh, where's my model?&lt;/LI&gt;&lt;LI&gt;Analyst turns off the elevation source and sees, there's my model.&lt;/LI&gt;&lt;LI&gt;Analyst gets center coord of model.&lt;/LI&gt;&lt;LI&gt;Analyst turns back on the elevation layer.&lt;/LI&gt;&lt;LI&gt;Analyst selects a location to gather the elevation measurement.&lt;/LI&gt;&lt;LI&gt;Analyst edits the multipatch.&lt;/LI&gt;&lt;LI&gt;Analyst moves the multipatch to an absolute z-value.&lt;/LI&gt;&lt;LI&gt;Analyst types in the value gathered 3 steps previously.&lt;/LI&gt;&lt;LI&gt;Analyst saves the multipatch.&lt;/LI&gt;&lt;LI&gt;Analyst sees, now the model correctly renders on the loaded elevation source.&lt;/LI&gt;&lt;LI&gt;Analyst shares content as a web scene.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;This process could be made so much better.&lt;/STRONG&gt;&amp;nbsp; I would like to see the following functionality: if a model is loaded in Pro and its elevation setting is set to "on the Ground"; then publishing that model as a web scene should cause the multipatch to inherit whatever that elevation value is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the better workflow, broken down, would look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Analyst imports 3D KMZ model into ArcGIS Pro local/global 3D scene as a multipatch. (currently works)&lt;/LI&gt;&lt;LI&gt;Analyst sets properties of multipatch to clamp to loaded elevation source (Ground). (currently works, tho it needs a refresh)&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;Analyst shares workspace as 3D web scene, which automatically sets the model's elevation value upon publication. (currently not available).&lt;/STRONG&gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Nov 2019 16:40:02 GMT</pubDate>
    <dc:creator>EricEagle</dc:creator>
    <dc:date>2019-11-25T16:40:02Z</dc:date>
    <item>
      <title>Automatically Set Elevation of KMZ 3D Model from Loaded Source</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/automatically-set-elevation-of-kmz-3d-model-from/idi-p/940341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;KML/KMZ is a common format for sharing geopositioned 3D models.&amp;nbsp; My office publishes a large amount of this content.&amp;nbsp; Some of it we create; some we receive from partners - so simply removing KML/KMZ from the business process is not a possibility.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that importing and publishing KML/KMZ 3D models is tedious, but I know it could be made much easier with only a few simple changes on Esri's part!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently, when a KMZ model is loaded into a 3D scene in ArcGIS Pro (imported into a 3D multipatch), the analyst must go through a process of determining the objective elevation of the multipatch, and then perform a manual move by editing the Z-value.&amp;nbsp; If this is not done prior to publication as a 3D web scene in Portal, the service will render the model at a 0/MSL altitude, causing it to draw "under" the elevation source in the web scene.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the current, bad workflow is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Analyst imports 3D KMZ model into ArcGIS Pro local/global 3D scene as multipatch.&lt;/LI&gt;&lt;LI&gt;Analyst asks, huh, where's my model?&lt;/LI&gt;&lt;LI&gt;Analyst turns off the elevation source and sees, there's my model.&lt;/LI&gt;&lt;LI&gt;Analyst gets center coord of model.&lt;/LI&gt;&lt;LI&gt;Analyst turns back on the elevation layer.&lt;/LI&gt;&lt;LI&gt;Analyst selects a location to gather the elevation measurement.&lt;/LI&gt;&lt;LI&gt;Analyst edits the multipatch.&lt;/LI&gt;&lt;LI&gt;Analyst moves the multipatch to an absolute z-value.&lt;/LI&gt;&lt;LI&gt;Analyst types in the value gathered 3 steps previously.&lt;/LI&gt;&lt;LI&gt;Analyst saves the multipatch.&lt;/LI&gt;&lt;LI&gt;Analyst sees, now the model correctly renders on the loaded elevation source.&lt;/LI&gt;&lt;LI&gt;Analyst shares content as a web scene.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;This process could be made so much better.&lt;/STRONG&gt;&amp;nbsp; I would like to see the following functionality: if a model is loaded in Pro and its elevation setting is set to "on the Ground"; then publishing that model as a web scene should cause the multipatch to inherit whatever that elevation value is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the better workflow, broken down, would look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Analyst imports 3D KMZ model into ArcGIS Pro local/global 3D scene as a multipatch. (currently works)&lt;/LI&gt;&lt;LI&gt;Analyst sets properties of multipatch to clamp to loaded elevation source (Ground). (currently works, tho it needs a refresh)&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;Analyst shares workspace as 3D web scene, which automatically sets the model's elevation value upon publication. (currently not available).&lt;/STRONG&gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Nov 2019 16:40:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/automatically-set-elevation-of-kmz-3d-model-from/idi-p/940341</guid>
      <dc:creator>EricEagle</dc:creator>
      <dc:date>2019-11-25T16:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically Set Elevation of KMZ 3D Model from Loaded Source - Status changed to: Under Consideration</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/automatically-set-elevation-of-kmz-3d-model-from/idc-p/1001818#M14345</link>
      <description />
      <pubDate>Mon, 16 Nov 2020 17:30:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/automatically-set-elevation-of-kmz-3d-model-from/idc-p/1001818#M14345</guid>
      <dc:creator>Andrew--Johnson</dc:creator>
      <dc:date>2020-11-16T17:30:10Z</dc:date>
    </item>
  </channel>
</rss>

