> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/reference/sql-structure/geometry/geometry-hierarchy.md).

# Geometry Hierarchy

## Description

Geometry is the base class. It is an abstract class. The instantiable subclasses of Geometry are restricted to zero-, one-, and two-dimensional geometric objects that exist in two-dimensional\
coordinate space. All instantiable geometry classes are defined so that valid instances of a geometry class are topologically closed (that is, all defined geometries include their boundary).

The base Geometry class has subclasses for Point, Curve, Surface, and GeometryCollection:

* [Point](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/point.md) represents zero-dimensional objects.
* Curve represents one-dimensional objects, and has a subclass [LineString](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/linestring.md), with sub-subclasses Line and LinearRing.
* Surface is designed for two-dimensional objects and has a subclass [Polygon](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/polygon.md).
* [GeometryCollection](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/geometrycollection.md) has specialized zero-, one-, and two-dimensional collection classes named [MultiPoint](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multipoint.md), [MultiLineString](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multilinestring.md), and [MultiPolygon](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multipolygon.md) for modeling geometries corresponding to collections of Points, LineStrings, and Polygons, respectively. MultiCurve and MultiSurface are introduced as abstract superclasses that generalize the collection interfaces to handle Curves and Surfaces.

Geometry, Curve, Surface, MultiCurve, and MultiSurface are defined as non-instantiable classes. They define a common set of methods for their subclasses and are included for extensibility.

[Point](/docs/server/reference/sql-statements/geometry-constructors/point-properties.md), [LineString](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties.md), [Polygon](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties.md), [GeometryCollection](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/geometrycollection.md), [MultiPoint](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multipoint.md),[MultiLineString](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multilinestring.md), and [MultiPolygon](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multipolygon.md) are instantiable classes.

<sub>*This page is licensed: GPLv2, originally from*</sub> [<sub>*fill\_help\_tables.sql*</sub>](https://github.com/MariaDB/server/blob/main/scripts/fill_help_tables.sql)

{% @marketo/form formId="4316" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mariadb.com/docs/server/reference/sql-structure/geometry/geometry-hierarchy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.