Results obtained are promising, however it is necessary to carefully study other complex cases. The evaluation is made through a case study corresponding to a real situation in Portugal previously identified. The 3D visualisation requirements against which CityEngine was evaluated are classified into three main categories: cadastral requirements, visualisation requirements and non-functional requirements. This paper focuses primarily on 3D visualisation, not on data management or data delivery. This work proposes the evaluation of CityEngine's suitability as a 3D cadastral visualisation tool, since it was not developed specifically for that purpose. One of those systems is the ESRI CityEngine. If these systems can somehow be reutilized in the 3D cadastre context, associate costs might be lower by building a system out of scratch. The 3D modelling of urban environments utilizes 3D visualisation systems. Thus, research on 3D cadastral visualisation needs more investigation. However, they still require maturation and validation by the users before being able to be used in real life situations. Currently, several 3D visualisation applications and cadastral prototypes have been developed around the world. In addition, multipatch features can be constructed programmatically using ArcObjects.3D visualisation is a graphical way to identify and spatially communicate the complexity of a large number of real life situations of overlapping and encroachments in 2D or 3D land and property interests (e.g., buildings with complex architecture, infrastructures above or below Earth surface, natural resources and corresponding rights).
The Import 3D Files geoprocessing tool will do the same but provides more import format options such as VRML. The Layer 3D To Feature Class geoprocessing tool will convert points symbolized by a variety of model formats (such as SketchUp, OpenFlight, 3ds, or COLLADA) to a multipatch feature class. Multipatch features can be created by importing existing 3D models into ArcGIS using geoprocessing tools. This assumption can be problematic, particularly if x,y units are geographic (latitude-longitude). If no units are defined, ArcGIS will assume that the z-units match the x,y units.
The units and datum for a feature class's z-values should be defined on the containing feature dataset (if one exists) or on the feature class itself (if there is no feature dataset). Both methods are fully supported in the display and analysis of the resulting 3D feature class. The values can represent absolute heights or relative-to-ground heights. Z-values are used for representing the shape and elevation of your multipatch features. Learn more about converting 2D features to 3D features What do the z-values represent? Learn more about creating new 3D feature classes To create a new multipatch feature class, simply choose Multipatch Features from the Type drop-down menu when defining the feature class's geometry. How do I create a multipatch feature class? You can use the Is Closed geoprocessing tool to verify that a multipatch is properly closed.Įxamples of multipatch features include textured buildings, lamp posts, trees, subsurface geologic formations, underground structures, or certain types of analytic surfaces. The patches must not intersect each other, and there must be no gaps or empty spaces in the shell. The patches it is composed of must all have the same counterclockwise orientation of their coordinates and participate in defining the shell of the volume. The feature must represent one distinct volume. For a multipatch to be considered closed, it must be constructed in the correct fashion. Closed multipatches may be used in additional analysis tools, such as Union 3D and Intersect 3D. Some multipatch features are considered closed, meaning they properly define a volume. While it is possible to model the base z-value of a multipatch using a numeric feature attribute, this option may not support all the same analysis and interaction options that are available when using embedded z-values. All multipatches store z-values as part of the coordinates used to construct patches.