id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
11104	Test incomplete objects	naoliv	team	"We are adding some tests for incomplete objects in OSM (commonly included in OSM by new users):

{{{
#!mapcss
*[area][eval(number_of_tags()) = 1],
*[lanes][eval(number_of_tags()) = 1],
*[maxspeed][eval(number_of_tags()) = 1],
*[name][eval(number_of_tags()) = 1],
*[oneway][eval(number_of_tags()) = 1],
*[ref][eval(number_of_tags()) = 1]
*[surface][eval(number_of_tags()) = 1] {
        throwWarning: tr(""incomplete object: only {0}"", ""{0.key}"");
}


*[name][area][eval(number_of_tags()) = 2],
*[name][ref][eval(number_of_tags()) = 2],
*[name][surface][eval(number_of_tags()) = 2] {
        throwWarning: tr(""incomplete object: only {0} and {1}"", ""{0.key}"", ""{1.key}"");
}
}}}

Is it interesting to include in JOSM? (with a better warning message, etc)"	enhancement	closed	normal	15.02	Core validator		fixed