id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
19148	Problems with multipolygon consisting of several separate areas with same primary tag but different secondary tags.	skyper	team	"This came up in #19136, see my [ticket:19136#comment:22 comment 22] and followups.
I've created an example file: 
[attachment:ticket:19136:josm_19136_multi_with_same_style_sample.osm josm_19136_multi_with_same_style_sample.osm]

If I have two parts of a forest with a name in common but the parts have different `operator` and different `leaf_type`. I need to leave the secondary tags on the parts and maybe use more general values for the multipolygon.
* Only secondary tags on a area without primary tag is not working
 * ""Create multipolygon"" just does that
* Simply adding the name to both parts contradicts: One feature one object
* Only a cheat, creating multipolygons for each area and an additional one for the group is accepted by validator
* I do not use `type=site` as osmwiki:Tag:type=site explicitly stats:
 > **This relation is not to be used in cases where the element can be represented by one or more areas and neither linear ways nor nodes outside these areas would have to be included or excluded from within these areas.**

=== Multi_Multi (no warning)
Same as ""Valid but warning"" but with multipolygons for each part. I get no warning.
* Should trigger the same warnings as ""Valid but warning"" cause it is just a different mapping style
* Additional warnings for the ""forest"" multipolygons without `name` as are not needed with only one `outer` without any primary tags

=== Wood vs Forest
I get `With the currently used mappaint style the style for outer way mismatches the area style (2)`
* `wood` and `forest` should be treated as synonyms, e.g. no warning

=== Valid but warning
I get `Area style on outer way (2)`
* Right, but not worse a warning as this is a valid case

=== Incorrect
I get no warning. This is the result of ""create multipolygon"". Use the two areas on the right side.
* Both areas do not have a primary tag, needs a warning: `Object with only secondary tags`

=== ""Create multipolygon""
I get no info if not all tags from `outer` are moved to the relation`
* I expect a warning if this is not possible
* Moving only the primary tag and leaving only secondary tags on the areas does not solve the problem.

{{{
Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-04-23 21:58:14 +0200 (Thu, 23 Apr 2020)
Revision:16376
Build-Date:2020-04-24 01:30:45
URL:https://josm.openstreetmap.de/svn/trunk
}}}
"	defect	new	normal		Core			template_report multipolygon