Open Dimitar5555 opened 1 year ago
Thanks for the suggestion.
We have a rejected PR on this already: #147.
The tag in question is used almost exclusively in Russia and Belarus (19600 uses in those two countries, ~1000 in the rest of the world):
https://taginfo.geofabrik.de/russia/tags/place=allotments https://taginfo.geofabrik.de/europe/belarus/tags/place=allotments
Most of these are tagged on polygons (while other populated places are largely mapped with nodes). About 90 percent of the polygons are also tagged landuse=allotments
, of the rest (both polygons and nodes) a large percentage is located within/overlapping landuse=allotments
polygons. Meaning: By nature of their present day de facto use these seem to overwhelmingly be classified as landuse=allotments
.
Based on previous discussion the tag seems to be used in those countries for mapping populated places that have a different history (within the Soviet Union) than other populated places and have today a different official status than other settlements. Elsewhere similar distinctions are either mapped with the standard populated place hierarchy tags (city/town/village/hamlet/isolated_dwelling) but with potentially add-on tags to indicate the different status or with name and other tags on the respective landuse polygons (landuse=allotments
or landuse=residential
) - which we render.
Bottom line: We have a regional particularity in tagging here (not using standard populated place tagging for certain populated places) and a region specific tag being used and documented in a way that only applies to the region in question (by referring to historic origins and present day characteristics regarding official classification which only exist in that region).
Our aim is to support global cohesion in tagging, OpenStreetMap depends on using a globally consistent tagging system. It is fine and highly desirable that local communities develop extensions of tagging to represent regional particularities. And we can and should be proactive in supporting tagging that emerges locally if consistently used. But such extensions should be invented at least with the intention to be in principle usable world wide as far as such features exist. If they are deliberately designed to be region specific and not to be used in other contexts that is something that is difficult for us to support under the goals we have.
In other words: If place=allotments
is clearly delineated from other populated place tags in a way that is applicable world wide and is used widely to map the features in question - like allotment/garden parcel/small scale non commercial agriculture settlements and (seasonal) cottage settlements, or something more narrow in definition - then it would IMO be worth to consider rendering it here. At the moment, however, it seems the reason why the tag is used almost exclusively in the two countries mentioned is not that this kind of settlement does not exist elsewhere (in terms of its practical present day characteristics) but because the tag is explicitly set up to be a region specific tag.
Most of these are tagged on polygons (while other populated places are largely mapped with nodes). About 90 percent of the polygons are also tagged
landuse=allotments
, of the rest (both polygons and nodes) a large percentage is located within/overlappinglanduse=allotments
polygons. Meaning: By nature of their present day de facto use these seem to overwhelmingly be classified aslanduse=allotments
.
Or maybe people are trying to get the names rendered which is why they put names on landuse=allotments
?
Based on previous discussion the tag seems to be used in those countries for mapping populated places that have a different history (within the Soviet Union) than other populated places and have today a different official status than other settlements. Elsewhere similar distinctions are either mapped with the standard populated place hierarchy tags (city/town/village/hamlet/isolated_dwelling) but with potentially add-on tags to indicate the different status or with name and other tags on the respective landuse polygons (
landuse=allotments
orlanduse=residential
) - which we render.
This where the problem lies. You define allotments as populated places or settlements while they are settlement formations (in Bulgaria, other countries may use other terms). They do not have population since people are not allowed to live there year round.
Extract from "Law on the Administrative and Territorial Structure of the Republic of Bulgaria":
Art. 3. (1) Territorial units shall be the settlements and settlement formations. (2) A settlement is a historically and functionally distinct territory defined by the presence of a permanent resident population, construction boundaries or land and construction boundaries and the necessary social and engineering infrastructure. (3) Settlements shall be divided into towns and villages and shall be subject to registration in the Unified Classification of Administrative Territorial and Territorial Units. (4) Settlement formations are territories outside the construction boundaries of settlements, arranged for the fulfilment of specific functions, which are defined by construction boundaries but do not have a permanent resident population. (5) A settlement and a settlement formation shall have a territory, boundaries and a name.
Another extract from "Rules and regulations for the development of separate types of territories and development zones":
Chapter Six. PLANNING OF AREAS FOR RECREATIONAL ACTIVITIES
Art. 27. (1) Areas for recreational activities shall be demarcated as development zones within or outside the boundaries of settlements and settlement formations and shall be defined according to the following varieties:
- resort, designated as Ok;
- holiday village, designated as Os;
- allotments, designated as Ov;
- other recreation (golf resorts, water parks, amusement parks, etc.) designated as Od
Expected behavior
It would be nice if names on
place=alltments
rendered on the map.Actual behavior
Currently they are not being rendered which forces mappers to use incorrect tags (like https://www.openstreetmap.org/node/2214572978).
Screenshots with links illustrating the problem
https://www.openstreetmap.org/node/273816756#map=15/43.8236/22.8997