Rechercher dans le manuel MySQL
12.16.12 Spatial Convenience Functions
The functions in this section provide convenience operations on geometry values.
Unless otherwise specified, functions in this section handle their arguments as follows:
If any argument is
NULL
, the return value isNULL
.If any geometry argument is not a syntactically well-formed geometry, an
ER_GIS_INVALID_DATA
error occurs.If any geometry argument has an SRID value that 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.Otherwise, the return value is non-
NULL
.
These convenience functions are available:
ST_Distance_Sphere(
g1
,g2
[,radius
])Returns the mimimum spherical distance between
Point
orMultiPoint
arguments on a sphere, in meters. (For general-purpose distance calculations, see theST_Distance()
function.) The optionalradius
argument should be given in meters.If both geometry parameters are valid Cartesian
Point
orMultiPoint
values in SRID 0, the return value is shortest distance between the two geometries on a sphere with the provided radius. If omitted, the default radius is 6,370,986 meters, Point X and Y coordinates are interpreted as longitude and latitude, respectively, in degrees.If both geometry parameters are valid
Point
orMultiPoint
values in a geographic spatial reference system (SRS), the return value is the shortest distance between the two geometries on a sphere with the provided radius. If omitted, the default radius is equal to the mean radius, defined as (2a+b)/3, where a is the semi-major axis and b is the semi-minor axis of the SRS.ST_Distance_Sphere()
handles its arguments as described in the introduction to this section, with these exceptions:Supported geometry argument combinations are
Point
andPoint
, orPoint
andMultiPoint
(in any argument order). If at least one of the geometries is neitherPoint
norMultiPoint
, and its SRID is 0, anER_NOT_IMPLEMENTED_FOR_CARTESIAN_SRS
error occurs. If at least one of the geometries is neitherPoint
norMultiPoint
, and its SRID refers to a geographic SRS, anER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS
error occurs. If any geometry refers to a projected SRS, anER_NOT_IMPLEMENTED_FOR_PROJECTED_SRS
error occurs.If any argument has a longitude or latitude that is out of range, an error occurs:
If any longitude argument is not in the range (−180, 180], an
ER_LONGITUDE_OUT_OF_RANGE
error occurs.If any latitude argument is not in the range [−90, 90], an
ER_LATITUDE_OUT_OF_RANGE
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.
If the
radius
argument is present but not positive, anER_NONPOSITIVE_RADIUS
error occurs.If the distance exceeds the range of a double-precision number, an
ER_STD_OVERFLOW_ERROR
error occurs.
- +--------------------------------+
- | ST_Distance_Sphere(@pt1, @pt2) |
- +--------------------------------+
- | 20015042.813723423 |
- +--------------------------------+
Returns 1 if the argument is geometrically valid, 0 if the argument is not geometrically valid. Geometry validity is defined by the OGC specification.
The only valid empty geometry is represented in the form of an empty geometry collection value.
ST_IsValid()
returns 1 in this case. MySQL does not support GISEMPTY
values such asPOINT EMPTY
.ST_IsValid()
handles its arguments as described in the introduction to this section, with this exception:If the geometry has a geographic SRS with a longitude or latitude that is out of range, an error occurs:
If any longitude argument is not in the range (−180, 180], an
ER_LONGITUDE_OUT_OF_RANGE
error occurs.If any latitude argument is not in the range [−90, 90], an
ER_LATITUDE_OUT_OF_RANGE
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.
- +------------------+
- | ST_IsValid(@ls1) |
- +------------------+
- | 0 |
- +------------------+
- +------------------+
- | ST_IsValid(@ls2) |
- +------------------+
- | 1 |
- +------------------+
Returns the rectangle that forms the envelope around two points, as a
Point
,LineString
, orPolygon
.Calculations are done using the Cartesian coordinate system rather than on a sphere, spheroid, or on earth.
Given two points
pt1
andpt2
,ST_MakeEnvelope()
creates the result geometry on an abstract plane like this:If
pt1
andpt2
are equal, the result is the pointpt1
.Otherwise, if
(
is a vertical or horizontal line segment, the result is the line segmentpt1
,pt2
)(
.pt1
,pt2
)Otherwise, the result is a polygon using
pt1
andpt2
as diagonal points.
The result geometry has an SRID of 0.
ST_MakeEnvelope()
handles its arguments as described in the introduction to this section, with these exceptions:If the arguments are not
Point
values, anER_WRONG_ARGUMENTS
error occurs.An
ER_GIS_INVALID_DATA
error occurs for the additional condition that any coordinate value of the two points is infinite orNaN
.If any geometry has an SRID value for a geographic spatial reference system (SRS), an
ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS
error occurs.
- +----------------------------------------+
- | ST_AsText(ST_MakeEnvelope(@pt1, @pt2)) |
- +----------------------------------------+
- +----------------------------------------+
Simplifies a geometry using the Douglas-Peucker algorithm and returns a simplified value of the same type.
The geometry may be any geometry type, although the Douglas-Peucker algorithm may not actually process every type. A geometry collection is processed by giving its components one by one to the simplification algorithm, and the returned geometries are put into a geometry collection as result.
The
max_distance
argument is the distance (in units of the input coordinates) of a vertex to other segments to be removed. Vertices within this distance of the simplified linestring are removed.According to Boost.Geometry, geometries might become invalid as a result of the simplification process, and the process might create self-intersections. To check the validity of the result, pass it to
ST_IsValid()
.ST_Simplify()
handles its arguments as described in the introduction to this section, with this exception:If the
max_distance
argument is not positive, or isNaN
, anER_WRONG_ARGUMENTS
error occurs.
- +---------------------------------+
- | ST_AsText(ST_Simplify(@g, 0.5)) |
- +---------------------------------+
- +---------------------------------+
- +---------------------------------+
- | ST_AsText(ST_Simplify(@g, 1.0)) |
- +---------------------------------+
- +---------------------------------+
Validates a geometry according to the OGC specification. A geometry can be syntactically well-formed (WKB value plus SRID) but geometrically invalid. For example, this polygon is geometrically invalid:
POLYGON((0 0, 0 0, 0 0, 0 0, 0 0))
ST_Validate()
returns the geometry if it is syntactically well-formed and is geometrically valid,NULL
if the argument is not syntactically well-formed or is not geometrically valid or isNULL
.ST_Validate()
can be used to filter out invalid geometry data, although at a cost. For applications that require more precise results not tainted by invalid data, this penalty may be worthwhile.If the geometry argument is valid, it is returned as is, except that if an input
Polygon
orMultiPolygon
has clockwise rings, those rings are reversed before checking for validity. If the geometry is valid, the value with the reversed rings is returned.The only valid empty geometry is represented in the form of an empty geometry collection value.
ST_Validate()
returns it directly without further checks in this case.As of MySQL 8.0.13,
ST_Validate()
handles its arguments as described in the introduction to this section, with these exceptions:If the geometry has a geographic SRS with a longitude or latitude that is out of range, an error occurs:
If any longitude argument is not in the range (−180, 180], an
ER_LONGITUDE_OUT_OF_RANGE
error occurs.If any latitude argument is not in the range [−90, 90], an
ER_LATITUDE_OUT_OF_RANGE
error occurs.
Ranges shown are in degrees. The exact range limits deviate slightly due to floating-point arithmetic.
Prior to MySQL 8.0.13,
ST_Validate()
handles its arguments as described in the introduction to this section, with these exceptions:If the geometry is not syntactically well-formed, the return value is
NULL
. AnER_GIS_INVALID_DATA
error does not occur.If the geometry has an SRID value for a geographic spatial reference system (SRS), an
ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS
error occurs.
- +------------------------------+
- | ST_AsText(ST_Validate(@ls1)) |
- +------------------------------+
- +------------------------------+
- +------------------------------+
- | ST_AsText(ST_Validate(@ls2)) |
- +------------------------------+
- +------------------------------+
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-convenience-functions.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
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.