Proposed features/Clock

The Feature Page for this approved proposal can be located at Tag:amenity=clock.

Clock
Status:	Approved (active)
Proposed by:	Avatar
Tagging:	amenity=clock
Applies to:	node
Definition:	A public visible clock
Rendered as:	clock icon
Draft start:	2009-01-21
RFC start:	2009-01-21
Vote start:	2009-02-08
Vote end:	2009-02-22

Contents 1 Reason 2 Proposed tags 2.1 Keys 2.2 Values 2.2.1 Support 2.2.2 Display 2.2.3 Visibility 2.2.4 Additional data 3 Icon 4 Examples 4.1 Example #1 4.2 Example #2 4.3 Example #3 5 Rendering 6 See also 7 Voting

Reason

Public visible clocks are useful for navigation (and for checking the time of day). Last year I visited San Francisco. My mobile phone and my watch broke. Seems there are much less public clocks in SF than in any German city. Finding the next public clock would have been very handy.

Proposed tags

Main tag would be amenity=clock.

Keys

Further useful keys include:

• support=* How is the clock supported/anchored?
• display=* How is the time displayed?
• visibility=* From which distance can you read the clock?
• date=* Does the clock also show the current date?
• thermometer=* Does the clock also display the (current) temperature?
• barometer=* Does the clock also display the (current) barometric pressure?
• hygrometer=* Does the clock also display the (current) humidity?

Values

Support

• support=pole The clock is mounted on a pole. See example #1.
• support=wall_mounted The clock is mounted to a wall. See example #2.
• support=billboard The clock is part of a billboard. See example #3.
• support=ground The clock is on the ground. (e.g. some sundials)

Display

• display=analog The time/data is displayed by hands on a dial.
• display=digital The time/data is displayed digitally.
• display=sundial The clock is a sundial.
• display=unorthodox The time is displayed in an unorthodox manner (binary, water, reverse direction).

Visibility

• visibility=house Clock is readable from up to 5m (e.g. a small wall mounted clock)
• visibility=street Clock is readable from up to 20m (e.g. a medium size billboard clock)
• visibility=area Clock is readable from more than 20m (e.g. church clock)

Additional data

• date=yes The clock also shows the current date. Default value: no.
• thermometer=yes The clock also displays the (current) temperature. Default value: no.
• barometer=yes The clock also displays the (current) barometric pressure. Default value: no.
• hygrometer=yes The clock also displays the (current) humidity. Default value: no.

Icon

I created a clock icon which may be appropriate.

Examples

Example #1

amenity=clock support=pole display=analog

Example #1

Example #2

amenity=clock support=wall_mounted display=analog

Example #2

Example #3

amenity=clock support=billboard display=digital thermometer=yes

Example #3

Rendering

amenity=clock in map^edit Clock=* in map^edit

See also

• Proposed features/measurement station

Voting

Type "{{vote|yes/no}} --~~~~" to approve/oppose this proposal and sign with your user name & date.

• I approve this proposal. --HB9DTX 21:58, 19 March 2009 (UTC)
• I approve this proposal. --Avatar 12:27, 8 February 2009 (UTC)
• I approve this proposal. --Nop 12:27, 8 February 2009 (UTC)
• I approve this proposal. --Quelbs 12:31, 8 February 2009 (UTC)
• I approve this proposal. --aquandur 12:41, 8 February 2009 (UTC)
• I approve this proposal. --Torstiko 12:42, 8 February 2009 (UTC)
• I approve this proposal. --nkbre 12:48, 8 February 2009 (UTC)
• I approve this proposal. --deejay1 12:51, 8 February 2009 (UTC)
• I approve this proposal. - but why don't you simply ask next person about the time?! --Markus 13:06, 8 February 2009 (UTC)
• I approve this proposal. --sadam 13:35, 8 February 2009 (UTC)
• I approve this proposal. --Dieterdreist 14:44, 8 February 2009 (UTC)
• I oppose this proposal. Conflicts with amenity=place_of_worship - should rather use clock=yes/no where apropriate, for instance in combination with amenity=place_of_worship or with shop=* or building=* or wherever the clock is located. There should also be a cleanup in additional tags. --Skippern 15:20, 8 February 2009 (UTC)

Acturally Example #1 could be replaces with amenity=signpost + clock=yes --Skippern 21:36, 8 February 2009 (UTC)

• I oppose this proposal. Conflicts with other amenities as main-tag, clock=yes/no seems much more reasonable. --De muur 15:40, 8 February 2009 (UTC)
• I approve this proposal. -- mikh43 16:24, 8 February 2009 (UTC) - I think it is useful - I would add support=tower (even though there is a potential clash with building=tower, clock=yes/no as 'tower' is so widely used for different purposes - even an electricity pylon!). Then I would know how best to tag a clock tower - a tower, usually brick or stone, built especially for a clock - quite common in British towns. A simple addition of clock=yes/no assumes that there is a place_of_worship, building, etc. - but there is sometimes only a pole.
• I approve this proposal. --Kaitu 17:07, 8 February 2009 (UTC)
• I approve this proposal. --Jan Tappenbeck 17:52, 8 February 2009 (UTC)
• I approve this proposal. --AndreR 17:54, 8 February 2009 (UTC)
• I approve this proposal. --Setimike 18:10, 8 February 2009 (UTC) I concur with mikh43, sometimes what you have, is just a clock.
• I oppose this proposal. Conflicts with other amenity - dont use amenity - see above --Josias 18:22, 8 February 2009 (UTC)
• I approve this proposal. ---jha- 18:57, 8 February 2009 (UTC)
• I oppose this proposal. Conflicts with other amenities. Clock=* as addition to these sounds more reasonable. --Stephankn 19:42, 8 February 2009 (UTC)
• I approve this proposal. --Mink 23:12, 8 February 2009 (UTC)
• I approve this proposal. --Lefty1963 07:50, 9 February 2009 (UTC)
• I approve this proposal. With caveats which I attend to address post-vote. While amenity=clock is fine for freestanding clocks, what about clocks that are attributes of other amenities, buildings or whatever? I oppose the display attribute: too far-reaching. To resolve the problem, I intend to redo display as clock={analog,digital,sundial,unorthodox,yes,no,...}, and possibly redo all other clock attributes with a clock: prefix. --achadwick 11:32, 9 February 2009 (UTC)
• I approve this proposal. But restrict the use only for solitary clocks - if a clock is attached to a building oder amenity I would like to see a clock=yes and use of the hopefully renamed clock:* tags --JND 19:07, 9 February 2009 (UTC)
• I approve this proposal. However I also support clock=yes where a clock appears on another amenity (eg amenity=place_of_worship. Frankie Roberto 22:43, 9 February 2009 (UTC)
• I approve this proposal. Though I'd like to see a tag for 'broken' to indicate that a given clock is only useful as a navigation aid --Cohort 22:30, 11 February 2009 (UTC)
• I approve this proposal. --go2sh 12:52, 12 February 2009 (UTC)
• I approve this proposal. --Riechfield 09:11, 19 February 2009 (UTC)
• I approve this proposal. --MikeCollinson 12:00, 25 February 2009 (UTC)
• I approve this proposal. --Willem1 19:29, 1 March 2009 (UTC)
• I oppose this proposal. Conflicts with other amenities. Clock=* as addition to these sounds more reasonable. --PhilippeP 14:34, 29 March 2009 (UTC)
• I oppose this proposal. Conflicts with other amenities. Clock=* as addition to these sounds more reasonable. --Lulu-Ann 10:14, 31 March 2009 (UTC)
• I oppose this proposal. Conflicts with tags like amenity=place_of_worship or man_made=tower etc. etc. --Telegnom 08:17, 22 April 2009 (UTC)
• I approve this proposal. Now we can place not only common clocks, but also notable ones. --Schumi4ever 15:11, 24 May 2009 (UTC)
• I approve this proposal. --rurseekatze 16:08, 2 August 2009 (UTC)