Proceedings of the 14th Annual ACM International Symposium on Advances in Geographic Information Systems 2006
DOI: 10.1145/1183471.1183501
|View full text |Cite
|
Sign up to set email alerts
|

Exploiting a page-level upper bound for multi-type nearest neighbor queries

Abstract: Given a query point and a collection of spatial features, a multi-type nearest neighbor (MTNN) query finds the shortest tour for the query point such that only one instance of each feature is visited during the tour. For example, a tourist may be interested in finding the shortest tour which starts at a hotel and passes through a post office, a gas station, and a grocery store. The MTNN query problem is different from the traditional nearest neighbor query problem in that there are many objects for each featur… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
19
0

Year Published

2008
2008
2021
2021

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 24 publications
(19 citation statements)
references
References 27 publications
0
19
0
Order By: Relevance
“…Furthermore, to minimize I/O costs, R-LORD computes the minimum bounding rectangle (MBR) of all ellipses generated from length-i optimal sub-routes, as shown in Figure 2(b), and uses this MBR as a range query to retrieve points from the R-tree [9] that indexes the category to be examined during the (i + 1) th step. PLUB [11] decomposes a general optimal route query to multiple total-order queries and processes them individually, e.g., using R-LORD. For instance, the query in Figure 1 is decomposed into three total-order queries: museum → restaurant → pub, restaurant → museum → pub, and restaurant → pub → museum.…”
Section: Optimal Route Query Processingmentioning
confidence: 99%
See 2 more Smart Citations
“…Furthermore, to minimize I/O costs, R-LORD computes the minimum bounding rectangle (MBR) of all ellipses generated from length-i optimal sub-routes, as shown in Figure 2(b), and uses this MBR as a range query to retrieve points from the R-tree [9] that indexes the category to be examined during the (i + 1) th step. PLUB [11] decomposes a general optimal route query to multiple total-order queries and processes them individually, e.g., using R-LORD. For instance, the query in Figure 1 is decomposed into three total-order queries: museum → restaurant → pub, restaurant → museum → pub, and restaurant → pub → museum.…”
Section: Optimal Route Query Processingmentioning
confidence: 99%
“…Since the properties of G Q are rather difficult to quantify, we consider three specific types of visit order graphs: one without any order constraints between data categories, one with a complete order of all categories, and a bipartite graph that requires half (i.e., m/2) of the categories be visited before the remaining ones. Zero-order and total-order graphs are common definitions used in previous studies on the optimal route query, e.g., [11], [13], and the bipartite graph has properties between the two extremes. In addition, we classify queries based on the effectiveness of the greedy algorithm.…”
Section: Experimental Evaluationmentioning
confidence: 99%
See 1 more Smart Citation
“…Several papers [3,10,11,14] study route-search queries over datasets in which objects have neither scores nor probabilities. The work of [15] investigates two variants of the shortest-route problem.…”
Section: Related Workmentioning
confidence: 99%
“…An OSR query retrieves a route of minimum length starting from a given source location and passing through a number of locations (with different types) in a particular order imposed on the types of the locations. A multi-type nearest neighbor (MTNN) query solution was proposed in [13] by Ma et al Given a query point and a collection of locations (with difference types), a MTNN query finds the shortest path for the query point such that only one instance of each type is visited during the trip. From a spatial query perspective, MTNN is an extended solution of OSR by exploiting a page-level upper bound.…”
Section: Route Planning Querymentioning
confidence: 99%