---
title: "Geometries support in ontologies"
canonical: "https://onesaitplatform.refined.site/space/DOCT/2220828141/Geometries%20support%20in%20ontologies"
format: markdown
---
Until version **1.3.1-Barbarian**, when an ontology was created and the user wanted to use Geospatial Information, it was possible to define a field type as **geometry**, being able to store in this field the longitude and latitude of a point, following the GeoJSON standard.
However, if the user wanted to introduce another type of geometry, such as lineStrings or Polygons, he/she had to manually modify the Ontology Scheme and adapt the geometry schema from Point type to LineString or Polygon type, with the annoyance that this is supposed to the user.
Therefore, from **1.3.1-Barbarian-RC2** the range of possibilities is extended when selecting the type of geometry to be used, being able to choose between the following:
- **Points**
- **MultiPoints**
- **LineStrings**
- **MultiLineStrings**
- **Polygons**
- **MultiPolygons**
> ✅ ### Types of vectorial geometries
> ✅
> ✅ Would you like to know more about each type of geometry? Take a look at the **[GeoJSON Draft Appendix](https://tools.ietf.org/html/rfc7946#page-22)**, where examples are shown for each type of geometry.
Thanks to this improvement, it's possible to define in a fast and efficient way the needed Geometry Scheme for each case. For example, in the case of a Polygon Geometry, when making the CRUD of the Ontology it's possible to set the multiple coordinates quickly and easily.
When the user wants to generate a Layer from the Ontology in **My GIS Layers**, choosing the **geometry** field will directly recognize the geometry defined for the property.
Finally, when the layer is represented in a map through **My GIS Viewers**, the polygon is perfectly represented from the coordinates provided.
