Skip to main content
Source

​
pub async fn filter_by_radius( &self, table_name: String, view_name: String, x_column_name: String, x_center: f64, y_column_name: String, y_center: f64, radius: f64, ) -> Result<FilterByRadiusResponse, KineticaError>

Filter a dataset for records within a circle’s boundary

Calculates which objects from a table lie within a circle with the given radius and center point (i.e. circular NAI). The operation is synchronous, meaning that a response will not be returned until all the objects are fully available. The response payload provides the count of the resulting set. A new resultant set (view) which satisfies the input circular NAI restriction specification is also created if a view_name is passed in as part of the request.

For track data, all track points that lie within the circle plus one point on either side of the circle (if the track goes beyond the circle) will be included in the result.

  • table_name - Name of the table on which the filter by radius operation will be performed, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table.
  • view_name - If provided, then this will be the name of the view containing the results, in [schema_name.]view_name format, using standard name resolution rules and meeting table naming criteria. Must not be an already existing table or view.
  • x_column_name - Name of the column to be used for the x-coordinate (the longitude) of the center.
  • x_center - Value of the longitude of the center. Must be within [-180.0, 180.0].
  • y_column_name - Name of the column to be used for the y-coordinate-the latitude-of the center.
  • y_center - Value of the latitude of the center. Must be within [-90.0, 90.0].
  • radius - The radius of the circle within which the search will be performed. Must be a non-zero positive value. It is in meters; so, for example, a value of ‘42000’ means 42 km.
Source

​
pub async fn filter_by_radius_with_opts( &self, table_name: String, view_name: String, x_column_name: String, x_center: f64, y_column_name: String, y_center: f64, radius: f64, options: FilterByRadiusRequestOptions, ) -> Result<FilterByRadiusResponse, KineticaError>

Filter a dataset for records within a circle’s boundary

Calculates which objects from a table lie within a circle with the given radius and center point (i.e. circular NAI). The operation is synchronous, meaning that a response will not be returned until all the objects are fully available. The response payload provides the count of the resulting set. A new resultant set (view) which satisfies the input circular NAI restriction specification is also created if a view_name is passed in as part of the request.

For track data, all track points that lie within the circle plus one point on either side of the circle (if the track goes beyond the circle) will be included in the result.

  • table_name - Name of the table on which the filter by radius operation will be performed, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table.
  • view_name - If provided, then this will be the name of the view containing the results, in [schema_name.]view_name format, using standard name resolution rules and meeting table naming criteria. Must not be an already existing table or view.
  • x_column_name - Name of the column to be used for the x-coordinate (the longitude) of the center.
  • x_center - Value of the longitude of the center. Must be within [-180.0, 180.0].
  • y_column_name - Name of the column to be used for the y-coordinate-the latitude-of the center.
  • y_center - Value of the latitude of the center. Must be within [-90.0, 90.0].
  • radius - The radius of the circle within which the search will be performed. Must be a non-zero positive value. It is in meters; so, for example, a value of ‘42000’ means 42 km.
  • options - The optional parameters; any left unset take the server’s defaults.

Sends a pre-built FilterByRadiusRequest to the /filter/byradius endpoint.

Sends a pre-built FilterByRadiusRequest to a specific worker URL, bypassing HA head-node selection. Used for multi-head access.