![]() The level of effort necessary for 3D polygons to meet these requirements is high, and therefore they are not recommended as a workflow for maintaining 3D areal faces.ģD polygon features store z-coordinates embedded inside their feature geometry, or Shape field, of their feature class. This is because the surface of a 3D polygon can only be guaranteed to be calculated in a consistent manner when there are exactly three vertices (constructing a 3D triangle), or when the vertices represent a planar surface. If you need to model the 3D bumpiness of the interior area of a polygon, the vast majority of use cases can only be met using multipatch features or a functional surface (such as a TIN). In nearly all instances, polygons should be modeled as 3D features only when the exterior perimeter needs to include z-values, or heights, to correctly locate itself in 3D space. Polygon features have two separate parts that can potentially be modeled in 3D: their exterior perimeter line and their interior area. ![]() Two ways to create a 3D polygon feature class?Ī polygon feature is a GIS object that stores its geographic representation-a series of x and y coordinate pairs that enclose an area-as one of its properties (or fields) in the row in the database.Sketch properties: Vertex-level sketch properties cannot be edited on the Edit Sketch Properties dialog box.Topology edits: Multipatch features cannot participate in a topology.Various editing tasks: You cannot extend or trim multipatch geometries or reshape an edge of a multipatch feature using a 2D line.Split tool: Splitting 3D multipatches using a 2D line is not supported.The list below contains some of the editing actions that are not available: ![]() Some editing actions are not appropriate for multipatch geometries and have been made unavailable for use with multipatch features. ![]() Unsupported editing actions for multipatches
0 Comments
Leave a Reply. |