From OpenStreetMap Wiki
Jump to: navigation, search


I would add advertising=perimeter. Could be useful in stadiums, racetracks,.... for example: Images --Hedaja 12:34, 24 August 2015

I think it's a good idea --Dlareg (talk) 07:46, 19 August 2016 (UTC)

Adopt Existing Standards and Lexicon

The outdoor advertising industry, the sign manufacturers, urban planning community, and especially the visual pollution watchdogs have already established an extensive number of taxonomies, lexicons, terminology, etc. which describe every aspect of 'Street Graphics' ( of which advertising is only one category, and a fuzzy one at that ). It might seem overkill now, but every other tagging scheme in OSM has evolved in a haphazard manner as people want to add progressively more refinement. A well done hierarchy would allow simple high level task and leave lower levels for those that want the detail. It would also give the data some value to those outside communities because there would be a higher probability there was standard meanings that somewhat matched what the real world uses.

Michael Patrick

interesting. Can you give some examples, or even a (structured?) comprehensive list how you think it should be done? --Dieterdreist (talk) 08:11, 3 May 2017 (UTC)

Use on relation?

The page says that this key could be used on relations. What relation (except multipolygon) it could be used on? Chrabroš (talk) 07:17, 3 May 2017 (UTC)

IMHO, multipolygons would be unlikely. The most probable for surfaces would occur on a small building, which will be simple polygons most of the time. Large buildings are typically not used themselves for advertizing, but only for offices (of an advertizing company, not using this "advertizing=*" tag meant for describing the support, but "office=advertizing").
However a long wall/barrier could be used as support, where a relation (not a multipolygon area) could eventually appear if it becomes segmented and one needs to keep the group of segments for the same single advertizing support.
The most probable use is for a big sculpture-like object, modeled in 3D with some relation (not necessarily a multipolygon used for a single surface).
THe use of relations to collect various advertizing places in some unbound area is undesired. — Verdy_p (talk) 14:23, 25 August 2017 (UTC)

Proposal for "tree" type

While attempting to add an advertising structure today, I came across what is known as a "tree" structure. It's essentially a billboard attached to a large stem that is connected to the pavement / road. The stem is known as a trunk (so advertising:support=trunk is the suggested tagging approach).

Example: (example from Mapillary).

--Dónal (talk) 13:27, 25 August 2017 (UTC)

You can use directly support=trunk which was already used 280 times according to Taginfo. --PanierAvide (talk) 13:40, 25 August 2017 (UTC)
To clarify: Suggestion is to use advertising=billboard and support=trunk for such infrastructure? --Dónal (talk) 15:05, 25 August 2017 (UTC)
Exactly ;-) --PanierAvide (talk) 16:07, 25 August 2017 (UTC)

Which language are you referring to? Or are these called tree in English? The support looks like the well known "pole" to me. --Dieterdreist (talk) 12:18, 1 September 2017 (UTC)
Seeing the support=* examples, I think the distinction is a matter of support width: few centimers = post, ~10/20 centimers = pole, 30+ centimeters = trunk. --PanierAvide (talk) 12:33, 1 September 2017 (UTC)
Those are simply examples. If you search for pictures of "advertising trunk" with a search engine, you won't find anything suitable to confirm this is a combination used in English to describe an advertising support (at least I couldn't find any), on the other hand, searching for "advertising pole" shows lots of square poles and bigger poles that seem to be what you want to tag. Bigger ones are also called "mast". "Trunk" doesn't seem to make sense in English, this is confirmed both, by the image search and by looking in a dictionary: [1] --Dieterdreist (talk) 14:05, 1 September 2017 (UTC)