vtlim commented on code in PR #12555: URL: https://github.com/apache/druid/pull/12555#discussion_r921707017
########## docs/development/geo.md: ########## @@ -23,53 +23,83 @@ title: "Spatial filters" --> > Apache Druid supports two query languages: [Druid SQL](../querying/sql.md) > and [native queries](../querying/querying.md). -> This document describes functionality that is only available in the native language. +> This document describes a feature that is only available in the native language. -Apache Druid supports filtering specially spatially indexed columns based on an origin and a bound. +Apache Druid supports filtering spatially indexed columns based on an origin and a bound. + +This topic explains how to apply spatial filters. +For information on other filters supported by Druid, see [Query filters](../querying/filters.md). ## Spatial indexing -In any of the data specs, there is the option of providing spatial dimensions. For example, for a JSON data spec, spatial dimensions can be specified as follows: +Spatial indexing refers to ingesting data of a spatial data type, such as geometry or geography, into Druid. + +Spatial dimensions are sting columns that contain coordinates separated by a comma. Review Comment: I think this describes the result of ingestion a spatial dimension. Consider starting with how a spatial dimension gets ingested? Possibly something like, "Spatial dimensions are derived (generated? composed?) from two specified input dimensions. Druid stores spatial dimensions as comma-separated values in string columns." -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
