[Tilesathome] or/p island issue

Frederik Ramm frederik at remote.org
Fri Aug 1 15:03:30 BST 2008


Hi,

> No offense to Frederik's work, but I'd rather have it use the XSLT  
> osmarender until or/p is actually feature complete.

Well... "feature complete"... as soon as I provide a feature that is  
not in XSLT, will you then drop XSLT because it's not "feature  
complete" any longer? Who defines "feature completeness"?

I'm not too emotionally attached to t at h using or not using or/p, so  
do whatever is best for you. As regards your area center algorithm,  
it is already implemented and in SVN but there's some die-hard bug  
that I haven't found yet, so there are some cases where it doesn't work.

The decluttering is on my list but I am likely to choose a slightly  
different approach than the XSLT version. Everyone else is, by the  
way, welcome to chip in as well. - I also have a working road-name  
decluttering that avoids double printing of road names on dual  
carriageways which I can deploy anytime. (But what about feature  
completeness then...?)

Bye
Frederik

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







More information about the Tilesathome mailing list