URL: http://<db.host>:<db.port>/filter/byseries
Filters objects matching all points of the given track (works only on track type data). It allows users to specify a particular track to find all other points in the table that fall within specified ranges (spatial and temporal) of all points of the given track. Additionally, the user can specify another track to see if the two intersect (or go close to each other within the specified ranges). The user also has the flexibility of using different metrics for the spatial distance calculation: Euclidean (flat geometry) or Great Circle (spherical geometry to approximate the Earth's surface distances). The filtered points are stored in a newly created result set. The return value of the function is the number of points in the resultant set (view).
This operation is synchronous, meaning that a response will not be returned until all the objects are fully available.
Input Parameter Description
Name | Type | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
table_name | string | Name of the table on which the filter by track operation will be performed, in [schema_name.]table_name format, using standard name resolution rules. Must be a currently existing table with a track present. | ||||||||||||
view_name | string | 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. The default value is ''. | ||||||||||||
track_id | string | The ID of the track which will act as the filtering points. Must be an existing track within the given table. | ||||||||||||
target_track_ids | array of strings | Up to one track ID to intersect with the "filter" track. If any provided, it must be an valid track ID within the given set. | ||||||||||||
options | map of string to strings | Optional parameters. The default value is an empty map ( {} ).
|
Output Parameter Description
The GPUdb server embeds the endpoint response inside a standard response structure which contains status information and the actual response to the query. Here is a description of the various fields of the wrapper:
Name | Type | Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
status | String | 'OK' or 'ERROR' | |||||||||||||
message | String | Empty if success or an error message | |||||||||||||
data_type | String | 'filter_by_series_response' or 'none' in case of an error | |||||||||||||
data | String | Empty string | |||||||||||||
data_str | JSON or String | This embedded JSON represents the result of the /filter/byseries endpoint:
Empty string in case of an error. |