for geometries indexed into the geo_shape field, it would be helpful to be able to aggregate on the type of geometry.
Example use cases:
(1) for UX-applications that need to present a different UX based on the type-of geometries stored in the index.
- e.g. for styling,
- show an icon-editor for indices that have points in
geo_shape
- show a fill/outline-editor for indices that have polygons/multipolygons stored.
(2) count/unique counts are especially relevant, but could be appropriate for all aggregations
(3) Similarly, it would be great to be able to specify filters on the data based on geometry-type
- e.g. only query for points for POI-type data.
This would be similar to the ST_GeometryType function in SQL.
for geometries indexed into the
geo_shapefield, it would be helpful to be able to aggregate on the type of geometry.Example use cases:
(1) for UX-applications that need to present a different UX based on the type-of geometries stored in the index.
geo_shape(2) count/unique counts are especially relevant, but could be appropriate for all aggregations
(3) Similarly, it would be great to be able to specify filters on the data based on geometry-type
- e.g. only query for points for POI-type data.
This would be similar to the
ST_GeometryTypefunction in SQL.