Hello, Le Thu, 19 Apr 2012 00:39:36 +0200, Étienne Loks <[email protected]> a écrit :
> In concerned SQL queries this patch apply a 0-buffer to malformed ways. > As malformed ways seem pretty uncommon and as this operation is heavy > for performance issue the query is first run without the 0-buffer and > is re-run with it if the query fails. > > With PostGIS 1.5 the failure message is not explicit so we can only > catch the generic psycopg2.InternalError. > --- > ocitysmap2/indexlib/indexer.py | 49 > +++++++++++++++++++++++++++++----------- > 1 file changed, 36 insertions(+), 13 deletions(-) I just started testing this, and here it seems to make the rendering process rely slow on getting public buildings: 2012-04-24 21:08:53,994 - ocitysmap@6189 - INFO - Getting amenities for Bâtiments publics/public_building... 2012-04-24 21:13:17,830 - ocitysmap@6189 - INFO - Getting amenities for Bâtiments publics/police... Is this normal to take 5 minutes just to get the public buildings? I'm rendering Solingen, Germany as a test case (it was throwing a GEOS Intersection error). Thomas -- Thomas Petazzoni http://thomas.enix.org MapOSMatic http://www.maposmatic.org Logiciels Libres à Toulouse http://www.toulibre.org Embedded Linux http://www.free-electrons.com
