<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>how about using this first ?<br><br><a href="http://dev.mysql.com/doc/refman/5.1/en/creating-spatial-indexes.html">
http://dev.mysql.com/doc/refman/5.1/en/creating-spatial-indexes.html</a></blockquote><div><br><br>According to the docs there : "A B-tree index on
spatial values will be useful for exact-value lookups, but not
for range scans." - so using that for lat/lon addressing is likely to be bad.<br><br>If you query for 1 tile at the same resolution as that tile is stored (If you see what I mean) it may give a marginal improvement. This depends on whether you use it just to index the tile location, or the whole node address itself (See the "sidenote" section on
<a href="http://wiki.openstreetmap.org/index.php/QuadTiles">http://wiki.openstreetmap.org/index.php/QuadTiles</a>)<br> </div><br></div>