id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
14133	mismatching of data and imagery projections	greg.schmidt@…	team	"Background:
- we have played around using the different imagery projections in JOSM, switching between imagery sources of 3857 and 4326.  The imagery loader properly does not allow an imagery source other than what JOSM is setup for to load (i.e. if JOSM set to load 4326, it will refuse to load a 3857 source properly).  Good so far.
- When we switch to imagery using 4326, and still have a OSM data source dishing out 3857 vector data, JOSM allows it do display and does not put out a warning.  

Questions:
1) is this what everyone else has observed?
2) does JOSM not automatically reproject the 3857 data vector source to the source that imagery is in (.e.g. 4326)?
3) should JOSM put out a warning if the data vectors are of a different projection than what is assigned for the imagery?

Mark this ticket as a possible defect for now.
"	defect	closed	normal		Core	latest	invalid	projection