Spatial join

Fundamental to the spatial join operation is the formulation of a spatial relationship between two geometric primitives as a logical predicate; that is, a criterion that can be evaluated as true or false. For example, "A is less than 5km from B" would be true if the distance between points A and B is 3km, and false if the distance is 10km. These relation predicates can be of two types: • A Topological relation is a qualitative relationship between two shapes that does not depend on a measurable space (that is, coordinates). Common examples of such predicates include "A is completely inside B," "A overlaps B," "A is adjacent to B" (i.e., sharing a boundary but no interior), and "A is disjoint from B" (not touching at all). These are commonly specified according to some form of the 9-Intersection Model, which is incorporated into the international Simple Feature Access specification (ISO 19125-2). • A Metric relation is a quantitative (measurable) relationship between two shapes in a coordinate space, most commonly a distance or direction. Common examples include "A is due north of B" or "A is less than 5 km from B." Not all software implementations support metric relations. Note that some relations are commutative (e.g., A overlaps B if and only if B overlaps A) while others are not (e.g., A is within B does not mean B is within A). The geometric primitives involved in these relations may be of any dimension (points, lines, or regions), but some relations may only have meaning with certain dimensions. For example, "A is within B" has a clear meaning if A is a point and B is a region, but is meaningless if both A and B are points. Other relations may be vague; for example, the distance between two regions or two lines may be interpreted as the minimal distance between their closest boundaries, or a mean distance between their centroids. == Operation ==

As in a relational table join as defined in the relational algebra, two input layers or tables are provided (hereafter X and Y), and the output is a table containing all of the columns of each of the inputs (or some subset thereof if selected by the user). The rows of the new table are a subset of Cross join or Cartesian product of the two tables, all possible pairs of rows {X1-Y1, X1-Y2, X1-Y3, X2-Y1, X2-Y2, X2-Y3, X3-Y1, X3-Y2, X3-Y3, ...}. Rather than include all possible combinations, each pair is evaluated according to the given spatial predicate; those for which the predicate is true are considered "matching" and are retained, while those for which the predicate is false are discarded. For example, consider the following two tables: When the spatial join is executed, the direction of attachment must be specified, for two reasons: 1) the given spatial predicate may not be commutative, and 2) there is often a many-to-one relationship between the rows (e.g., many students are inside each school district). In the example above, a common goal would be to join the schools table to the students table (the target table), with the relation predicate being "student.residence within school.district." Assuming that the districts do not overlap, each student point will be in no more than one school district, so the output would have the same rows as the students table, with the corresponding school attributes attached, as: The reverse operation, in this case attaching the student information to the schools table, is not as simple because many rows must be joined to one row. Some GIS software does not allow this operation, but most implementations allow for an aggregate join, in which aggregate summaries of the matching rows can be included, such as arrays, counts, sums, or means. For example, the result table might look like: Another option when there are multiple matches is to use some criterion to select one of the rows from the matching set, usually a spatial optimization criterion. For example, one could join the school building points (not the districts) to the student residents points by selecting the school that is nearest to each student. Not all software implements this option directly, although in some cases it can be derived through a combination of tools. == External links ==