[MDEV-3333] LP:1043845 - st_distance() results are incorrect depending on variable order Created: 2012-08-30 Updated: 2015-02-02 Resolved: 2012-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Woods (Inactive) | Assignee: | Alexey Botchkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
|
Using MariaDB 5.3.3 on CentOS 6.0 The st_distance() function returns different results depending on the order of the variables. The results appear to be more accurate when the least complex spatial object is used as the first variable. For instance, st_distance(point, linestring) appears to consistently return accurate results but st_distance(linestring, point) often returns incorrect results depending on the linestring and point data. See below for a specific example. As a workaround we have had success using the least complex spatial object first where point < linestring < polygon (from a complexity standpoint). select st_distance(geomfromtext(' select st_distance(geomfromtext('point(-95.96269500000000000000 36.14181833333330000000)') |
| Comments |
| Comment by Elena Stepanova [ 2012-08-30 ] |
|
Re: st_distance() results are incorrect depending on variable order |
| Comment by Alexey Botchkov [ 2012-08-31 ] |
|
Re: st_distance() results are incorrect depending on variable order |
| Comment by Rasmus Johansson (Inactive) [ 2012-08-31 ] |
|
Launchpad bug id: 1043845 |