Quoting Holyfoot's email:
Related tasks in JIRA are:
Speaking shortly, the MariaDB GIS part is now OpenGIS compliant, and passes all the OpenGIS conformance tests
To get that the next things were done:
Missing functions were added:
The return type is Integer, with a return value of 1 for
TRUE, 0 for FALSE, and –1 for UNKNOWN
corresponding to a function invocation on NULL arguments;
return TRUE if c is a ring, i.e., if c is closed and simple. A
simple Curve does not pass through the same Point more than once.
The return type is POINT, returns a Point guaranteed to lie on the Surface.
arguments: POLYGON or MYLTIPOLYGON.
The return type is Integer, returns the number of interiorRings
Relate(g1 Geometry, g2 Geometry, patternMatrix String)
The return type is Integer, with a return value of 1 for TRUE, 0 for
FALSE, and –1 for UNKNOWN corresponding to a function invocation on NULL arguments;
returns TRUE if the spatial relationship specified by the pattern Matrix holds.
The return is Geometry, returna a geometric object that is the convex hull of g1
The information about the GEOMETRY column's reference system (SRID) is now stored in the
field's metadata. Syntax of the CREATE and ALTER was modified to specify the SRID
for the geometry columns.
With this information some views required by OpenGIS, were added:
These are links to the INFORMATION_SCHEMA.GEOMETRY_COLUMNS and
describes the available feature tables and their Geometry properties.
stores information on each spatial reference system used in the database.
Required stored procedures added:
AddGeometryColumn(FEATURE_TABLE_CATALOG, FEATURE_TABLE_SCHEMA,FEATURE_TABLE_NAME, GEOMETRY_COLUMN_NAME, SRID)
adds new column of spatial type to the specified table
DropGeometryColumn(FEATURE_TABLE_CATALOG, FEATURE_TABLE_SCHEMA,FEATURE_TABLE_NAME, GEOMETRY_COLUMN_NAME)
removes the spatial column from the table.