tag:blogger.com,1999:blog-5932295847698688808.post7087654663074587330..comments2019-02-01T20:29:29.873-08:00Comments on Gregor The Map Guy: Gregor the Map Guyhttp://www.blogger.com/profile/14880809629054113501noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5932295847698688808.post-59217084540265731862012-07-31T17:01:26.419-07:002012-07-31T17:01:26.419-07:00Very nice! I hadn't seen that new filter.
Thi...Very nice! I hadn't seen that new filter.<br /><br />This new method is significantly simpler, which is great for code maintenance:<br /><br />SELECT * FROM routing_trails WHERE is_road IS NULL ORDER BY the_geom <-> $point LIMIT 1<br /><br />I implemented this at the project being discussed, and in those cases it executes in 2ms instead of 60ms. It's not a huge difference, but it does mean less load on the server, which is always good.Gregor the Map Guyhttps://www.blogger.com/profile/14880809629054113501noreply@blogger.comtag:blogger.com,1999:blog-5932295847698688808.post-52845990022522739792012-07-31T12:42:56.617-07:002012-07-31T12:42:56.617-07:00Nice post,
Have you thought about using the <-&...Nice post,<br />Have you thought about using the <-> operator as part of PostGIS 2.0? This does a sorted list from a GiST index, ala http://blog.opengeo.org/2011/09/28/indexed-nearest-neighbour-search-in-postgis/<br /><br />Best,Anonymousnoreply@blogger.com