Geometry QML Type

Base type for types that represent geometric shapes. More...

• List of all members, including inherited members

Properties

• dimension : int
• empty : bool
• extent : Envelope
• geometryType : Enums.GeometryType
• hasCurves : bool
• hasM : bool
• hasZ : bool
• json : jsobject
• spatialReference : SpatialReference
• unknownJson : jsobject
• unsupportedJson : jsobject

Signals

• emptyChanged()
• extentChanged()
• hasCurvesChanged()
• hasMChanged()
• hasZChanged()
• spatialReferenceChanged()

Methods

• bool equals(Geometry other)
• bool equalsWithTolerance(Geometry other, double tolerance)

Detailed Description

Note: You cannot declare or create a component of this type in QML code.

Geometry is the base class for two-dimensional (x,y) or three-dimensional (x,y,z) geometries, such as Point and Polyline objects. Objects that inherit from the Geometry class may also include an m (measure) value for each vertex. The Geometry class provides functionality common to all types of geometry; Point, Multipoint, Polyline, Polygon, and Envelope all inherit from Geometry and represent different types of shapes.

Geometries are used throughout the API, for example to define the shape of a feature or graphic, the extent of a layer, or as inputs and outputs of different types of tasks. Geometry examples include features created to be stored in a geodatabase or read from a non-editable layer, and features returned from tasks such as a spatial query, geocode operation, network trace, or geoprocessing task.

This QML type supports the following default properties. A default property may be declared inside another declared object without being assigned explicitly to a property.

Immutability

All geometries are immutable, which offers important benefits. For example, they are inherently thread-safe, help prevent inadvertent changes, and allow for certain performance optimizations. Instead of changing the properties of existing geometries, you can create and update geometries using the various subclasses of GeometryBuilder (for example, PolygonBuilder), which can represent the state of a geometry under construction while allowing modifications, thus enabling editing workflows.

Additionally, GeometryEngine offers a range of topological and relational operations and spatial transformations that read the content of existing geometries and create new geometries, for example, project, move, scale, rotate, buffer, union, and so on.

Spatial references

The coordinates that define a geometry only have meaning in the context of the Geometry's SpatialReference. The vertices and the spatial reference together allow your app to translate a real-world object from its location on Earth to its location on your map or scene.

In some cases, a geometry's spatial reference may not be set. For example, a Graphic that does not have a spatial reference is drawn using the same spatial reference as the MapView to which it was added. If the coordinates are in a different SpatialReference, the graphics may not display in the correct location, or at all.

When using a GeometryBuilder to create a Polyline or Polygon from a collection of Point, you don't need to set the spatial reference of every point before you add it to the builder, because it is assigned the spatial reference of the builder itself. In most other cases, such as when using a geometry in geometry operations or when editing a feature table, Geometry::spatialReference must be set.

This QML type supports the following default properties. A default property may be declared inside another declared object without being assigned explicitly to a property.

Spatial reference and projection

Changing the coordinates of a geometry to have the same shape and location represented using a different SpatialReference is known as "projection" or sometimes as "reprojection". Because geometries are immutable, they do not have any member methods that project, transform, or otherwise modify their content.

GeometryEngine, however, provides a wide range of methods that read the content of geometries and modify that content to create new geometries. There are methods to GeometryEngine::project, GeometryEngine::moveGeodetic, GeometryEngine::cut, GeometryEngine::densify, and GeometryEngine::generalize geometries.

Dimension

Every non-empty Geometry has an inherent dimension (sometimes called the topological dimensionality) that indicates the general class of the Geometry.

• 0 - points and multipoints
• 1 - lines and polylines
• 2 - polygons and envelopes
• 3 - objects with volume

Serializing to JSON

Geometries can be serialized and de-serialized to and from JSON. ArcGIS REST API documentation describes the JSON representation of geometry objects. You can use this encoding and decoding mechanism to exchange geometries with REST Web services or to store them in text files.

Valid polygons have at least three vertices, and valid polylines, two vertices. When there are not enough of them, JSON serialization copies existing vertices to reach the minimum vertex count. This results in invalid (degenerate) geometries that can be parsed as the valid JSON for those geometry types.

See also JsonSerializable, GeometryBuilder, and GeometryEngine.

Property Documentation

Signal Documentation

Method Documentation