Overpass turbo/Polygon Features

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Overpass turbo/Polygon Features
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština 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î latviešu Lëtzebuergesch lietuvių 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 Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް
Overpass API logo.svg
Overpass API · Language reference · Language guide · Technical terms · Areas · Query examples · Advanced examples · Sparse Editing · Permanent ID · FAQ · more · Web site
Servers status · Versions · Development · Technical design · Installation · XAPI compatibility layer · Public transport sketch lines · Applications · Source code and issues
Overpass turbo · Wizard · Overpass turbo shortcuts · MapCSS stylesheets · Export to GeoJSON · more · Development · Source code and issues · Web site

As OpenStreetMap doesn't have an intrinsic area data type, an heuristic has to be applied to determine whether a way is a Line or a Polygon. For Overpass turbo and osmtogeojson I came up with the following (see here for a machine-readable JSON file of this table):

A way is considered a Polygon if

  1. It forms a closed loop, and
  2. it is not tagged area=no, and
  3. at least one of the following conditions is true:

This is mostly based on the information found in the OSM-wiki (namely the presence and absence of the way/area symbols on the individual key-pages). I used taginfo's wiki database for this task.

Unfortunately, the wiki doesn't include any information about whether or not a tag is categorizing (such as landuse=*) or descriptive (such as name=*). Therefore, this heuristic includes my own understanding and opinion about this. For the same reason, this list is surely quite incomplete! Please inform me about more tags that could imply areas.