Alternative to POINT data type is 2 simple float fields, "x" and "y", or "latitude" and "longitude" (an approach that we used in our http://astuce.com.ua/ project). It has its own benefit in search speed.
To speed up the spatial data lookup, a spatial index can be used, but you are forced to switch to MyISAM tables to be able to use it, which is not a case if you love InnoDB's foreign keys...
So a solution is 2 float fields + a separate index on them. This approach allows to easily filter points by a square of a desired size:
> SELECT * > FROM city > WHERE city.lat BETWEEN @x-0.5 AND @x+0.5 > AND city.lng BETWEEN @y-0.5 AND @y+0.5;
© 2013, Oracle Corporation and/or its affiliates
User Comments
set @p = GeomFromText('POINT(11 0)');
select x(@p), y(@p);
Alternative to POINT data type is 2 simple float fields, "x" and "y", or "latitude" and "longitude" (an approach that we used in our http://astuce.com.ua/ project). It has its own benefit in search speed.
To speed up the spatial data lookup, a spatial index can be used, but you are forced to switch to MyISAM tables to be able to use it, which is not a case if you love InnoDB's foreign keys...
So a solution is 2 float fields + a separate index on them. This approach allows to easily filter points by a square of a desired size:
> SELECT *
> FROM city
> WHERE city.lat BETWEEN @x-0.5 AND @x+0.5
> AND city.lng BETWEEN @y-0.5 AND @y+0.5;
That's is much faster.
Add your own comment.