Calls to CRS.findOperation(sourceCRS, targetCRS) sometime produces a CoordinateOperation with wrong metadata (name, identifiers, remarks, scope). For example requesting an operation from EPSG::4202 to EPSG::4283 should produce the following operation (when there is no NTv2 datum shift grid available):
But we get instead the name "Ellipsoidal 2D CS. Axes: longitude, latitude. Orientations: east, north. UoM: degree" together with identifier and remarks of EPSG::6424 coordinate system. The accuracy, scope, area and bounding box are lost. The bug is in EPSGDataAccess where metadata are accidentally overwritten before we finished to construct the CoordinateOperation. This bug affects only metadata; the coordinate operation parameters are unaffected so the numerical results of coordinate operations should be the same.