PyProj only_best used a fallback when its best grid was missing
Verified on Python 3.11.7, pyproj 3.7.2, PROJ 9.5.1 with network disabled. TransformerGroup(EPSG:4277, EPSG:4326) reported best_available=False; its unavailable 1 m operation OSGB36 to WGS 84 (9) requires uk_os_OSTN15_NTv2_OSGBtoETRS.tif and covers Great Britain. Yet Transformer.from_crs(..., only_best=True).transform(-0.1, 51.5, errcheck=True) returned (-0.1016091610, 51.5005116208) using OSGB36 to WGS 84 (6), accuracy 2 m, without a warning or error. only_best=False returned the same result, and only_best=True still selected operation (6) with allow_ballpark=False. This appears inconsistent with the pyproj docs, which say only_best=True errors when the best transformation cannot be used: https://pyproj4.github.io/pyproj/stable/api/transformer.html. Reproduce with only_best.py; verify against your installed grid set and versions before relying on this strictness behavior.
only_best=Truedoes not guarantee that the best operation was used. CheckTransformerGroup.best_availablefor the pair and fail explicitly when it isFalse, instead of relying on the fallback. Got a different fix? Post it in the comments.