Rechercher dans le manuel MySQL

12.16.9.1 Spatial Relation Functions That Use Object Shapes

Table des matières

The OpenGIS specification defines the following functions to test the relationship between two geometry values g1 and g2, using precise object shapes. The return values 1 and 0 indicate true and false, respectively, except for ST_Distance(), which returns distance values.

Functions in this section detect arguments in either Cartesian or geographic spatial reference systems (SRSs), and return results appropriate to the SRS.

Unless otherwise specified, functions in this section handle their arguments as follows:

  • If any argument is NULL or any geometry argument is an empty geometry, the return value is NULL.

  • If any geometry argument is not a syntactically well-formed geometry, an ER_GIS_INVALID_DATA error occurs.

  • If any geometry argument refers to an undefined spatial reference system (SRS), an ER_SRS_NOT_FOUND error occurs.

  • For functions that take multiple geometry arguments, if those arguments do not have the same SRID, an ER_GIS_DIFFERENT_SRIDS error occurs.

  • If any geometry argument is geometrically invalid, either the result is true or false (it is undefined which), or an error occurs.

  • For geographic SRS geometry arguments, if any argument has a longitude or latitude that is out of range, an error occurs:

    Ranges shown are in degrees. If an SRS uses another unit, the range uses the corresponding values in its unit. The exact range limits deviate slightly due to floating-point arithmetic.

  • Otherwise, the return value is non-NULL.

These object-shape functions are available for testing geometry relationships:

  • ST_Contains(g1, g2)

    Returns 1 or 0 to indicate whether g1 completely contains g2. This tests the opposite relationship as ST_Within().

    ST_Contains() handles its arguments as described in the introduction to this section.

  • ST_Crosses(g1, g2)

    Two geometries spatially cross if their spatial relation has the following properties:

    • Unless g1 and and g2 are both of dimension 1: g1 crosses g2 if the interior of g2 has points in common with the interior of g1, but g2 does not cover the entire interior of g1.

    • If both g1 and g2 are of dimension 1: If the lines cross each other in a finite number of points (that is, no common line segments, only single points in common).

    This function returns 1 or 0 to indicate whether g1 spatially crosses g2.

    ST_Crosses() handles its arguments as described in the introduction to this section except that the return value is NULL for these additional conditions:

    • g1 is of dimension 2 (Polygon or MultiPolygon).

    • g2 is of dimension 1 (Point or MultiPoint).

  • ST_Disjoint(g1, g2)

    Returns 1 or 0 to indicate whether g1 is spatially disjoint from (does not intersect) g2.

    ST_Disjoint() handles its arguments as described in the introduction to this section.

  • ST_Distance(g1, g2 [, unit])

    Returns the distance between g1 and g2, measured in the length unit of the spatial reference system (SRS) of the geometry arguments, or in the unit of the optional unit argument if that is specified.

    This function processes geometry collections by returning the shortest distance among all combinations of the components of the two geometry arguments.

    ST_Distance() handles its geometry arguments as described in the introduction to this section, with these exceptions:

    • ST_Distance() detects arguments in a geographic (ellipsoidal) spatial reference system and returns the geodetic distance on the ellipsoid. The only permitted geographic argument types are Point and Point, or Point and MultiPoint (in any argument order). If called with other geometry type argument combinations in a geographic SRS, an ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS error occurs.

    • If any argument is geometrically invalid, either the result is an undefined distance (that is, it can be any number), or an error occurs.

    • If an intermediate or final result produces NaN or a negative number, an ER_GIS_INVALID_DATA error occurs.

    As of MySQL 8.0.14, ST_Distance() permits an optional unit argument that specifies the linear unit for the returned distance value. These rules apply:

    • If a unit is specified but not supported by MySQL, an ER_UNIT_NOT_FOUND error occurs.

    • If a supported linear unit is specified and the SRID is 0, an ER_GEOMETRY_IN_UNKNOWN_LENGTH_UNIT error occurs.

    • If a supported linear unit is specified and the SRID is not 0, the result is in that unit.

    • If a unit is not specified, the result is in the unit of the SRS of the geometries, whether Cartesian or geographic. Currently, all MySQL SRSs are expressed in meters.

    A unit is supported if it is found in the INFORMATION_SCHEMA ST_UNITS_OF_MEASURE table. See Section 25.28, “The INFORMATION_SCHEMA ST_UNITS_OF_MEASURE Table”.

    1. mysql> SET @g1 = Point(1,1);
    2. mysql> SET @g2 = Point(2,2);
    3. mysql> SELECT ST_Distance(@g1, @g2);
    4. +-----------------------+
    5. | ST_Distance(@g1, @g2) |
    6. +-----------------------+
    7. |    1.4142135623730951 |
    8. +-----------------------+
    9.  
    10. mysql> SET @g1 = ST_GeomFromText('POINT(1 1)', 4326);
    11. mysql> SET @g2 = ST_GeomFromText('POINT(2 2)', 4326);
    12. mysql> SELECT ST_Distance(@g1, @g2);
    13. +-----------------------+
    14. | ST_Distance(@g1, @g2) |
    15. +-----------------------+
    16. |     156874.3859490455 |
    17. +-----------------------+
    18. mysql> SELECT ST_Distance(@g1, @g2, 'metre');
    19. +--------------------------------+
    20. | ST_Distance(@g1, @g2, 'metre') |
    21. +--------------------------------+
    22. |              156874.3859490455 |
    23. +--------------------------------+
    24. mysql> SELECT ST_Distance(@g1, @g2, 'foot');
    25. +-------------------------------+
    26. | ST_Distance(@g1, @g2, 'foot') |
    27. +-------------------------------+
    28. |             514679.7439273146 |
    29. +-------------------------------+

    For the special case of distance calculations on a sphere, see the ST_Distance_Sphere() function.

  • ST_Equals(g1, g2)

    Returns 1 or 0 to indicate whether g1 is spatially equal to g2.

    ST_Equals() handles its arguments as described in the introduction to this section, except that it does not return NULL for empty geometry arguments.

    1. mysql> SET @g1 = Point(1,1), @g2 = Point(2,2);
    2. mysql> SELECT ST_Equals(@g1, @g1), ST_Equals(@g1, @g2);
    3. +---------------------+---------------------+
    4. | ST_Equals(@g1, @g1) | ST_Equals(@g1, @g2) |
    5. +---------------------+---------------------+
    6. |                   1 |                   0 |
    7. +---------------------+---------------------+

  • ST_Intersects(g1, g2)

    Returns 1 or 0 to indicate whether g1 spatially intersects g2.

    ST_Intersects() handles its arguments as described in the introduction to this section.

  • ST_Overlaps(g1, g2)

    Two geometries spatially overlap if they intersect and their intersection results in a geometry of the same dimension but not equal to either of the given geometries.

    This function returns 1 or 0 to indicate whether g1 spatially overlaps g2.

    ST_Overlaps() handles its arguments as described in the introduction to this section except that the return value is NULL for the additional condition that the dimensions of the two geometries are not equal.

  • ST_Touches(g1, g2)

    Two geometries spatially touch if their interiors do not intersect, but the boundary of one of the geometries intersects either the boundary or the interior of the other.

    This function returns 1 or 0 to indicate whether g1 spatially touches g2.

    ST_Touches() handles its arguments as described in the introduction to this section except that the return value is NULL for the additional condition that both geometries are of dimension 0 (Point or MultiPoint).

  • ST_Within(g1, g2)

    Returns 1 or 0 to indicate whether g1 is spatially within g2. This tests the opposite relationship as ST_Contains().

    ST_Within() handles its arguments as described in the introduction to this section.


Rechercher dans le manuel MySQL

Traduction non disponible

Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.

Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-spatial-relation-functions-object-shapes.html

L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.

Références

  1. Consulter le document html Langue du document :en Manuel MySQL : https://dev.mysql.com/

Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.

Table des matières Haut