id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23397	Improve the results of partial validations	GerdP	GerdP	"I open this ticket because of a discussion in the german forum:
https://community.openstreetmap.org/t/selbstuberschneidende-linien-arbeitet-der-datenprufer-bei-josm-sauber/107483

The current status regarding the JOSM validator is quite confusing and unsatisfactory.
We distinguish between 
- full test
- partial test 
- Test before upload 
Problems:
- A full test typically reports so many problems that those caused by my own changes are difficult to find.
- A partial test doesn't always find simple but important geometry errors when e.g. a node of a road is moved so that the road crosses a building or a node of an area way is moved so that the area gets self-crossing. Reason is that the ways are not treated as modified and therefore not passed to the tests.

A lot of code was added to particular tests to select the ""correct"" objects, e.g. MapCss tests which calculate insideness first calculate the objects which might be concerned.
Still, many important tests don't work well, e.g. `CrossingWays` or `SharpAngles` or `UnconnectedWays`.

I am still not 100% sure how to handle this, but I think almost all users would expect that all parent ways and relations of a node which is moved are passed to all tests, even those which test only the tags of the parent object.
Besides that we should change the tests which need to know all other ways to produce reasonable results to just use all ways and maybe remove unwanted findings.
"	enhancement	closed	normal	24.01	Core validator	tested	fixed