KML/KMZ is a common format for sharing geopositioned 3D models. My office publishes a large amount of this content. Some of it we create; some we receive from partners - so simply removing KML/KMZ from the business process is not a possibility.
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!
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. 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.
So the current, bad workflow is:
This process could be made so much better. 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.
So the better workflow, broken down, would look like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.