From c0a7ceccd6d12d201eb8b2025ef90291e8af4b81 Mon Sep 17 00:00:00 2001 From: ThomasG77 Date: Sat, 7 Jan 2012 11:41:43 -0800 Subject: [PATCH] Updated Optimize Rendering with PostGIS (markdown) --- OptimizeRenderingWithPostGIS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OptimizeRenderingWithPostGIS.md b/OptimizeRenderingWithPostGIS.md index a161b99..b39cbe3 100644 --- a/OptimizeRenderingWithPostGIS.md +++ b/OptimizeRenderingWithPostGIS.md @@ -155,7 +155,7 @@ SQL to the rescue! Let's have postgresql roll all those choices into 1 simple on from planet_osm_line where highway is not null) as foo ``` -The query is split over multiple lines so it's easy to see what's going on. You can also split your own queries into multiple lines in the stylesheet (Mapnik 0.6.0 > | see #173), if it helps you to understand long queries. +The query is split over multiple lines so it's easy to see what's going on. You can also split your own queries into multiple lines in the stylesheet (Mapnik 0.6.0 > | see [#173](https://github.com/mapnik/mapnik/issues/173)), if it helps you to understand long queries. Now you can replace the two filters with these: