Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.4
Description
The MySQL 5.7 ST_AsGeoJSON function has an argument that limits the number of decimals:
https://dev.mysql.com/doc/refman/5.7/en/spatial-geojson-functions.html#function_st-asgeojson
MariaDB accepts an argument but it has no effect:
In MySQL 5.7:
mysql [localhost] {msandbox} ((none)) > SELECT ST_AsGeoJSON(ST_GeomFromText('POINT(5.333 7.222)'),2);
|
+-------------------------------------------------------+
|
| ST_AsGeoJSON(ST_GeomFromText('POINT(5.333 7.222)'),2) |
|
+-------------------------------------------------------+
|
| {"type": "Point", "coordinates": [5.33, 7.22]} |
|
+-------------------------------------------------------+
|
1 row in set (0.00 sec)
|
In MariaDB:
SELECT ST_AsGeoJSON(ST_GeomFromText('POINT(5.333 7.222)'),2);
|
+-------------------------------------------------------+
|
| ST_AsGeoJSON(ST_GeomFromText('POINT(5.333 7.222)'),2) |
|
+-------------------------------------------------------+
|
| {"type": "Point", "coordinates": [5.333, 7.222]} |
|
+-------------------------------------------------------+
|
Attachments
Activity
Ian,
after the fix the decimals are limited with the paramenter.
The 'options' are NOT completely like MySQL - only support the '1' option to add the boundary box.
Can you comment on whether this is supposed to behave like the MySQL version (max_digits and options)? I'd like to document what it should do, even if it's not working at present.