You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: Ldp [Added to the original trac issue at 4.14pm, Tuesday, 10th November 2009]
Splitting in multiple lines is almost always the right choice for buildings/areas. We cannot detect* that this building is exceptionally long and narrow, and invoke other rendering rules on that basis.
Author: dieterdreist [Added to the original trac issue at 4.38pm, Tuesday, 10th November 2009]
Replying to [comment:1 Ldp]:
Splitting in multiple lines is almost always the right choice for buildings/areas.
IMHO no, because this is ONE building, not several
We cannot detect* that this building is exceptionally long and narrow, and invoke other rendering rules on that basis.
you cannot detect it now, but maybe it would be worth to try to in the future. You don't have to solve this now, and sorry for misclassifying this as bug, it is an enhancement. Please keep this open as it helps to develop better rendering engines in the future.
Reporter: dieterdreist
[Submitted to the original trac issue database at 12.28pm, Tuesday, 10th November 2009]
look here, the "pasetto del borgo" is a very long corridor, but the text is in 2 lines:
http://www.openstreetmap.org/?lat=41.903297&lon=12.461511&zoom=18&layers=B000FTF
it would be better to have it in one line (and probably also repeated or stretched).
The text was updated successfully, but these errors were encountered: