This is more of a question about how GDAL 3.x and PROJ 7.x work more than a question about how to do something. I have been experimenting with GDAL 3.4.2 and have noticed some things that are different about how gdalwarp is working. I was previously using GDAL 2.3.1.
The issue I am having is that when I try to do a gdalwarp operation on an image that is out of the applicable area of a projection, I get an error that says something like "ERROR 6: Cannot find coordinate operations from EPSG:4326 to EPSG:4326" or something along those lines (EPSG:4326 is NAD83). If I change the georeferencing on the image to a part of the world where the projection is applicable (North America), the gdalwarp operation works without any errors. In GDAL 2.3.1, there were no errors in either case.
As an example, if I run the following gdalwarp command on this image located somewhere in Spain but assigned a NAD83 projection, I get an error message:
gdalwarp.exe -ts 550 534 -te -1.9269800000000 43.3142800000000 -1.9055500000000 43.3350900000000 -r cubic -dstalpha spain.tif -overwrite testSP.tif
However, if I run a similar gdalwarp command on the same image georeferenced somewhere in North America and assigned a NAD83 projection located here (I just translated the longitude coordinates 112 degrees west), I do not get an error message and the output is created correctly:
gdalwarp.exe -ts 550 534 -te -113.9269800000000 43.3142800000000 -113.9055500000000 43.3350900000000 -r cubic -dstalpha us.tif -overwrite testUS.tif
Any ideas about this? Does the newer verison of GDAL/PROJ do some kind of bounds checking to see if the image being warped is within the valid bounds of the projection area?