Public Member Functions | |
virtual QueryOrder | order () const =0 |
virtual bool | hasKnnQuery () const =0 |
virtual KnnQueryDescriptorHandle | getKnnQuery () const =0 |
virtual bool | hasRegionQuery () const =0 |
virtual GeometryHandle | getRegionQuery () const =0 |
virtual bool | requiresSorting () const =0 |
virtual SortOrder | getSortingOrder () const =0 |
![]() | |
virtual void | Delete () |
Static Public Member Functions | |
static ISpatialQueryDescriptor * | New (KnnQueryDescriptorHandle knnQuery, SortOrder sort=SortOrder::unsorted) |
create a new spatial query descriptor object More... | |
static ISpatialQueryDescriptor * | New (GeometryHandle regionQuery, SortOrder sort=SortOrder::unsorted) |
static ISpatialQueryDescriptor * | New (KnnQueryDescriptorHandle knnQuery, GeometryHandle regionQuery, SortOrder sort=SortOrder::unsorted) |
perform knn search and than region query ( More... | |
static ISpatialQueryDescriptor * | New (GeometryHandle regionQuery, KnnQueryDescriptorHandle knnQuery, SortOrder sort=SortOrder::unsorted) |
perform region query and than knn search ( More... | |
|
static |
perform region query and than knn search (
|
static |
perform knn search and than region query (
|
static |
create a new spatial query descriptor object
In case of knn queries the point are always sorted by the distance in ascending order (2d distances in case of 2d knn query and 3d distances in case of 3d knn query). Hence it is not necessary to speicify a sorting order parameter.