[Tilesathome] or/p is production ready

[Frederik Ramm]

Hi,

   I believe my or/p (Osmarender in Perl) implementation is now
production ready. Here's a comparison of or/p with original Osmarender
output from tiles at home:

http://openstreetmap.gryph.de/slippymap/

It's only the Karlsruhe area (about 25 level-12 tiles and everything
below). I think you'll be hard pressed to spot any differences but if
you do, please tell me about them.

Two things I'm aware of: 

(1) The or/p area center algorithm is still the "old" Osmarender rule that
simply uses the centre of the bounding box,

(2) polygons with holes are handled slightly differently (inner/outer
roles are used exclusively, direction of ways is not a factor any
more).

(1) will probably be fixed sooner or later (I have already implemented
Bobkare's algorithm but it doesn't work yet), and (2) might need some
fine tuning but will probably stay.

If you want to use or/p instead of the XSLT version of Osmarender in
the tiles at home environment, simply setting the config option 

Osmarender=orp

in your tilesAtHome.conf should do the trick (provided you have the
latest tilesGen.pl). You might want to give it a closely watched
dry-run first, or at least do a

cd orp
perl -c orp.pl

to see if you have the necessary perl modules installed. You will
likely need (on Debian): libxml-perl, libxml-xpath-perl,
libxml-writer-perl, and libset-object-perl.

You don't, however, gain a lot currently if you switch to or/p -
execution of or/p is faster and less memory consuming than the XSLT
variant but that gain is completely drowned out by Inkscape's resource
hunger.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"