Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

leisure=nature_reserve labelled along boundary as well as at centroid #2070

Closed
DaveF63 opened this issue Mar 5, 2016 · 4 comments
Closed
Assignees

Comments

@DaveF63
Copy link

DaveF63 commented Mar 5, 2016

Hi

Is this intentional:

nature_reserve

I don't remember it occurring previously.

@mrwojo
Copy link
Contributor

mrwojo commented Mar 5, 2016

Warmley Forest Park: http://www.openstreetmap.org/way/38757891

The boundary text was added in 2014, and is shown only when the NR appears large (at least 192,000 pixels, which if square would be about 438x438 px).

Area is not an ideal condition for showing boundary text, but in many cases I've seen it seems to be "good enough". The given example is especially awkward due to the coincidental placement of the text at the tip of a concavity right at the centroid.

Boundary labels on long and/or concave objects can be more readily seen than the centroid label. Consider "Elmer Feldenheimer State Natural Area":
http://www.openstreetmap.org/relation/1438877#map=15/45.9681/-123.9509

See also: #1028

@matkoniecz
Copy link
Contributor

It is useful for really big areas like http://www.openstreetmap.org/#map=17/50.14531/19.67638

selection_001

Rendering at http://www.openstreetmap.org/#map=17/51.46274/-2.46999 is not the best, maybe increasing minimal NR size for it to appear may be a good idea.

@matkoniecz matkoniecz added this to the Bugs and improvements milestone Mar 5, 2016
@kocio-pl kocio-pl self-assigned this Sep 13, 2017
@kocio-pl
Copy link
Collaborator

Any idea what size should be the lower limit for rendering boundary labels?

@kocio-pl
Copy link
Collaborator

I don't see such problems with rendering names of protected areas and this one doesn't look like a serious problem, therefore I close this issue now. It can be reopened if there is more input how should it be solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants