-
Notifications
You must be signed in to change notification settings - Fork 822
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
Add amenity=clock icon #3135
Add amenity=clock icon #3135
Conversation
We had this idea in the past:
|
Please include in code:
|
Will places tagged with both |
I've checked this combination with Overpass Turbo and Google Earth, most of examples doesn't have any other function than being a clock, so |
e3c3971
to
05ccfe4
Compare
sent from a phone
On 21. Mar 2018, at 21:51, Tomasz Wójcik ***@***.***> wrote:
I've checked this combination with Overpass Turbo and Google Earth, most of examples doesn't have any other function than being a clock, so amenity=clock tag should have a pririty there IMO.
for most commemorative clocks memorial seems fitting better than monument, as the latter should be accessible.
You can’t see in google earth if something has a commemorative function, or maybe you can explain how?
|
@james2432 We mean to render all clocks on zoom 19 (visibility=* doesn't matter) and clocks with visibility=area on zoom 18 |
sent from a phone
On 22. Mar 2018, at 07:21, Tomasz Wójcik ***@***.***> wrote:
You can’t see in google earth if something has a commemorative function, or maybe you can explain how?
street view :)
neither, I’d say it requires local knowledge
|
@Tomasz-W I understand now, will tweak :) 👍 |
05ccfe4
to
84993f8
Compare
It's important to test how does it look with churches/towers and stations - people may tag them on such objects, not only standalone clocks, and this might be making visual noise. |
Aparently they are never tagged with churches/towers: |
I meant "on the wall of the churches/towers", not "the churches/towers which are considered to be clocks" - this wouldn't make sense for me. |
do you have an example of a clock that is near a church? |
No, I don't. |
0537d22
to
d542cb7
Compare
I'm considering which tag should have priority, but in cases which I can imagine at the moment: |
I would exclude at least |
This could lead to dropping this tag to get it rendered.... |
What about |
@Tomasz-W The problem of objects with multiple tags is hard, basically I just rely on current code. Otherwise we should have complicated tools for chopping and moving some queries. @HolgerJeromin Cheating is always possible, but there should be a way for a proper tagging to not make a visual mess in typical cases. |
@james2432 How are your plans about updating this code? |
Proof of exclusion for support = wall and support=wall_mounted https://www.openstreetmap.org/node/5507892508 (node, support=wall_mounted) (z19 ... z20 was also tested) https://www.openstreetmap.org/way/442511850 (way, support=wall) (z19 ... z20 was also tested) https://www.openstreetmap.org/node/4294148104 (node, support=wall) (z19 ... z20 was also tested) Also added the tags-> in parenthesis when using IS |
project.mml
Outdated
@@ -1519,6 +1519,8 @@ Layer: | |||
tags->'tower:type' as "tower:type", | |||
tags->'castle_type' as castle_type, | |||
tags->'information' as information, | |||
tags->'visibility' as "visibility", | |||
tags->'support' as support, |
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.
Why "visibility" is in quotes and support is not?
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.
purly esthetical, will add the quotes to follow others
project.mml
Outdated
@@ -2343,6 +2349,7 @@ Layer: | |||
WHERE building IS NOT NULL | |||
AND building NOT IN ('no') | |||
AND name IS NOT NULL | |||
AND NOT tags->'tower:type' IN('bell_tower') |
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.
Lacking space.
See purely esthetical, the other tags/column names are not enclosed with quotes here. Added space. Is there a coding standard that says all column names must be enclosed in quotes? |
project.mml
Outdated
@@ -2343,6 +2349,7 @@ Layer: | |||
WHERE building IS NOT NULL | |||
AND building NOT IN ('no') | |||
AND name IS NOT NULL | |||
AND NOT tags->'tower:type' IN ('bell_tower') |
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.
Better NOT IN
, as above with building NOT IN ('no')
.
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.
Changed
I might have few days off without the access to the computer, so I will look at it soon after I'm back. |
Sorry, wrong button... |
This code is strange, it has two sections: [feature = 'amenity_clock']["tower:type" != 'bell_tower'][feature != 'advertising_column'][zoom >= 18] [feature = 'amenity_clock']["tower:type" != 'bell_tower'][feature != 'advertising_column']['support' != 'wall']['support' != 'wall_mounted'][zoom >= 19] { Wall clocks should never be shown, because they are just a part of tower (unlike clock towers with multiple faces for example), not the landmarks in themselves. |
@james2432 What's the state of this PR? Are you willing to finish it? |
well my laptop just died completely(motherboard), so I will be unable to continue this until I get a new one. |
Oh, I understand. Anyway, I still hope that someday we will have these clocks and craft objects on map :) |
@kocio-pl, if I want to finish this do I do it by opening a new PR and noting that it closes this one along with the original issue or is there a certain procedure for that? |
New PR with closing comment will be OK. |
you can create a PR on my branch I will merge it, ai'm just unable to create new changes since I dont have a computer to work on it(using phone) |
OK cool. Creating a new PR here instead of on a branch might make it easier to deal with any subsequent issues that could come up. @james2432, all that needs doing on it at this point is fixing rendering on walls? |
@james2432, I copied everything except the wall thing from your commit and although Kosmtik ran, I couldn't get it to display clocks on the map. If there anyway you could go over my code and see what I might be keeping them from displaying? https://github.com/Adamant36/openstreetmap-carto/tree/clock |
@Adamant36 Oh, one more thing. Please change icon to "v1" version as it's obviously more clear than a "v2" https://gist.github.com/Tomasz-W/07ed36017474669db82b11cb7f64dd26 |
I am really, really sorry but I think that showing all clocks is not a good idea (in other words I think that underlying #3070 should be rejected). |
I thought it was a little wierd myself, but it seemed like it had some support at the time. Its generally easy to go back to an issue after some time has passed, or the disscussion has died down, and to close it because it doesn't make sense in retrospect. You might not get any complaints either. Since everyone has pretty much left the building at this point. It still might be worth leaving open due to the earlier support though. I was still planning on working on it eventual if james2434 never came back. What specific issue do you have with it? Maybe some clocks could be displayed instead of all clocks or something. |
Certain clocks are described by tags like e.g. |
@Tomasz-W if you want to open a new issue for the display of prominent ones as @matkoniecz suggests in the original issue I'd be willing to work on it when I get some time if I can. That would at least allow for some discussion of the pros and cons in the meantime though. |
Fixes #3070
See comment below due to rework
From https://www.openstreetmap.org/#map=19/45.01689/-75.64647 (node)Z18:Z19: