View source for DE-9IM

{{Short description|Topological model}}
[[File:DE-9IM-logoSmall.png|right|230px]]

{{Technical|date=May 2019}}

The '''Dimensionally Extended 9-Intersection Model''' ('''DE-9IM''') is a [[topological]] [[Interpretation (logic)|model]] and a [[Specification (technical standard)|standard]] used to describe the [[spatial relation]]s of two regions (two [[2D geometric model|geometries in two-dimensions]], '''R'''<sup>2</sup>), in [[geometry]], [[point-set topology]], [[geospatial topology]], and fields related to [[Spatial analysis|computer spatial analysis]]. The spatial relations expressed by the model are invariant to [[Rotation (mathematics)|rotation]], [[Translation (geometry)|translation]] and [[Scaling (geometry)|scaling]] transformations.

The matrix provides an approach for classifying geometry relations. Roughly speaking, with a true/false matrix domain, there are 512 possible 2D topologic relations, that can be grouped into ''binary classification schemes''. The English language contains about 10 schemes (relations), such as "intersects", "touches" and "equals". When testing two geometries against a scheme, the result is a '''''spatial predicate''''' named by the scheme.

The model was developed by Clementini and others<ref>
{{cite book |last1=Clementini |first1=Eliseo |first2 = Paolino | last2 = Di Felice | first3 = Peter | last3 = van Oosterom |editor1-first=David |editor1-last=Abel |editor2-last=Ooi |editor2-first=Beng Chin |chapter=A small set of formal topological relationships suitable for end-user interaction |title=Advances in Spatial Databases: Third International Symposium, SSD '93 Singapore, June 23–25, 1993 Proceedings |series=Lecture Notes in Computer Science |volume=692/1993 |year=1993 |publisher=Springer |doi=10.1007/3-540-56869-7_16 |pages=277–295|isbn=978-3-540-56869-8 |url=http://resolver.tudelft.nl/uuid:a2db9ae8-f768-4bff-ada3-966a6c8e9db6 }}</ref><ref>{{cite journal |last1=Clementini |first1=Eliseo |last2=Sharma |first2=Jayant |last3=Egenhofer |first3=Max J. |year=1994 |title=Modelling topological spatial relations: Strategies for query processing |journal=Computers & Graphics |volume=18 |issue=6 |pages=815–822 |doi=10.1016/0097-8493(94)90007-8 }}</ref> based on the seminal works of Egenhofer and others.<ref>{{cite journal | first1 = M.J. | last1 = Egenhofer | first2 = R.D.| last2 = Franzosa | year = 1991 | title = Point-set topological spatial relations | doi = 10.1080/02693799108927841 | journal = Int. J. GIS | volume = 5 | issue = 2 | pages = 161–174 | doi-access = free }}</ref><ref name="sdh1990">{{cite conference|first1=M.J. |last1=Egenhofer |first2=J.R. |last2=Herring |year=1990 |title=A Mathematical Framework for the Definition of Topological Relationships |book-title=Proceedings of the 4th International Symposium on Spatial Data Handling |url=http://www.spatial.maine.edu/~max/MJEJRH-SDH1990.pdf |url-status=dead |archive-url=https://web.archive.org/web/20100614161335/http://www.spatial.maine.edu/~max/MJEJRH-SDH1990.pdf |archive-date=2010-06-14 }}</ref> It has been used as a basis for standards of ''[[Information retrieval|queries]]'' and ''[[First-order logic|assertions]]'' in [[geographic information systems]] (GIS) and [[spatial database]]s.

== Matrix model ==
The DE-9IM model is based on a 3×3 [[intersection]] [[Matrix (mathematics)|matrix]] with the form:

{{NumBlk|:|<math>
\operatorname{DE9IM}(a,b) = \begin{bmatrix}
\dim(I(a) \cap I(b)) & \dim(I(a) \cap B(b)) & \dim(I(a) \cap E(b)) \\
\dim(B(a) \cap I(b)) & \dim(B(a) \cap B(b)) & \dim(B(a) \cap E(b))\\
\dim(E(a) \cap I(b)) & \dim(E(a) \cap B(b)) & \dim(E(a) \cap E(b))
\end{bmatrix}
</math>
|{{EquationRef|1}}}}

where {{tmath|\dim}} is the [[dimension]] of the [[Intersection (set theory)|intersection]] (∩) of the [[Interior of a manifold|interior]] (I), [[Boundary of a manifold|boundary]] (B), and [[Exterior (topology)|exterior]] (E) of geometries ''a'' and ''b''.

The terms ''interior'' and ''boundary'' in this article are used in the sense used in algebraic topology and manifold theory, not in the sense used in general topology: for example, the interior of a line segment is the line segment without its endpoints, and its boundary is just the two endpoints (in general topology, the interior of a line segment in the plane is empty and the line segment is its own boundary).

In the notation of topological space operators, the matrix elements can be expressed also as
{{NumBlk|:|{{math|1=''I''(''a'')=''a''<sup>o</sup> &nbsp;&nbsp; ''B''(''a'')=∂''a'' &nbsp;&nbsp; ''E''(''a'')=''a''<sup>''e''</sup>}}|{{EquationRef|2}}}}

The dimension of [[empty set]]s (∅) are denoted as −1 or {{mono|F}} (false). The dimension of non-empty sets (¬∅) are denoted with the maximum number of dimensions of the intersection, specifically {{mono|0}} for [[Point (geometry)|points]], {{mono|1}} for [[Line (geometry)|lines]], {{mono|2}} for [[area]]s.  Then, the [[Data domain|domain]] of the model is {{mset|1={{mono|0}},{{mono|1}},{{mono|2}},{{mono|F}} }}.

A simplified version of {{tmath|\dim(x)}} values are obtained mapping the values {{mset|1={{mono|0,1,2}} }} to {{mono|T}} (true), so using the [[boolean domain]] {{mset|1={{mono|T}},{{mono|F}} }}.  The matrix, denoted with operators, can be expressed as
{{NumBlk|:|<math>
\operatorname{bin}(\operatorname{DE9IM}(a,b)) = \operatorname{9IM}(a,b) = \begin{bmatrix}
a^o  \cap b^o \ne \emptyset   &   a^o \cap \partial{b} \ne \emptyset & a^o \cap b^e \ne \emptyset \\
\partial{a} \cap b^o\ne\emptyset   &    \partial{a} \cap \partial{b}\ne\emptyset  &  \partial{a} \cap b^e\ne\emptyset \\
a^e \cap b^o\ne\emptyset    &    a^e \cap \partial{b}\ne\emptyset   &   a^e  \cap b^e\ne\emptyset
\end{bmatrix}
</math>
|{{EquationRef|3}}}}

The elements of the matrix can be named as shown below:

{{NumBlk|:|<math>
\begin{bmatrix}
II & IB & IE \\
BI & BB & BE \\
EI & EB & EE
\end{bmatrix}
</math>
|{{EquationRef|4}}}}

Both matrix forms, with dimensional and boolean domains, can be [[Serialization|serialized]] as "''DE-9IM string codes''", which represent them in a single-line string pattern. Since 1999 the ''string codes'' have a [[#Standards|standard]]<ref name="firstStd">The "[[OpenGIS]] Simple Features Specification For SQL", [http://portal.opengeospatial.org/files/?artifact_id=829 Revision 1.1], was released at May 5, 1999. It was the first international standard to establish the format conventions for ''DE-9IM string codes'', and the names of the "Named Spatial Relationship predicates based on the DE-9IM" (see section with this title).</ref> format.

For output checking or pattern analysis, a matrix value (or a string code) can be checked by a "[[Mask (computing)|mask]]": a desired output value with optional [[asterisk]] symbols as [[Wildcard character|wildcards]] — that is, "{{mono|*}}" indicating output positions that the designer does not care about (free values or "don't-care positions").
The domain of the mask elements is {{mset|1={{mono|0}},{{mono|1}},{{mono|2}},{{mono|F}},{{mono|*}} }}, or {{mset|1={{mono|T}},{{mono|F}},{{mono|*}} }} for the boolean form.

The simpler models ''4-Intersection'' and ''9-Intersection'' were proposed before DE-9IM for expressing ''spatial relations''<ref name="4vs9">M. J. Egenhofer, J. Sharma, and D. Mark (1993) "[http://www.spatial.maine.edu/~max/4Vs9.pdf A Critical Comparison of the 4-Intersection and 9-Intersection Models for Spatial Relations: Formal Analysis] {{Webarchive|url=https://web.archive.org/web/20100614023708/http://www.spatial.maine.edu/~max/4Vs9.pdf |date=2010-06-14 }}", In: [http://mapcontext.com/autocarto/proceedings/auto-carto-11/index.html Auto-Carto XI] {{Webarchive|url=https://web.archive.org/web/20140925121313/http://mapcontext.com/autocarto/proceedings/auto-carto-11/index.html |date=2014-09-25 }}.</ref> (and originated the terms ''4IM'' and ''9IM'').  They can be used instead of the DE-9IM to optimize computation when input conditions satisfy specific constraints.

=== Illustration ===
Visually, for two overlapping polygonal geometries, the result of the function '''DE_9IM(''a'',''b'')''' looks like:<ref name="PostGISch4" />
{| border="0" align="center" 
|-
|
| align="center" |
{| border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0"
|-
| align="center" valign="middle" | ''b'' &nbsp; [[File:DE9IM b.svg|100px]]
|}
|-
| align="center" valign="middle" |
{| border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0"
|-
| align="center" valign="middle" | ''a''<br>[[File:DE9IM a.svg|100px]]
|}
|
{| border="0" class="wikitable"
|-
! align="center" | 
! align="center" | '''Interior'''
! align="center" | '''Boundary'''
! align="center" | '''Exterior'''
|-
| align="center" | '''Interior'''
| align="center" style="border-right: 2px solid #BCB; border-bottom: 2px solid #BCB;"| [[File:DE9IM II.svg|100px]]

&nbsp; <math>\dim[I(a){\color{red}\cap}I(b)] = 2</math> &nbsp;
| align="center" style="border-right: 2px solid #BCB; border-bottom: 2px solid #BCB;" | [[File:DE9IM IB.svg|100px]]

&nbsp; <math>\dim[I(a){\color{red}\cap}B(b)] = 1</math> &nbsp;
| align="center" style="border-bottom: 2px solid #BCB;" | [[File:DE9IM IE.svg|100px]]

&nbsp; <math>\dim[I(a){\color{red}\cap}E(b)] = 2</math> &nbsp;
|-
| align="center" | <span class="bold">'''Boundary'''</span>
| align="center" style="border-right: 2px solid #BCB; border-bottom: 2px solid #BCB;" | <div class="informalfigure"><div>[[File:DE9IM BI.svg|100px]]</div></div>

&nbsp; <math>\dim[B(a){\color{red}\cap}I(b)] = 1</math> &nbsp;
| align="center" style="border-right: 2px solid #BCB; border-bottom: 2px solid #BCB;" | <div class="informalfigure"><div>[[File:DE9IM BB.svg|100px]]</div></div>

&nbsp; <math>\dim[B(a){\color{red}\cap}B(b)] = 0</math> &nbsp;
| align="center" style="border-bottom: 2px solid #BCB;"| <div class="informalfigure"><div>[[File:DE9IM BE.svg|100px]]</div></div>

&nbsp; <math>\dim[B(a){\color{red}\cap}E(b)] = 1</math> &nbsp;
|-
| align="center" | <span class="bold">'''Exterior'''</span>
| align="center" style="border-right: 2px solid #BCB;"| <div class="informalfigure"><div>[[File:DE9IM EI.svg|100px]]</div></div>

&nbsp; <math>\dim[E(a){\color{red}\cap}I(b)] = 2</math> &nbsp;
| align="center" style="border-right: 2px solid #BCB;"| <div class="informalfigure"><div>[[File:DE9IM EB.svg|100px]]</div></div>

&nbsp; <math>\dim[E(a){\color{red}\cap}B(b)] = 1</math> &nbsp;
| align="center" | <div class="informalfigure"><div>[[File:DE9IM EE.svg|100px]]</div></div>

&nbsp; <math>\dim[E(a){\color{red}\cap}E(b)] = 2</math> &nbsp;
|}
|}

This matrix can be [[Serialization|serialized]]. Reading from left-to-right and top-to-bottom, the result is {{tmath|1=II=2,\,IB=1,\,IE=2,\,BI=1,\,BB=0,\,BE=1,\,EI=2,\,EB=1,\,EE=2}}.&nbsp; So, in a  compact representation as string code is '{{mono|'''212101212'''}}'.

== Spatial predicates ==

Any [[topological property]] based on a DE-9IM [[Binary relation|binary]] [[spatial relation]] is a '''spatial predicate'''.  For ease of use "named spatial predicates" have been defined for some common relations, which later became standard predicates.
The ''spatial predicate [[Subroutine|functions]]'' that can be derived from DE-9IM include:<ref name="sdh1990"/>
<ref>{{citation |url=http://www.vividsolutions.com/jts/javadoc/com/vividsolutions/jts/geom/IntersectionMatrix.html |title=JTS: Class IntersectionMatrix |publisher=Vivid Solutions, Inc. |url-status=dead |archive-url=https://web.archive.org/web/20110321145301/http://www.vividsolutions.com/jts/javadoc/com/vividsolutions/jts/geom/IntersectionMatrix.html |archive-date=2011-03-21 }}</ref>

:Predicates defined with masks of domain {{mset|1={{mono|T}},{{mono|F}},{{mono|*}} }}:

{| class="wikitable"
|-
! style="width:8em" | Name (synonym)
!colspan="4"| Intersection matrix and mask code string<br>([[Boolean algebra#Basic operations|boolean OR]] between matrices)
!Meaning and definition<ref name="sdh1990"/>
!Equivalent
|-
!rowspan="2"| Equals
|colspan="4"| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{F}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|{{NumBlk|:|{{math|''II'' ∧ ~''IE'' ∧ ~''BE'' ∧ ~''EI'' ∧ ~''EB''}}|{{EquationRef|5}}}}''a'' and ''b'' are topologically [[Equality (relational operator)|equal]]. "Two geometries are topologically equal if their interiors intersect and no part of the interior or boundary of one geometry intersects the exterior of the other".<ref>JTS Technical Specifications of 2003.</ref>
|rowspan="2"|''Within'' & ''Contains''
|-
| <code>T*F**FFF*</code>
|
|
|
|-
!rowspan="2"| Disjoint
|colspan="4"| <math>\Bigl[\begin{smallmatrix}
\mathrm{F}&\mathrm{F}&\mathrm{*}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|{{NumBlk|:|{{math|''~II'' ∧ ~''IB'' ∧ ~''BI'' ∧ ~''BB''}}|{{EquationRef|6}}}}''a'' and ''b'' are [[Disjoint sets|disjoint]]: they have no point in common. They form a set of  [[Disconnected (topology)#Disconnected spaces|disconnected]] geometries.
|rowspan="2"|''not Intersects''
|-
| <code>FF*FF****</code>
|
|
|
|-
!rowspan="2"| Touches<br>(meets)
| <math>\Bigl[\begin{smallmatrix}
\mathrm{F}&\mathrm{T}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{F}&\mathrm{*}&\mathrm{*}\\
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|colspan="2"| <math>\Bigl[\begin{smallmatrix}
\mathrm{F}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{T}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|{{NumBlk|:|{{math|''~II'' ∧ (''IB'' ∨ ''BI'' ∨ ''BB'')}}|{{EquationRef|7}}}}''a'' touches ''b'': they have at least one point in common, but their interiors do not intersect.
|rowspan="2"|
|-
| <code>FT*******</code>
| <code>F**T*****</code>
|colspan="2"| <code>F***T****</code>
|-
!rowspan="2"| Contains
|colspan="4"| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|{{NumBlk|:|{{math|''II'' ∧ ~''EI'' ∧ ~''EB''}}|{{EquationRef|8}}}}''a'' contains ''b'': geometry ''b'' lies in ''a'', and the interiors intersect. Another definition: "''a'' contains ''b'' [[if and only if|iff]] no points of ''b''  lie in the exterior of ''a'', and at least one point of the interior of ''b'' lies in the interior of ''a''".<ref name="davis2007">M. Davis (2007), "[http://lin-ear-th-inking.blogspot.com.br/2007/06/subtleties-of-ogc-covers-spatial.html Quirks of the 'Contains' Spatial Predicate]".</ref>
|rowspan="2"|''Within''(''b'',''a'')
|-
|colspan="4"| <code>T*****FF*</code>
|-
!rowspan="2"| Covers
| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{T}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{T}&\mathrm{*}\\
\mathrm{F}&\mathrm{F}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|{{NumBlk|:|{{math|(''II'' ∨ ''IB'' ∨ ''BI'' ∨ ''BB'') ∧ ~''EI'' ∧ ~''EB''}}|{{EquationRef|9}}}}''a'' covers ''b'': geometry ''b'' lies in ''a''. Other definitions: "At least one point of ''b'' lies in ''a'', and no point of ''b'' lies in the exterior of ''a''", or "Every point of ''b'' is a point of (the interior or boundary of) ''a''".
|rowspan="2"|''CoveredBy''(''b'',''a'')
|-
| <code>T*****FF*</code>
| <code>*T****FF*</code>
| <code>***T**FF*</code>
| <code>****T*FF*</code>
|}

:Predicates that can be obtained from the above by [[Negation#Definition|logical negation]] or parameter inversion ([[transposed matrix|matrix transposition]]), as indicated by the last column:

{| class="wikitable"
|-
!rowspan="2" style="width:8em" | Intersects
| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{T}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{T}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|''a'' [[Intersection (set theory)|intersects]] ''b'': geometries ''a'' and ''b'' have at least one point in common.
|rowspan="2"|''not Disjoint''
|-
| <code>T********</code>
| <code>*T*******</code>
| <code>***T*****</code>
| <code>****T****</code>
|-
!rowspan="2"| Within <br>(inside)
|colspan="4"| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|''a'' is within ''b'': ''a'' lies in the interior of ''b''.
|rowspan="2"|''Contains''(''b'',''a'')
|-
|colspan="4"| <code>T*F**F***</code>
|-
!rowspan="2"| CoveredBy
| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{T}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{*}&\mathrm{F}\\
\mathrm{T}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{*}&\mathrm{*}&\mathrm{F}\\
\mathrm{*}&\mathrm{T}&\mathrm{F}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2"|''a'' is covered by ''b'' (extends ''Within''): geometry ''a'' lies in ''b''. Other definitions: "At least one point of ''a'' lies in ''b'', and no point of ''a'' lies in the exterior of ''b''", or "Every point of ''a'' is a point of (the interior or boundary of) ''b''".
|rowspan="2"|''Covers''(''b'',''a'')
|-
| <code>T*F**F***</code>
| <code>*TF**F***</code>
| <code>**FT*F***</code>
| <code>**F*TF***</code>
|}

:Predicates that utilize the input dimensions, and are defined with masks of domain {{mset|1={{mono|0}},{{mono|1}},{{mono|T}},{{mono|*}} }}:

{| class="wikitable"
|-
!rowspan="2" style="width:8em" | '''Crosses'''<span style="font-weight:normal"><br>{{tmath|1=\dim(a)\ne\dim(b)}} or <br>{{math|1=dim(any) = 1}}</span>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{T}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{T}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|colspan="2"| <math>\Bigl[\begin{smallmatrix}
\mathrm{0}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2" colspan="2"|''a'' crosses ''b'': they have some but not all interior points in common, and the dimension of the intersection is less than that of at least one of them. The following mask selection rules must '''only''' be checked when {{tmath|\dim(a)\ne\dim(b)}} (except for line / line inputs, which ''are'' allowed), otherwise the predicate is '''false''':<ref name="ST_Crosses">[http://postgis.org/docs/ST_Crosses.html ST_Crosses]</ref>
{{NumBlk|:|{{math|(''II''{{=}}0)}} for lines, &nbsp; {{math|(''II'' ∧ ''IE'')}} when {{tmath|\dim(a)<\dim(b)}}, &nbsp;  {{math|(''II'' ∧ ''EI'')}} when {{tmath|\dim(a)>\dim(b)}}|{{EquationRef|10}}}}
|-
| <code>T*T******</code> <small><br>{{tmath|\dim(a)<\dim(b)}}</small>
| <code>T*****T**</code> <small><br>{{tmath|\dim(a)>\dim(b)}}</small>
|colspan="2"| <code>0********</code> <small><br>{{math|1=dim(any) = 1}}</small>
|-
!rowspan="2"| Overlaps<span style="font-weight:normal"><br>{{tmath|1=\dim(a)=\dim(b)}}</span>
| <math>\Bigl[\begin{smallmatrix}
\mathrm{T}&\mathrm{*}&\mathrm{T}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{T}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|colspan="3"| <math>\Bigl[\begin{smallmatrix}
\mathrm{1}&\mathrm{*}&\mathrm{T}\\
\mathrm{*}&\mathrm{*}&\mathrm{*}\\
\mathrm{T}&\mathrm{*}&\mathrm{*}
\end{smallmatrix}\Bigr]</math>
|rowspan="2" colspan="2"|''a'' overlaps ''b'': they have some but not all points in common, they have the same dimension, and the intersection of the interiors of the two geometries has the same dimension as the geometries themselves. The following mask selection rules must '''only''' be checked when {{tmath|1=\dim(a)=\dim(b)}}, otherwise the predicate is '''false''':
{{NumBlk|:|{{math|(''II'' ∧ ''IE'' ∧ ''EI'')}} for points or surfaces, &nbsp; {{math|(''II''{{=}}1 ∧ ''IE'' ∧ ''EI'')}} for lines|{{EquationRef|11}}}}
|-
| <code>T*T***T**</code> <small><br>{{math|1=dim = 0 or 2}}</small>
| colspan="2" | <code>1*T***T**</code> <small><br>{{math|1=dim = 1}}</small>
|}

Notice that:

* The ''topologically equal'' definition does not imply that they have the same points or even that they are of the same class.

* The output of {{tmath|\operatorname{DE-9IM}(a,b)}} have the information contained in a list of all interpretable predicates about geometries ''a'' and ''b''.

* All predicates are computed by masks. Only ''Crosses'' and ''Overlaps'' have additional conditions about {{tmath|\dim(a)}} and {{tmath|\dim(b)}}.

* All mask string codes end with <code>*</code>.  This is because ''EE'' is trivially true, and thus provides no useful information.

* The ''Equals'' mask, <code>T*F**FFF*</code>, is the "merge" of ''Contains'' (<code>T*****FF*</code>) and ''Within'' (<code>T*F**F***</code>): {{math|(''II'' ∧ ~''EI'' ∧ ~''EB'') ∧ (''II'' ∧ ~''IE'' ∧ ~''BE'')}}.

* The mask <code>T*****FF*</code> occurs in the definition of both ''Contains'' and ''Covers''.  ''Covers'' is a more inclusive relation. In particular, unlike ''Contains'' it does not distinguish between points in the boundary and in the interior of geometries. For most situations, ''Covers'' should be used in preference to ''Contains''.

* Similarly, the mask <code>T*F**F***</code> occurs in the definition of both ''Within'' and ''CoveredBy''.  For most situations, ''CoveredBy'' should be used in preference to ''Within''.

* Historically, other terms and other formal approaches have been used to express ''spatial predicates''; for example [[region connection calculus]] was introduced in 1992 by<ref>{{cite conference|ref=randell92|author1=Randell, D.A.|author2=Cui, Z|author3=Cohn, A.G.|title=A spatial logic based on regions and connection|book-title=3rd Int. Conf. on Knowledge Representation and Reasoning|publisher=Morgan Kaufmann|date=1992|pages=165–176}}</ref> Randell, Cohn and Cohn.

=== Properties ===
The spatial predicates have the following properties of [[Binary relation|binary relations]]:

* [[Reflexive_relation|Reflexive]]: Equals, Contains, Covers, CoveredBy, Intersects, Within 
* [[Reflexive_relation|Anti-reflexive]]: Disjoint
* [[Symmetric_relation|Symmetric]]: Equals, Intersects, Crosses, Touches, Overlaps
* [[Transitive_relation|Transitive]]: Equals, Contains, Covers, CoveredBy, Within
 
=== Interpretation ===
[[File:TopologicSpatialRelarions2.png|thumb|400px|Examples of spatial relations.]]
The choice of terminology and semantics for the spatial predicates is based on reasonable conventions and the tradition of topological studies.<ref name="sdh1990"/>
Relationships such as ''Intersects'', ''Disjoint'', ''Touches'', ''Within'', ''Equals''  (between two geometries ''a'' and ''b'')  have an obvious semantic:<ref name="davis2007"/><ref name="cafrca">{{cite journal | first1 = G. | last1 = Câmara | first2 = U. M. | last2 = Freitas | first3 = M. A. | last3 = Casanova | year = 1995 | title = Fields and Objects Algebras for GIS Operations | citeseerx = 10.1.1.17.991 }}</ref>
; ''Equals'':   ''a'' = ''b''  that is  (''a'' ∩ ''b'' = ''a'') ∧ (''a'' ∩ ''b'' = ''b'')
; ''Within'':   ''a'' ∩ ''b'' = ''a''
; ''Intersects'':   ''a'' ∩ ''b'' ≠ ∅
; ''Touches'': (''a'' ∩ ''b'' ≠ ∅) ∧ (''a''<sup>ο</sup> ∩ ''b''<sup>ο</sup> = ∅)

The predicates ''Contains'' and ''Within''  have subtle aspects to their definition which are contrary to intuition.
For example,<ref name="davis2007"/>  a line ''L'' which is completely contained in the boundary of a polygon ''P'' is ''not'' considered to be contained in ''P''.   This quirk can be expressed as "Polygons do not contain their boundary". This issue is caused by the final clause of the ''Contains'' definition above: "at least one point of the interior of B lies in the interior of A".  For this case, the predicate ''Covers''  has more intuitive semantics (see definition), avoiding boundary considerations.

For better understanding, the dimensionality of inputs can be used as justification for a gradual introduction of semantic complexity:
:{|class="wikitable"
|-
!Relations between
!Appropriate predicates
!Semantic added
|-
|point/point
|''Equals'', ''Disjoint''
|Other valid predicates collapses into ''Equals''.
|-
|point/line
|adds ''Intersects''
|''Intersects'' is a refinement of ''Equals'': "some equal point at the line".
|-
|line/line
|width="180"|adds ''Touches'', ''Crosses'', ...
|''Touches'' is a refinement of ''Intersects'', about "boundaries" only. ''Crosses'' is about "only one point".
|}

=== Coverage on possible matrix results ===
The number of possible results in a boolean ''9IM'' matrix is 2<sup>9</sup>=512, and in a DE-9IM matrix is 3<sup>9</sup>=6561. The percentage of these results that satisfy a specific predicate is determined as following,
{{aligned table|class=wikitable|cols=2|row1header=y|col1style=text-align:right;
|Probability|Name
| 93.7% |''Intersects''
| 43.8% |''Touches''
| 25% |''Crosses'' (for valid inputs, 0% otherwise)
| 23.4% |''Covers'' and ''CoveredBy''
| 12.5% |''Contains'', ''Overlaps'' (for valid inputs, 0% otherwise) and ''Within''
| 6.3%   |''Disjoint''
| 3.1%   |''Equals''
}}
On usual applications the geometries intersects ''a priori'', and the other relations are checked.

The composite predicates "''Intersects'' OR ''Disjoint''" and "''Equals'' OR ''Different''"  have the sum 100% (always true predicates),
but "''Covers'' OR ''CoveredBy''" have 41%, that is not the sum, because they are neither logical complements or independent relations; similarly "''Contains'' OR ''Within''", have 21%. The sum 25 % + 12.5 % = 37.5 % is obtained when ignoring overlapping lines in "''Crosses''  OR ''Overlaps''", because the valid input sets are disjoint.

== Queries and assertions ==
The ''DE-9IM'' offers a full descriptive assertion about the two input geometries. It is a mathematical function that represents a [[Functional completeness|complete set]] of all possible relations about two entities, like a [[Truth table]], the [[Three-way comparison]], a [[Karnaugh map#2-variable map examples|Karnaugh map]] or a [[Venn diagram]]. Each output value is like a truth table line, that represent relations of specific inputs.

As illustrated above, the output '212101212' resulted from ''DE-9IM''(''a'',''b'') is a complete description of all topologic relations between specific geometries ''a'' and ''b''. It says to us that {{tmath|1=II=2,\,IB=1,\,IE=2,\,BI=1,\,BB=0,\,BE=1,\,EI=2,\,EB=1,\,EE=2}}.

By other hand, if we check predicates like ''Intersects''(''a'',''b'') or  ''Touches''(''a'',''b'') — for the same example we have "''Intersects''={{mono|true}} and ''Touches''={{mono|true}}" — it is an incomplete description of "all topologic relations".
Predicates also do not say any thing about the dimensionality of the geometries (it doesn't matter if ''a'' and ''b'' are lines, areas or points).

This independence of geometry-type and the lack of [[Completeness (logic)|completeness]], on ''predicates'', are useful for [[Query language|general queries]] about two geometries:
:{|border="0" class="wikitable"
|
!interior/boundary/exterior semantic
!usual semantic
|-
!Assertions
|style="background-color:#DDC" align="center"|'''more descriptive'''<br>  " ''a'' and ''b'' have {{math|1=DE-9IM(''a'',''b'')='212101212'}} "
|style="background-color:#DDC" align="center"|'''less descriptive'''<br> " ''a Touches b'' "
|-
!Queries
|style="background-color:#DDC" align="center"|'''more restrictive'''<br>" Show all pair of geometries where {{math|1=DE-9IM(''a'',''b'')='212101212'}} "
|style="background-color:#DDC" align="center"|'''more general'''<br>" Show all pair of geometries where ''Touches''(''a'',''b'') "
|}

For usual applications, the use of ''spatial predicates'' also is justified by being more [[Human-readable medium|human-readable]] than ''DE-9IM'' descriptions: a typical user  have better intuition about predicates (than a set of interiors/border/exterior intersections).

Predicates have useful [[Semantics (computer science)|semantic]] into usual applications, so it is useful the translation of a ''DE-9IM'' description into a list of all associated predicates,<ref>A [https://github.com/ppKrauss/postgis-st-relate-summary ''DE-9IM'' translator], of all associated predicates of a spatial relation.</ref><ref name="SDO_RELATE">Note. The [http://docs.oracle.com/cd/B19306_01/appdev.102/b14255/sdo_operat.htm#i78531 Oracle's spatial funcion {{mono|SDO_RELATE()}}] {{Webarchive|url=https://web.archive.org/web/20130721054305/http://docs.oracle.com/cd/B19306_01/appdev.102/b14255/sdo_operat.htm#i78531 |date=2013-07-21 }} do only a partial translation, internally, offering to user a mask for a or-list of predicates to be checked, instead the DE-9IM string.</ref> that is like a [[Type conversion|casting process]] between the two different semantic types. Examples:

* The string codes "{{mono|0F1F00102}}" and "{{mono|0F1FF0102}}" have the semantic of "''Intersects & Crosses & Overlaps''".
* The string code "{{mono|1FFF0FFF2}}" have the semantic of "''Equals''".
* The string codes "{{mono|F01FF0102}}",  "{{mono|FF10F0102}}", "{{mono|FF1F00102}}", "{{mono|F01FFF102}}",  and "{{mono|FF1F0F1F2}}" have the semantic of "''Intersects & Touches''".

=== Standards ===
The [[Open Geospatial Consortium]]  (OGC) has standardized the typical spatial predicates (Contains, Crosses, Intersects, Touches, etc.) as boolean functions, and the DE-9IM model,<ref name="ogs1">"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option", [[Open Geospatial Consortium|OGC]], http://www.opengeospatial.org/standards/sfs</ref> as a function that returns a string (the DE-9IM code), with domain of {{mset|1={{mono|0}},{{mono|1}},{{mono|2}},{{mono|F}} }},  meaning {{mono|0}}=point, {{mono|1}}=line, {{mono|2}}=area, and {{mono|F}}="empty set". This DE-9IM string code is a standardized format for data interchange.

The [[Simple Feature Access]] (ISO 19125) standard,<ref name="SFS2007">
[[Open Geospatial Consortium|Open Geospatial Consortium Inc.]] (2007), "OpenGIS® Implementation Standard for Geographic
information - Simple feature access - Part 2: SQL option", [http://www.opengeospatial.org/standards/sfs OGC document] ''06-104r4'' version 1.2.1 (review of 2010-08-04).</ref> in the chapter 7.2.8, "SQL routines on type Geometry", recommends as supported routines the ''SQL/MM Spatial''<ref>ISO 13249-3 Part 3: Spatial, summarized in  [http://www.sigmod.org/record/issues/0112/standards.pdf SQL Multimedia and Application Packages (SQL/MM)] {{Webarchive|url=https://web.archive.org/web/20100214215605/http://www.sigmod.org/record/issues/0112/standards.pdf |date=2010-02-14 }}.</ref> (ISO 13249-3 Part 3: Spatial)  ''ST_Dimension'', ''ST_GeometryType'', ''ST_IsEmpty'', ''ST_IsSimple'', ''ST_Boundary'' for all Geometry Types.
The same standard, consistent with the definitions of relations in "Part 1, Clause 6.1.2.3"
of the SQL/MM, recommends (shall be supported) the function labels: ''ST_Equals'', ''ST_Disjoint'', ''ST_Intersects'', ''ST_Touches'', ''ST_Crosses'', ''ST_Within'', ''ST_Contains'', ''ST_Overlaps'' and ''ST_Relate''.

The DE-9IM in the OGC standards use the following definitions of Interior and Boundary, for the main OGC standard geometry types:<ref>"Encyclopedia of GIS", edited by Shashi Shekhar and Hui Xiong. SpringerScience 2008. pg. 242</ref>
{|class="wikitable" align="center"
!Subtypes
!Dim
!Interior ({{mvar|I}})
!boundary ({{mvar|B}})
|-
|Point, MultiPoint
|0
|Point, Points
|Empty
|-
|LineString, Line
|1
|Points that are left when the boundary points are removed.
|Two end points.
|-
|LinearRing
|1
|All points along the geometry.
|Empty.
|-
|MultilineString
|1
|Points that are left when the boundary points are removed.
|Those points that are in the boundaries of an odd number of its elements (curves).
|-
|Polygon
|2
|Points within the rings.
|Set of rings.
|-
|MultiPolygon
|2
|Points within the rings.
|Set of rings of its elements (polygons).
|-
|colspan="4"|NOTICE: '''exterior points (E)''' are points ''p'' not in the ''interior'' or ''boundary'', so not need extra interpretation,  {{mono|E(p){{=}}not(I(p) or B(p))}}.
|}

=== Implementation and practical use ===
Most spatial databases, such as [[PostGIS]], implements the ''DE-9IM()'' model by the standard functions:<ref>
ST_Relate() [[PostGIS]] function  [http://www.postgis.org/docs/ST_Relate.html online documentation].</ref> <code>ST_Relate</code>, <code>ST_Equals</code>, <code>ST_Intersects</code>, etc. The function <code>ST_Relate(a,b)</code> outputs the standard OGC's ''DE-9IM string code''.

Examples: two geometries, ''a'' and ''b'', that intersects and touches with a point (for instance with {{tmath|1=\dim(B(a)\cap I(b))=0}} and {{tmath|1=\dim(I(a)\cap I(b))=F}}), can be <code>ST_Relate(a,b)='FF1F0F1F2'</code> or <code>ST_Relate(a,b)='FF10F0102'</code> or <code>ST_Relate(a,b)='FF1F0F1F2'</code>. It also satisfies <code>ST_Intersects(a,b)=true</code> and <code>ST_Touches(a,b)=true</code>.
When <code>ST_Relate(a,b)='0FFFFF212'</code>, the returned DE-9IM code have the semantic of "Intersects(a,b) & Crosses(a,b) & Within(a,b) & CoveredBy(a,b)", that is, returns <code>true</code> on the boolean expression <code>ST_Intersects(a,b) AND ST_Crosses(a,b) AND ST_Within(a,b) AND  ST_Coveredby(a,b)</code>.

The use of {{mono|ST_Relate()}} is faster than direct computing of a set of correspondent predicates.<ref name="PostGISch4">[http://www.postgis.org/docs/using_postgis_dbmanagement.html#DE-9IM Chapter 4. Using PostGIS: Data Management and Queries]</ref> There are cases where using {{mono|ST_Relate()}} is the only way to compute a complex predicate — see the example of the code <code>0FFFFF0F2</code>,<ref name="test1case4">JTS test case of "point A within one of B points", http://www.vividsolutions.com/jts/tests/Run1Case4.html {{Webarchive|url=https://web.archive.org/web/20160304032952/http://www.vividsolutions.com/jts/tests/Run1Case4.html |date=2016-03-04 }}</ref> of a point that not "crosses" a multipoint (a object that is a set of points), but predicate ''Crosses'' (when defined by a mask) returns ''true''.

It is usual to [[Function overloading|overload]] the {{mono|ST_Relate()}} by adding a mask parameter,
or use a returned {{mono|ST_Relate(a,b)}} string into the {{mono|ST_RelateMatch()}} function.<ref>
ST_RelateMatch() [[PostGIS]] function  [http://www.postgis.org/docs/ST_RelateMatch.html online documentation].</ref>
When using {{mono|ST_Relate(a,b,mask)}}, it returns a boolean. Examples:
* <code>ST_Relate(a,b,'*FF*FF212')</code> returns ''true'' when <code>ST_Relate(a,b)</code> is <code>0FFFFF212</code> or <code>01FFFF212</code>, and returns ''false''  when <code>01FFFF122</code> or <code>0FF1FFFFF</code>.
* <code>ST_RelateMatch('0FFFFF212','*FF*FF212')</code> and <code>ST_RelateMatch('01FFFF212','TTF*FF212')</code> are ''true'',  <code>ST_RelateMatch('01FFFF122','*FF*FF212')</code> is ''false''.

== Synonyms  ==
* "Egenhofer-Matrix" is a synonym for the ''9IM'' 3x3 matrix of boolean domain.<ref name="encygis">"Encyclopedia of GIS", S. Shekhar, H. Xiong. {{ISBN|978-0-387-35975-5}}.</ref>
* "Clementini-Matrix" is a synonym for the [[#Matrix_model|DE-9IM]] 3x3 matrix of {{mset|1={{mono|0}},{{mono|1}},{{mono|2}},{{mono|F}} }} domain.<ref name="encygis"/>
* "Egenhofer operators" and "Clementini operators" are sometimes a reference to matrix elements as ''II'', ''IE'', etc. that can be used in boolean operations. Example: the predicate "''G<sub>1</sub>'' contains ''G<sub>2</sub>''"  can be expressed by "{{math|{{angbr|''G<sub>1</sub>''{{!}} II ∧ ~EI ∧ ~EB {{!}}''G<sub>1</sub>''}}}}", that can be translated to mask syntax, <code>T*****FF*</code>.
* [[#Spatial_predicates|Predicate]]s "meets" is a synonym for ''touches''; "inside" is a synonym for ''within''
* Oracle's<ref name="SDO_RELATE"/> "ANYINTERACT" is  a synonym for ''intersects'' and  "OVERLAPBDYINTERSECT" is  a synonym for ''overlaps''.  Its  "OVERLAPBDYDISJOINT" does not have a corresponding named predicate.
* In [[Region connection calculus]]  operators offer some synonyms for [[#Spatial_predicates|predicate]]s: ''disjoint'' is DC (disconnected), ''touches'' is EC (externally connected), ''equals'' is EQ. Other, like ''Overlaps'' as PO (partially overlapping),  need context analysis or composition.<ref>"Multidimensional Region Connection Calculus" (2017), http://qrg.northwestern.edu/qr2017/papers/QR2017_paper_8.pdf</ref><ref>{{cite book |doi=10.1007/978-3-642-45111-9_32 |chapter=Identification of Relations in Region Connection Calculus: 9-Intersection Reduced to 3 + -Intersection Predicates |title=Advances in Soft Computing and Its Applications |series=Lecture Notes in Computer Science |year=2013 |last1=Sabharwal |first1=Chaman L. |last2=Leopold |first2=Jennifer L. |volume=8266 |pages=362–375 |isbn=978-3-642-45110-2 }}</ref>

== See also ==
{|
|-
|valign="top"|Standards:
* [[Simple feature access]] (ISO 19125)
* [[Open Geospatial Consortium]]
* [[GeoSPARQL]]
|&nbsp; &nbsp; &nbsp;
|valign="top"|Software:
* [[Spatial database]]
* [[Object-based spatial database]]
* [[Free and open-source software|FOSS]]:
** [[JTS Topology Suite]]
** [[GRASS GIS]] 
** [[GDAL]] (library)
** [[PostGIS]]
|&nbsp; &nbsp; &nbsp;
|valign="top"|Related topics:
* [[Geospatial topology]]
* [[Karnaugh map#2-variable map examples|Karnaugh (2-variable) map]]
* [[Relational operator]]
* [[Spatial analysis]]
* '''[[Spatial relation]]'''
* [[Spatial–temporal reasoning]]
|}

== References ==
{{Reflist}}

== External links ==
* [http://docs.geotools.org/latest/userguide/library/jts/dim9.html Point Set Theory and the DE-9IM Matrix]
* [https://web.archive.org/web/20131206005929/http://edndoc.esri.com/arcsde/9.1/general_topics/understand_spatial_relations.htm Illustrated Tutorial for DE-9IM]

[[Category:Matrices]]
[[Category:Geometric topology]]
[[Category:Geographic data and information]]
[[Category:Binary operations]]
[[Category:Geometric intersection]]