Three new simple but useful spatial functions

[craigtaverner]

Three new simple but useful spatial functions

• ST_Dimension (topological dimension)
  • The topological dimension is 0 for points, 1 for lines and 2 for polygons. This is important in understanding how centroids are calculated in ST_CENTROID_AGG, where higher dimensions completely remove the contribution from lower ones.
  • See the PostGIS equivalent at https://postgis.net/docs/ST_Dimension.html
• ST_GeometryType
  • A string name of the geometry type: ST_Point, ST_LineString, etc.
  • See the PostGIS equivalent at https://postgis.net/docs/ST_GeometryType.html
• ST_IsEmpty
  • A boolean flag for whether the geometry is empty or not
  • See PostGIS equivalent at https://postgis.net/docs/ST_IsEmpty.html

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[elasticsearchmachine]

Hi @craigtaverner, I've created a changelog YAML for you.

[github-actions]

🔍 Preview links for changed docs

• docs/reference/query-languages/esql/functions-operators/spatial-functions/st_dimension.md
• docs/reference/query-languages/esql/functions-operators/spatial-functions/st_geometrytype.md
• docs/reference/query-languages/esql/functions-operators/spatial-functions/st_isempty.md
• docs/reference/query-languages/esql/kibana/docs/functions/st_dimension.md
• docs/reference/query-languages/esql/kibana/docs/functions/st_geometrytype.md
• docs/reference/query-languages/esql/kibana/docs/functions/st_isempty.md

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel