-
Notifications
You must be signed in to change notification settings - Fork 819
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
Adding place=square name rendering #2673
Conversation
The question is how to render squares which are tagged as points? This is a valid tagging according to Wiki (some shapes would be hard to define) and it's about 10% of all the cases. |
place=square currently does not have a language independent definition. It is currently defined as things that are named in a certain way in English, French, German, Italian, Spanish and Russian - which all mean at least slightly different things. The wikipedia article linked to from the wiki has a definition that is incompatible with the name based definition in OSM and practical use of the tag. I think this disqualifies it from being rendered here at the moment. As said before i would be against text only rendering of areas based on way_area for features where there is usually no verifiable extent because that will likely lead to mappers applying a very wide interpretation of the extent of a particular square they consider important. |
I was thinking of square as a missing element of our road system and similar enough to simple pedestrian squares, but maybe moving it to placenames makes more sense technically. I agree with you that definition on wiki should be improved (probably with something like "open space common in urban centres, like cities or towns"). For me however this is not a blocker for rendering this tag - currently parts of the complex squares are tagged with a name. Sometimes it makes sense (main road which changes name on square boundaries), but it's also a common workaround just to render it somehow (disconnected pedestrian areas or even parking aisles). I find it to be worse problem (breaking intuitive rule One feature, one OSM element) than vague square definition. |
In this specific example, it seems to be these are functionally parks (grass+trees+walkable), and there is no reason for the black rendering other than people not wanting a green-colored label on something without "park" in the name. Another way to look at it is that the example is not so much seeking to properly tag any sort of plaza so much as an obvious, roundabout (hah!) fix for issue #1253 on these two roundabouts. I.E. it's just tagging for the renderer either way. I see no reason whatsoever not to define Plac Teatralny as highway=pedestrian area=yes. From the aerial imagery, the area is, as expected, a pedestrian area that happens to be bisected by a road, but to the best of my knowledge (a little limited, admittedly, especially where routing is concerned), there is nothing about that which would be considered improper for semantic or routing reasons as long s there are nodes where the road intersects the edge of the plaza (and now that I think of it, it would make Empire State Plaza look much simpler and nicer than the way I originally did it bu eliminating a lot of unnecessary footpaths). Highway=pedestrian is defined for plazas and squares on both its page and "Map Features". The concern with "all objects on the square" on the place=plaza page seems more clearly related to a reluctance to use relationships than any tagging problems. |
I think you're missing the complexity of this square (I guess you talk about Plac Inwalidów): it consists of two "functional" parks, two one-way roads separated with a grass area, tram area and a road around it (BTW it's not a full circle, so not a roundabout) with footways. |
Only part of a square is pedestrian area (and as you can see it was tagged with a name once) - but there is also similar one (currently not drawn) on the front of the theater. The rest of the square is a parking space and roads, not pedestrian area. |
There's the reluctance to use relations I was talking about! Take "Park" A and "Park" B (you call them "grass areas", I say they clearly function as parks), combine them into a relation and BINGO Plac Invalidow is showing. Everything else is nothing but hair splitting.
A similar argument goes with Plac Teatralny, where you just happen to have drawn a lot of "enlarged sidewalks" as paths in this specific area, and rather inconsistently to boot, I should add. If they were all traced as pedestrian areas (which would render far more accurately the spots with sunken planters at each end of the parking, I should add), it would make a lot of sense to either just connect them all into a single pedestrian area (which would obviate the need to connect to the streets with footpaths. Win-win,) or into a multipolygon with your preferred of highway=pedestrian or highway=footpath that could get an area name. Whether the streets or parking are formally part of Plac Teatralny, again, is irrelevant for the purpose of getting the name on the map (since the name and the exact precise area are not visually connected either way, even when using place=square!), and my way is semantically more accurate (it's not perfect, but a lot of OSM semantics aren't, and it's accurate enough in this case). Another bonus of my suggestions is that routing engines can take you to Plac Teatralny right up (since it's the name of a pedestrian area or group thereof). Otherwise you have to wait and hope they will maybe eventually take place=square into account. If you're really anal, you can still use it on the relationship, but I would never do so for Plac Invalidow, which I don't consider to be a square in the first place, as I pointed out in my initial answer. |
sent from a phone
On 5. Jul 2017, at 10:22, Christoph Hormann ***@***.***> wrote:
place=square currently does not have a language independent definition
as it is about a toponym I think it is correct to be language dependent.
|
sent from a phone
On 5. Jul 2017, at 16:00, Circeus ***@***.***> wrote:
The road are already name tagged, yet somehow you are not happy. Why?
because a square is not a road. Streets and squares together form the open space of settlements, honestly I find it disturbing we even have to discuss this here, I would have expected it is obvious to anyone interested in (urban) geography.
|
Thank you for derailing this with a tiny, irrelevant point that ignores my actual argument. The condescension is a nice touch, too. |
@Circeus: You've made a lot of interesting statements about how to tag squares. But it's hard to keep up since you expand already written entries, so I get lost eventually. More importantly - this is not the right place to do discuss square definition, let's keep on talking on Tagging list where it belongs. Currently relation is not allowed for squares on Wiki, but this tag needs more care anyway, so we can discuss also this point. In this ticket I'd like to not check whether particular example is tagged as it should be, but rather how to achieve rendering both for points and areas tagged with |
What is the status of this proposal? |
Waiting for definition fix. Wiki page should be probably changed to be clear that this is about toponym, not the land features. I'm currently working with easier problems, but plan to take care about wiki. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tagging as request changes, for administrative purposes.
Just a note: discussion in #2816 might lead to some general conclusions about |
7.5k now |
2017-10-30 23:38 GMT+01:00 polarbearing <[email protected]>:
7.5k now
Wiki definition improved.
I don't see a general conclusion about the place tag necessary to start
rending this value. In case there is a general conclusion eventually, this
case could be simply included
+1, please start rendering this, the tag was overdue, is rapidly gaining
attraction even if not rendered, and is not disputed in any way.
|
Now that the definition is fixed, I plan to do it soon. |
I have updated the code to omit parks and the likes, which are sometimes called a "square". |
Hooray! |
Yes, exactly. |
So why exactly did you decide to not render names for points? |
I don't remember the details, but that was certainly not a decision to avoid rendering points. Thanks for spotting it though - would you like to prepare the missing code? |
I have never done something like this before, I would have to try things out first. |
I don't know exactly. My advise is to start with general technical description and setting testing environment first and then play a bit with a code: https://wiki.openstreetmap.org/wiki/Standard_tile_layer Let me know if you need some more help. |
Does points mean place=square on nodes? |
Yes, this is what I understand. |
I tried this https://github.com/d3d9/openstreetmap-carto/commit/339b3b85cc7bd69d6ff57e9e76f6d4e3df15323e, how is it? |
I had no time to look closer, but on the first sight on the code and renderings it seems like a proper solution. Could you make a PR? |
Resolves #2203.
Rendering the same as other
roads_area_text_name
objects.Warsaw, z16 - two squares which are not simple footway or pedestrian areas:
Before
After