![]() ![]() ![]() You could try editing the multipatch in SketchUp by the way of Collada then replacing the model when you are finished editing) ArcScene 3D Editor -> Replace with Model (This should be possible according to documentation but I have not tried. Exactly how were they created? Can you provide some screen captures? (You might need to create more complex 3D solid object features in a 3rd party 3D drawing software as ArcGIS is very limited in this area. I suspect your polygon multipatches do not fully enclose a volume. Intersection also succeeded without errors. (See screen captures below) I then created some circular polygons, extruded them and converted them to multipatch features. Intersection succeeded without errors and produced expected results. I was also able to calculate volume of the spheres. It didn't work: my output had the same amount of entities only. I've inserted the required parameters which are the 3d layer (not feature class) as input, an output multipatch feature class and a grouping definition by the OBJECTID field. I tried running an example with spheres and created 2 intersecting multipatch feature classes. I've tried to use 'Layer 3D To Feature Class' Geoprocessing tool. Personally, I have not had a lot of success using "Extrude Between" with complex surfaces) (Unless you extrude between 2 TIN surfaces which should produce a closed multipatch. Multipatch features created with the Interpolate multipatch to polygon (using a surface) tool can likely not be closed. To close a multipatch feature, it must completely enclose a volume. You can publish hosted scene layers using 3D point data beginning with ArcGIS 10.4 Data Store and Portal for ArcGIS 10.4. It makes sense to use this function to group a collection of 3D polygon faces into a single multipatch polyhedron. Your portal must be configured with ArcGIS Data Store (10.3.1 or later release) to publish hosted scene layers using multipatch data. In this case, what is the advantage of the conversion? These are downgraded to polygons because they are shared backend and cannot support multipatch geometries. If grouping by ObjectID then you will have the same number of entities - i.e one multipatch for each polygon. You can check whether the geometry is MULTIPATCH or POLYGON on the Feature Layer Properties -> Source -> Geometry. You report that your "output had the same amount of entities only they all were having the same geometry." It lists several other caveats why the conversion might not work. They have no fixed orientation that can be used for exporting. The position of these 2D symbols areÄynamically oriented to face the camera position in a 3D scene, so The Layer 3D To Feature Class docs for ArcGIS Pro state "[Marker One clue is that you are converting billboards. Without more information, we cannot be sure why it failed in this case. There are many reasons why 'Layer 3D To Feature Class'will fail. ![]()
0 Comments
Leave a Reply. |