Template:Deprecated features/reason/doc
Jump to navigation
Jump to search
 | This is a documentation subpage for Template:Deprecated features/reason. It contains usage information, categories and other content or metadata that is not part of the original template. |
Usage
This is not to be used directly - it is used in the internals of Template:Deprecated features (more precisely, in Template:Deprecated features/item).
Available languages
Note: if there is an English text in your language's column, then you are welcome to translate it in the template - locate the number in the first column, then go to that number in the switch (in the source code) and add your translation in the inner switch.
If your language is not in the following table, then you are welcome to add translations for all items!
The table below is just a manual preview of the numbers 1 to 100.
| Reason number | EN | FR | ES | RU |
|---|---|---|---|---|
| 1 | Introduction of "shop" | Introduction de "shop" | Introduction of "shop" | Появление ключа "shop" |
| 2 | Introduction of Key:highway | Introduction de la clé highway | Introduction of Key:highway | Появление ключа "highway" |
| 3 | Any type of highway=* (primary, secondary, ...) may have inclined sections tagged separately, this does not create a new type of highway | Tout type de highway=* (primary, secondary, ...) peut avoir des sections en pente - cela ne crée pas de nouveau type de highway. | Any type of highway=* (primary, secondary, ...) may have inclined sections tagged separately, this does not create a new type of highway | Any type of highway=* (primary, secondary, ...) may have inclined sections tagged separately, this does not create a new type of highway |
| 4 | Their "concept" better fits in this new key and highway gets a bit uncluttered. | Le concept de barrière (barrier) est ainsi séparé du concept de voirie (highway), lequel attribut est quelque peu soulagé. | Their "concept" better fits in this new key and highway gets a bit uncluttered. | "Суть" этого значения лучше подходит новому ключу (решено голосованием) |
| 5 | Any highway classification can be unsurfaced. | Tout type de voirie peut n’avoir aucun revêtement. | Any highway classification can be unsurfaced. | Дороги многих классов могут не иметь твёрдого покрытия |
| 6 | No description, usage completely unknown | Usage complètement inconnu... | No description, usage completely unknown | нет описания, точное применение не ясно |
| 7 | better fits into toplevel tags | L’attribut tourisme (tourism) est plus précis que équipement(amenity). | better fits into toplevel tags | Лучшее сочетание с ключом |
| 8 | Was intended to depend on whether the woodland/forest was "managed" or "primaeval", but also see Forest for more discussion about the problems here. | Choisir le premier attribut si la forêt est gérée, le second si elle est purement naturelle. Voir aussi Forest pour les discussions sur les problèmes soulevés. | Was intended to depend on whether the woodland/forest was "managed" or "primaeval", but also see Forest for more discussion about the problems here. | В зависимости от того, ухожен ли лес или дик. |
| 9 | Abandoned feature. | Projet abandonné. | Abandoned feature. | Abandoned feature. |
| 10 | More flexibility; allows us to keep original value of waterway= | Plus flexible (et permet ainsi de recouvrer le type réel du cours d’eau (waterway). | More flexibility; allows us to keep original value of waterway= | Бóльшая гибкость; позволяет сохранить основное значение waterway=*. |
| 11 | An ad is not an amenity... Taken from Category:Tag descriptions with status "deprecated". | Une publicité (advertising) n'est pas un équipement (amenity)... Repris de Category:Tag descriptions with status "deprecated". | An ad is not an amenity... Taken from Category:Tag descriptions with status "deprecated". | An ad is not an amenity... Taken from Category:Tag descriptions with status "deprecated". |
| 12 | This tag has never been approved, nor had wide usage. Take one of the replacements to correctly tag the education place. | Cet attribut n'a ni été approuvé, ni été largement utilisé. Choisissez l'une des suggestions pour renseigner l'établissement éducatif. | This tag has never been approved, nor had wide usage. Take one of the replacements to correctly tag the education place. | This tag has never been approved, nor had wide usage. Take one of the replacements to correctly tag the education place. |
| 13 | More accurate tagging for public rights of way in England and Wales. | Balisage plus précis pour les règles de priorité publiques en Angleterre et au Pays de Galles. | More accurate tagging for public rights of way in England and Wales. | Более точное тегирование общественных дорожных прав в Англии и Уэльсе (англ.). |
| 14 | Cleaning the semantics of the "building" tag; entrance=* approved. building=entrance is still considered coexisting. | L’attribut building=* a désormais une sémantique claire ; tandis que l’attribut entrance=* a lui été approuvé. Attention toutefois, building=entrance reste encore le standard de facto. | Cleaning the semantics of the "building" tag; entrance=* approved. building=entrance is still considered coexisting. | Улучшение схемы тегирования с ключом "building"; удтверждён тег entrance=*. (но аккуратнее, тег building=entrance всё ещё стандарт де-факто) |
| 15 | For tagging islands in lakes and rivers use Relations/Multipolygon, for islands in the sea use natural=coastline and place=island. | Utilisez des relations multipolygone pour les îles dans les lacs, et l’attribut natural=coastline pour les îles en mer. | For tagging islands in lakes and rivers use Relations/Multipolygon, for islands in the sea use natural=coastline and place=island. | Для островов в реках и озёрах стоит применять мультиполигоны, для океанических - natural=coastline. |
| 16 | Tag historic=* should be used for historic items (and therefore not a museum). | L’attribut historic=* devrait être réservé aux éléments historiques — et donc pas les musées. | Tag historic=* should be used for historic items (and therefore not a museum). | Tag historic=* should be used for historic items (and therefore not a museum). |
| 17 | "highway=ford" on a way doesn't allow tagging the highway itself (as e.g. "unclassified"). This doesn't apply to nodes; though, and renderers haven't quite caught up (ref openstreetmap-carto issue 267 and elsewhere) - don't automatically (or semi-automatically) change "ford" node tagging. | highway=ford sur un chemin de voirie ne permet pas de donner le type de voirie comme unclassified, etc. (ceci ne s’applique pas aux nœuds). Mais les outils de rendu n’ont pas encore complètement intégré l’attribut (voir entre autres le problème n° 267 de openstreetmap-carto). Ne changez pas (semi-)automatiquement les attributs ford sur les nœuds. | "highway=ford" on a way doesn't allow tagging the highway itself (as e.g. "unclassified"). This doesn't apply to nodes; though, and renderers haven't quite caught up (ref openstreetmap-carto issue 267 and elsewhere) - don't automatically (or semi-automatically) change "ford" node tagging. | highway=ford" на линии не позволяет описать сам класс дороги (например, "unclassified"). Некоторые рендереры ещё не освоились с новым тегом (см. openstreetmap-carto issue 267) - не меняйте автоматически (или полуавтоматически) старую схему на новую. |
| 18 | Usage of American form color probably mainly due to a bug in JOSM presets. | Probablement arrivé à cause d’une anomalie dans les pré-définitions de FR:JOSM. | Usage of American form color probably mainly due to a bug in JOSM presets. | Usage of American form color probably mainly due to a bug in JOSM presets. |
| 19 | The value "station" is ambiguous and has been used both for substations and power plants / generators ("power station"). Please take the opportunity to review the object and add useful information, not just "correct" it. | L'attribut "station", ambigu, a été employé à la fois pour les transformateurs (substations) et les générateurs (plants). Pour "station" et "substation", prenez l'opportunité de revoir l'objet et d'ajouter d'autres informations, et pas simplement de le "corriger". | The value "station" is ambiguous and has been used both for substations and power plants / generators ("power station"). Please take the opportunity to review the object and add useful information, not just "correct" it. | 'power=station' может быть спутано с "power station" (= электростанцией) и никогда не используется в качестве синонима "подстанции" в британском английском. Please take the opportunity to review the object and add useful information, not just "correct" it. |
| 20 | This is more expressive and more flexible. | Système conditionnel plus expressif et plus flexible. | This is more expressive and more flexible. | схема тегирования условий : более гибка, чем старые ключи day_on/off и hour_on/off. |
| 21 | There is no need for redundant tags. One key is sufficient. | Pas besoin d’attributs redondants ; une seule clé suffit. | There is no need for redundant tags. One key is sufficient. | There is no need for redundant tags. One key is sufficient. |
| 22 | The values wood=coniferous and wood=deciduous are ambiguous. It was approved to use leaf_type=* instead. | Les valeurs deciduous et coniferous sont ambiguës ; l’attribut leaf_type=* a été approuvé. | The values wood=coniferous and wood=deciduous are ambiguous. It was approved to use leaf_type=* instead. | The values wood=coniferous and wood=deciduous are ambiguous. It was approved to use leaf_type=* instead. |
| 23 | Although it made sense in the past, nowadays it completely overlaps with name=*. More info here. | Même si cet attribut fut sensé auparavant, cet attribut a sensiblememt les mêmes fonctions que name=*. Voir plus d’infos. | Although it made sense in the past, nowadays it completely overlaps with name=*. More info here. | Although it made sense in the past, nowadays it completely overlaps with name=*. More info here. |
| 24 | Proposed features/Bridge types - was formerly used to map two very different bridge types (hanging/swinging rope bridges and movable swing bridges) | Proposed features/Bridge types - cet attribut a été utilisé pour désigner deux types de ponts différents. | Proposed features/Bridge types - was formerly used to map two very different bridge types (hanging/swinging rope bridges and movable swing bridges) | Proposed features/Bridge types - was formerly used to map two very different bridge types (hanging/swinging rope bridges and movable swing bridges) |
| 25 | Proposed features/Bridge types | Proposed features/Bridge types | Proposed features/Bridge types | Proposed features/Bridge types |
| 26 | The latter tag is more expressive than the former. | L’attribut charging_station est plus expressif. | The latter tag is more expressive than the former. | The latter tag is more expressive than the former. |
| 27 | Cycle routes | Cycle routes | Cycle routes | RU:Cycle routes |
| 28 | Proposed features/generator rationalisation | Proposed features/generator rationalisation | Proposed features/generator rationalisation | Proposed features/generator rationalisation |
| 29 | Proposed features/Building attributes has been abandoned. | Proposed features/Building attributes : projet abandonné. | Proposed features/Building attributes has been abandoned. | Proposed features/Building attributes has been abandoned. |
| 30 | Even though this tag is widely used, it has been deprecated by Proposed features/Water details. Both tagging schemes should persist for some time. | Même si cet attribut est très employé, il a été déprécié par Proposed features/Water details. Les deux schémas de balisage devraient coexister quelque temps. | Even though this tag is widely used, it has been deprecated by Proposed features/Water details. Both tagging schemes should persist for some time. | Even though this tag is widely used, it has been deprecated by Proposed features/Water details. Both tagging schemes should persist for some time. |
| 31 | No specific reason stated, should be replaced with an actual reason. Actual reason may be described at tag page, this entry also may be an invalidly listed one. | No specific reason stated, should be replaced with an actual reason. Actual reason may be described at tag page, this entry also may be an invalidly listed one. | No specific reason stated, should be replaced with an actual reason. Actual reason may be described at tag page, this entry also may be an invalidly listed one. | No specific reason stated, should be replaced with an actual reason. Actual reason may be described at tag page, this entry also may be an invalidly listed one. |
| 32 | Taken from Category:Tag descriptions with status "deprecated". Tagging as "leisure" has been proposed, while "amenity" has been marked as deprecated in the same time. | Repris de Category:Tag descriptions with status "deprecated". Alors que le schéma de balisage avec leisure a été proposé, le schéma avec amenity a été déprécié dans le même temps. | Taken from Category:Tag descriptions with status "deprecated". Tagging as "leisure" has been proposed, while "amenity" has been marked as deprecated in the same time. | Taken from Category:Tag descriptions with status "deprecated". Tagging as "leisure" has been proposed, while "amenity" has been marked as deprecated in the same time. |
| 33 | Taken from Category:Tag descriptions with status "deprecated". See DE:Tag:highway=no. | Repris de Category:Tag descriptions with status "deprecated". Voir également DE:Tag:highway=no | Taken from Category:Tag descriptions with status "deprecated". See DE:Tag:highway=no. | Taken from Category:Tag descriptions with status "deprecated". See DE:Tag:highway=no. |
| 34 | Taken from Category:Tag descriptions with status "deprecated". See also Talk:Tag:shop=organic. | Repris de Category:Tag descriptions with status "deprecated". Voir également la discussion Talk:Tag:shop=organic. | Taken from Category:Tag descriptions with status "deprecated". See also Talk:Tag:shop=organic. | Taken from Category:Tag descriptions with status "deprecated". See also Talk:Tag:shop=organic. |
| 35 | Proposed features/Telecom local loop (archive) | Proposed features/Telecom local loop (archive) | Proposed features/Telecom local loop (archive) | Proposed features/Telecom local loop (archive) |
| 36 | Taken from Category:Tag descriptions with status "deprecated". Originally designed to mark agricultural zones, this tag has confused many contributors, who tagged also buildings with it. | Repris de Category:Tag descriptions with status "deprecated". Au départ prévu pour délimiter les zones agricoles, l’attribut a créé de la confusion, car il a été utilisé aussi pour baliser des exploitations. | Taken from Category:Tag descriptions with status "deprecated". Originally designed to mark agricultural zones, this tag has confused many contributors, who tagged also buildings with it. | Taken from Category:Tag descriptions with status "deprecated". Originally designed to mark agricultural zones, this tag has confused many contributors, who tagged also buildings with it. |
| 37 | Taken from Category:Key descriptions with status "deprecated". | Repris de Category:Key descriptions with status "deprecated". | Taken from Category:Key descriptions with status "deprecated". | Taken from Category:Key descriptions with status "deprecated". |
| 38 | Proposed features/Escalators and Moving Walkways | Proposed features/Escalators and Moving Walkways | Proposed features/Escalators and Moving Walkways | Proposed features/Escalators and Moving Walkways |
| 39 | British English is preferred in tags. | L'anglais britannique est préféré dans les tags. | British English is preferred in tags. | British English is preferred in tags. |
| 40 | If there is an exit... it should be mapped! | Si la voie a bien une issue... celle-ci devrait être cartographiée ! | If there is an exit... it should be mapped! | If there is an exit... it should be mapped! |
| 41 | See OpenRailwayMap/Aktiventreffen 2014 2#Tracks. Clashes with railway=narrow_gauge when such railways are preserved. | L’usage de l’attribut déprécié ne permet pas d’exprimer qu’une voie à gabarit étroit (railway=narrow_gauge) a été conservée. Voir aussi OpenRailwayMap/Aktiventreffen 2014 2#Tracks. | See OpenRailwayMap/Aktiventreffen 2014 2#Tracks. Clashes with railway=narrow_gauge when such railways are preserved. | See OpenRailwayMap/Aktiventreffen 2014 2#Tracks. Clashes with railway=narrow_gauge when such railways are preserved. |
| 42 | Tag whose definition remains unclear. man_made=pier is way more widely used. | Attribut dont la définition reste peu claire ; man_made=pier est beaucoup plus utilisé. | Tag whose definition remains unclear. man_made=pier is way more widely used. | Tag whose definition remains unclear. man_made=pier is way more widely used. |
| 43 | Do not make any automated edit for this: read WikiProject Whitewater Maps. | Ne faites pas de modification automatisée pour cet attribut — lisez WikiProject Whitewater Maps. | Do not make any automated edit for this: read WikiProject Whitewater Maps. | Do not make any automated edit for this: read WikiProject Whitewater Maps. |
| 44 | Proposed features/Gambling | Proposed features/Gambling | Proposed features/Gambling | Proposed features/Gambling |
| 45 | Proposed features/seafood shop | Proposed features/seafood shop | Proposed features/seafood shop | Proposed features/seafood shop |
| 46 | Proposed features/agricultural Field#Conclusion? | Proposed features/agricultural Field#Conclusion? | Proposed features/agricultural Field#Conclusion? | Proposed features/agricultural Field#Conclusion? |
| 47 | WikiProject Emergency Cleanup | WikiProject Emergency Cleanup | WikiProject Emergency Cleanup | WikiProject Emergency Cleanup |
| 48 | Introduction of barrier=* | Introduction de barrier=* | Introduction of barrier=* | Usage of American form color probably mainly due to a bug in JOSM presets. |
| 49 | Taken from Category:Tag descriptions with status "deprecated". Besides, the deprecated tagging does not indicate which kind of amenity (or whatever) it used to/will be... See also Lifecycle prefix. | Repris de Category:Tag descriptions with status "deprecated". La version dépréciée n'indique d'ailleurs pas de quel équipement (ou autre) il s'agissait/ra... Voir aussi Lifecycle prefix. | Taken from Category:Tag descriptions with status "deprecated". Besides, the deprecated tagging does not indicate which kind of amenity (or whatever) it used to/will be... See also Lifecycle prefix. | Taken from Category:Tag descriptions with status "deprecated". Besides, the deprecated tagging does not indicate which kind of amenity (or whatever) it used to/will be... See also Lifecycle prefix. |
| 50 | Taken from Category:Tag descriptions with status "deprecated". There is currently no consensus on the preferred tagging suggestions, as both got consensus on Oct. 2009 (Proposed features/Additional parking types for amenity=parking; Proposed features/tag:landuse=garages). | Repris de Category:Tag descriptions with status "deprecated". Il n'y a actuellement pas de consensus sur une préférence de suggestion; les deux ont reçu un consensus en octobre 2009 (Proposed features/Additional parking types for amenity=parking; Proposed features/tag:landuse=garages). | Taken from Category:Tag descriptions with status "deprecated". There is currently no consensus on the preferred tagging suggestions, as both got consensus on Oct. 2009 (Proposed features/Additional parking types for amenity=parking; Proposed features/tag:landuse=garages). | Taken from Category:Tag descriptions with status "deprecated". There is currently no consensus on the preferred tagging suggestions, as both got consensus on Oct. 2009 (Proposed features/Additional parking types for amenity=parking; Proposed features/tag:landuse=garages). |
| 51 | A star '*' should not be considered as a correct value tag. | L'astérisque '*' ne devrait pas être considérée comme une valeur d'attribut correcte. | A star '*' should not be considered as a correct value tag. | A star '*' should not be considered as a correct value tag. |
| 52 | This tag is confusing. A furnace is a big oven used for melting metals; some people also applied this tag for shops selling cooking stoves. | 'furnace' en anglais signifie principalement fourneau - donc pour fondre le métal; certains ont utilisé ce tag pour identifier les vendeurs de fours ménagers. | This tag is confusing. A furnace is a big oven used for melting metals; some people also applied this tag for shops selling cooking stoves. | This tag is confusing. A furnace is a big oven used for melting metals; some people also applied this tag for shops selling cooking stoves. |
| 53 | In Arabic wadi means valley, but this conflicts with explanations in Wikipedia and probably with interpretations in various parts of the world. For initial discussion that ended with wadi deprecation see https://lists.openstreetmap.org/pipermail/tagging/2015-January/thread.html#20946. Beware that this kind of edit requires local knowledge: it is impossible to do it correctly with mass replace without local knowledge. | En arabe, wadi signifie vallée, mais cela entre en conflit avec les explications données sur Wikipédia et, probablement, avec les interprétations en divers endroits du monde. | In Arabic wadi means valley, but this conflicts with explanations in Wikipedia and probably with interpretations in various parts of the world. For initial discussion that ended with wadi deprecation see https://lists.openstreetmap.org/pipermail/tagging/2015-January/thread.html#20946. Beware that this kind of edit requires local knowledge: it is impossible to do it correctly with mass replace without local knowledge. | In Arabic wadi means valley, but this conflicts with explanations in Wikipedia and probably with interpretations in various parts of the world. For initial discussion that ended with wadi deprecation see https://lists.openstreetmap.org/pipermail/tagging/2015-January/thread.html#20946. Beware that this kind of edit requires local knowledge: it is impossible to do it correctly with mass replace without local knowledge. |
| 54 | Implementation of location=* key by Proposed features/PipelineExtension which also supports underwater. | L'attribut location=* proposé par Proposed features/PipelineExtension permet de tagger aussi les localisations sous-marines. | Implementation of location=* key by Proposed features/PipelineExtension which also supports underwater. | Implementation of location=* key by Proposed features/PipelineExtension which also supports underwater. |
| 55 | Proposed features/Government offices | Proposed features/Government offices | Proposed features/Government offices | Proposed features/Government offices |
| 56 | The difference between a condominium and an apartment is purely legal, difficult to verify, and unimportant to OSM. | The difference between a condominium and an apartment is purely legal, difficult to verify, and unimportant to OSM. | The difference between a condominium and an apartment is purely legal, difficult to verify, and unimportant to OSM. | The difference between a condominium and an apartment is purely legal, difficult to verify, and unimportant to OSM. |
| 57 | Deprecated by the Proposed features/Utility markers proposal. | Deprecated by the Proposed features/Utility markers proposal. | Deprecated by the Proposed features/Utility markers proposal. | Deprecated by the Proposed features/Utility markers proposal. |
| 58 | Proposed features/automated external defibrillator (archive) | Proposed features/automated external defibrillator (archive) | Proposed features/automated external defibrillator (archive) | Proposed features/automated external defibrillator (archive) |
| 59 | Proposed features/Manufacturer and Model#Rationale_of_the_proposal | Proposed features/Manufacturer and Model#Rationale_of_the_proposal | Proposed features/Manufacturer and Model#Rationale_of_the_proposal | Proposed features/Manufacturer and Model#Rationale_of_the_proposal |
| 60 | As discussed on https://lists.openstreetmap.org/pipermail/talk/2023-March/088110.html and https://community.openstreetmap.org/t/type-of-stone-in-surface-surface-granite-and-similar/9424 | As discussed on https://lists.openstreetmap.org/pipermail/talk/2023-March/088110.html and https://community.openstreetmap.org/t/type-of-stone-in-surface-surface-granite-and-similar/9424 | As discussed on https://lists.openstreetmap.org/pipermail/talk/2023-March/088110.html and https://community.openstreetmap.org/t/type-of-stone-in-surface-surface-granite-and-similar/9424 | As discussed on https://lists.openstreetmap.org/pipermail/talk/2023-March/088110.html and https://community.openstreetmap.org/t/type-of-stone-in-surface-surface-granite-and-similar/9424 |
| 61 | Proposal:Continuous crossings | Proposal:Continuous crossings | Proposal:Continuous crossings | Proposal:Continuous crossings |
| 62 | ||||
| 63 | Proposed features/hazard | Proposed features/hazard | Proposed features/hazard | Proposed features/hazard |
| 64 | On 01/01/2015, there was about 12,000 uses of amenity=fire_hydrant and 300,000 uses of emergency=fire_hydrant. 9,000 of the 12,000 had both tags. Both were allowed. Early July 2015, there was around 0 uses of amenity=fire_hydrant. On 09/11/2015, amenity=fire_hydrant has been deprecated. | On 01/01/2015, there was about 12,000 uses of amenity=fire_hydrant and 300,000 uses of emergency=fire_hydrant. 9,000 of the 12,000 had both tags. Both were allowed. Early July 2015, there was around 0 uses of amenity=fire_hydrant. On 09/11/2015, amenity=fire_hydrant has been deprecated. | On 01/01/2015, there was about 12,000 uses of amenity=fire_hydrant and 300,000 uses of emergency=fire_hydrant. 9,000 of the 12,000 had both tags. Both were allowed. Early July 2015, there was around 0 uses of amenity=fire_hydrant. On 09/11/2015, amenity=fire_hydrant has been deprecated. | On 01/01/2015, there was about 12,000 uses of amenity=fire_hydrant and 300,000 uses of emergency=fire_hydrant. 9,000 of the 12,000 had both tags. Both were allowed. Early July 2015, there was around 0 uses of amenity=fire_hydrant. On 09/11/2015, amenity=fire_hydrant has been deprecated. |
| 65 | Replaced by new street parking schema, that is intended to be easier and more logical to apply, follows established OSM conventions more closely and harmonises tagging of parking spaces mapped on the centerline as an attribute of a street with parking spaces mapped as a separate feature. | Replaced by new street parking schema, that is intended to be easier and more logical to apply, follows established OSM conventions more closely and harmonises tagging of parking spaces mapped on the centerline as an attribute of a street with parking spaces mapped as a separate feature. | Replaced by new street parking schema, that is intended to be easier and more logical to apply, follows established OSM conventions more closely and harmonises tagging of parking spaces mapped on the centerline as an attribute of a street with parking spaces mapped as a separate feature. | Replaced by new street parking schema, that is intended to be easier and more logical to apply, follows established OSM conventions more closely and harmonises tagging of parking spaces mapped on the centerline as an attribute of a street with parking spaces mapped as a separate feature. |
| 66 | this key has no clear meaning, and isn’t relevant to the suggested combinations. | this key has no clear meaning, and isn’t relevant to the suggested combinations. | this key has no clear meaning, and isn’t relevant to the suggested combinations. | this key has no clear meaning, and isn’t relevant to the suggested combinations. |
| 67 | 1. Using this relation was time-consuming. 2. Mixing railway=facility with public_transport=stop_area resulted in complex and confusing tagging like type=public_transport + public_transport=stop_area + railway=facility for passenger stations and railway=facility without any type=* for non-passenger stations. 3. It resulted in mixing tags like public_transport=stop_position and railway=subway_entrance with features such as landuse=* from a railway operations perspective. 4. This relation duplicated a lot of tags of railway=station. 5. This relation mapped one real world feature as two features in OSM, which is not a good practice. Related discussion |
1. Using this relation was time-consuming. 2. Mixing railway=facility with public_transport=stop_area resulted in complex and confusing tagging like type=public_transport + public_transport=stop_area + railway=facility for passenger stations and railway=facility without any type=* for non-passenger stations. 3. It resulted in mixing tags like public_transport=stop_position and railway=subway_entrance with features such as landuse=* from a railway operations perspective. 4. This relation duplicated a lot of tags of railway=station. 5. This relation mapped one real world feature as two features in OSM, which is not a good practice. Related discussion |
1. Using this relation was time-consuming. 2. Mixing railway=facility with public_transport=stop_area resulted in complex and confusing tagging like type=public_transport + public_transport=stop_area + railway=facility for passenger stations and railway=facility without any type=* for non-passenger stations. 3. It resulted in mixing tags like public_transport=stop_position and railway=subway_entrance with features such as landuse=* from a railway operations perspective. 4. This relation duplicated a lot of tags of railway=station. 5. This relation mapped one real world feature as two features in OSM, which is not a good practice. Related discussion |
1. Using this relation was time-consuming. 2. Mixing railway=facility with public_transport=stop_area resulted in complex and confusing tagging like type=public_transport + public_transport=stop_area + railway=facility for passenger stations and railway=facility without any type=* for non-passenger stations. 3. It resulted in mixing tags like public_transport=stop_position and railway=subway_entrance with features such as landuse=* from a railway operations perspective. 4. This relation duplicated a lot of tags of railway=station. 5. This relation mapped one real world feature as two features in OSM, which is not a good practice. Related discussion |
| 68 | Replaced by the more recent and more logical oneway:bicycle=* tagging; mixed infrastructure and access/direction information; logical problems if used with cycleway side suffixes; exclusion of other transport modes and other associated problems (see deprecation proposal for details). | Replaced by the more recent and more logical oneway:bicycle=* tagging; mixed infrastructure and access/direction information; logical problems if used with cycleway side suffixes; exclusion of other transport modes and other associated problems (see deprecation proposal for details). | Replaced by the more recent and more logical oneway:bicycle=* tagging; mixed infrastructure and access/direction information; logical problems if used with cycleway side suffixes; exclusion of other transport modes and other associated problems (see deprecation proposal for details). | Replaced by the more recent and more logical oneway:bicycle=* tagging; mixed infrastructure and access/direction information; logical problems if used with cycleway side suffixes; exclusion of other transport modes and other associated problems (see deprecation proposal for details). |
| 69 | Lane count becomes ambiguous, redundancy with modern and better tools, exclusion of other transport modes and other associated problems (see deprecation proposal for details). | Lane count becomes ambiguous, redundancy with modern and better tools, exclusion of other transport modes and other associated problems (see deprecation proposal for details). | Lane count becomes ambiguous, redundancy with modern and better tools, exclusion of other transport modes and other associated problems (see deprecation proposal for details). | Lane count becomes ambiguous, redundancy with modern and better tools, exclusion of other transport modes and other associated problems (see deprecation proposal for details). |
| 70 | ||||
| 71 | ||||
| 72 | ||||
| 73 | ||||
| 74 | ||||
| 75 | ||||
| 76 | ||||
| 77 | ||||
| 78 | ||||
| 79 | ||||
| 80 | ||||
| 81 | ||||
| 82 | ||||
| 83 | ||||
| 84 | Redundant tag. | Attribut redondant. | Redundant tag. | Redundant tag. |
| 85 | ||||
| 86 | ||||
| 87 | ||||
| 88 | ||||
| 89 | ||||
| 90 | Poor or ambiguous semantics. | Poor or ambiguous semantics. | Poor or ambiguous semantics. | Poor or ambiguous semantics. |
| 91 | Mapping such toilets is the bad practice. See Good practice | Mapping such toilets is the bad practice. See Good practice | Mapping such toilets is the bad practice. See Good practice | Mapping such toilets is the bad practice. See Good practice |
| 92 | ||||
| 93 | ||||
| 94 | ||||
| 95 | Proposed features/shop as post-partner | Proposed features/shop as post-partner | Proposed features/shop as post-partner | Proposed features/shop as post-partner |
| 96 | ||||
| 97 | The embassy=embassy tag has been deprecated by a voteː Proposed features/deprecate embassy=embassy. | Le tag embassy=embassy a été déprécié par un vote ː Proposed features/deprecate embassy=embassy. | The embassy=embassy tag has been deprecated by a voteː Proposed features/deprecate embassy=embassy. | The embassy=embassy tag has been deprecated by a voteː Proposed features/deprecate embassy=embassy. |
| 98 | The boundary=forestry_compartment tag has been deprecated by a voteː Proposed features/boundary=forest(_compartment) relations (v3). | Le tag boundary=forestry_compartment a été déprécié par un vote ː Proposed features/boundary=forest(_compartment) relations (v3). | The boundary=forestry_compartment tag has been deprecated by a voteː Proposed features/boundary=forest(_compartment) relations (v3). | The boundary=forestry_compartment tag has been deprecated by a voteː Proposed features/boundary=forest(_compartment) relations (v3). |
| 99 | This is a misleading use of building=* & it conflates different types of (collapsed) buildings. | This is a misleading use of building=* & it conflates different types of (collapsed) buildings. | This is a misleading use of building=* & it conflates different types of (collapsed) buildings. | This is a misleading use of building=* & it conflates different types of (collapsed) buildings. |
| 100 | ||||
| ... |