pub async fn filter_by_radius_geometry( &self, table_name: String, view_name: String, column_name: String, x_center: f64, y_center: f64, radius: f64, ) -> Result<FilterByRadiusGeometryResponse, KineticaError>
Filter a dataset for geospatial geometry objects intersecting a circle’s boundary
Calculates which geospatial geometry objects from a table intersect 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.
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.column_name- Name of the geospatial geometry column to be filtered.x_center- Value of the longitude of the center. Must be within [-180.0, 180.0].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.
pub async fn filter_by_radius_geometry_with_opts( &self, table_name: String, view_name: String, column_name: String, x_center: f64, y_center: f64, radius: f64, options: FilterByRadiusGeometryRequestOptions, ) -> Result<FilterByRadiusGeometryResponse, KineticaError>
Filter a dataset for geospatial geometry objects intersecting a circle’s boundary
Calculates which geospatial geometry objects from a table intersect 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.
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.column_name- Name of the geospatial geometry column to be filtered.x_center- Value of the longitude of the center. Must be within [-180.0, 180.0].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.
pub async fn filter_by_radius_geometry_raw( &self, request: &FilterByRadiusGeometryRequest, ) -> Result<FilterByRadiusGeometryResponse, KineticaError>
Sends a pre-built FilterByRadiusGeometryRequest to the /filter/byradius/geometry endpoint.
pub async fn filter_by_radius_geometry_from_url( &self, url: &str, request: &FilterByRadiusGeometryRequest, ) -> Result<FilterByRadiusGeometryResponse, KineticaError>
Sends a pre-built FilterByRadiusGeometryRequest to a specific worker URL, bypassing HA head-node selection. Used for multi-head access.