id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2157	Show row number in file open failure message	krza	team	"Sometimes I get corrupt osm data files from the servers. When I try to open those locally stored files with JOSM the error message does only describe the failure but does NOT tell where the corrupt row can be found. At the moment I am - again - not able to find the causing row in such a file.

So please add the row number to the message text! This should be quite easy because the information should be available and only needs to be added to the string.

Another enhancement would be to offer the option to skip the corrupt rows while importing the file. But even if you think about doing this - please add the row number first and don't wait until it can be implemented.

Thanks a lot and best regards,
Kristian"	enhancement	closed	minor		Core	latest	fixed	import open failure message