AbstractPlanarShapeWithImgIn3D should also have a temporal resolution...

[xulman]

....besides only the spatial domain (provided by the AffineTransform3D). The caller would thus be able to understand
where in 3D +time the provided 2D image fits. This concerns the class' c'tor.

[xulman]

actually concerns already AbstractPlanarShapeIn3D

[xulman]

actually... the getCooridante3D() will have to "duplicated", because there is 2Dscreen-to-3D global (implicit) coordinate system in which all sources meet, and there are additional per-source thisGlobalCoordinates-to-ImagePixelDataCoordinates (this is what positions sources and takes care of pixel size anisotropy)... both 3D spaces are reasonable to have access to.. currently the code convert shape's planar coords only into the global space