Output Types

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Output Types
· Afrikaans · Alemannisch · aragonés · asturianu · Aymar aru · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · bamanankan · Bân-lâm-gú · Basa Jawa · Basa Sunda · Baso Minangkabau · bosanski · brezhoneg · català · čeština · corsu · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · kurdî · Latina · latviešu · Lëtzebuergesch · lietuvių · Limburgs · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tagalog · Tiếng Việt · Türkçe · Türkmençe · Vahcuengh · vèneto · walon · Wolof · Yorùbá · Zazaki · isiZulu · српски / srpski · авар · Аҧсшәа · башҡортса · беларуская · български · қазақша · Кыргызча · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · भोजपुरी · मराठी · संस्कृतम् · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · བོད་ཡིག · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 中文(繁體)‎ · 吴语 · 粵語 · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް
Logo. Feature : Output Types
One example for Feature : Output Types
Keys that describe various ways a feature produces something


This page has been created to bring together all the keys that describe various ways a feature produces something. It has the aim of producing a coherent set of features which could be used to create maps showing areas of the world where:

  1. Raw materials or resources are Mined, Grown, Fished or Reheard
  2. These materials processed into other forms such as parts, materials or power.

Raw Material Tags


The produce=* tag aims to show a feature's agricultural output produced though a natural process of growing, breading or fishing. This should be tagged for outputs that are biological like strawberries rather than inanimate outputs like coal. Examples of produce:

  • Oysters
  • Plums
  • Bananas

Currently this tag and crop have very similar meanings and an idea to merge the two might be a good idea. See the issues section for more details.


  • crop=* - see produce desc above.


The resource=* tag page gives a detailed explanation of mineral resources and how to tag them. It is meant to describe none biological outputs like coal or gold rather than biological outputs like corn or salmon.

The page does not imply that the tag means the minerals are being mined, rather a way to tag there existence. Tags such as man_made=mineshaft and landuse=quarry should be combined to verify that the resource is being exhumed.

Processing Tags


The product=* aims to show a human manufactured output or product that a feature produces though a process that involves taking produce or resources and converting them into a product of some kind.

A good example of this may be landuse=farmland feature that has a produce=sugar_cane which is then the processed in a man_made=works feature to produce the product=sugar . (See Sugar on Wikipedia)

NOTE: This goes against products current current proposal (mine as well) that states it should be a non biological output.

In the case where the product is non tangable i.e. service an alternate tag may be better suited.


The term output term is currently used for power generation in the format of generator:output=*. This term has widespread consensus and casts another perspective on how the above tags maybe should be used. e.g. orchard:produce = avocado.


Crop vs Produce

Currently the tag crop=* and produce=* have very similar meanings in that they both refer to the biological output of an area. The term crop currently is only related to an agricultural crop from farmland, meadow, orchard e.t.c. whereas produce refers to output from any biological process. As such any value that belongs to the crop key would also be fit for use as a produce value. However the reverse is not true i.e. you would not have a value such as crop=salmon. Sometimes being more specific can be an advantage but in this case it is not as the tag needs a

The following are pros and cons to preferring the produce tag over the crop tag

  • Pros:
    • Produce is more widely applicable and therefore is more likely to gain traction with users.
    • It implies only two things: 1:An output 2:That the output is biological
  • Cons:
    • It is still more specific than a general output tag.
  • Pros:
  • Cons:
    • To be used in a uniform mannor in relation to other tags will require.
    • The fact that the area is a field, orchard e.t.c. will almost certainly be implied by supporting tags.

Produce/Crops vs Resource

Think about the fact that the resource tag merely states things exist but the produce tag states they exist for a purpose. Perhaps we should use another tag to describe biological resources that just exist and are not necessarily utilised for a purpose. These tags sort of exist already e.g. species names for trees. The {tag|landuse} tag is a good indicator of whether or not a resource is being harvested

Perhaps the resource tag could be adapted as a kind of base layer tagging resources of any kind whether or not they are being utilised. The produce tag could then be a layer above which would specify that the resource (at least biological) was being utilised? (to complex ???)


It is clear this concept has a close tie with the landuse=* tag. Think about this.

Man Made

It is clear this concept has a close tie with the man_made=* tag especially the product tag. Think about this.