I appear to have found a genuine case of a false positive identification in that a single FITS file will produce radically different WCS values according to the level of down sampling with the -z option to solve-field. I would attach the file but for its size:
pcl@horus ~/astro/M33 $ time solve-field -z 8 -K -p foo.fits &
[2] 15628
pcl@horus ~/astro/M33 $ Reading input file 1 of 1: "foo.fits"...
Extracting sources...
This looks like a multi-color image: processing the first image plane only. (NAXIS=3)
Downsampling by 8...
simplexy: found 509 sources.
Solving...
Reading file "./foo.axy"...
log-odds ratio 156.949 (1.45231e+68), 57 match, 0 conflict, 91 distractors, 80 index.
RA,Dec = (22.8644,30.4697), pixel scale 3.06535 arcsec/pix.
Hit/miss: Hit/miss: ++-+++++++++++++++++-++++++-++-++++--+-+-+-+-+-+++--------+----++-+--++--+-+--++----------+---------
Field 1: solved with index index-4211.fits.
Field 1 solved: writing to file ./foo.solved to indicate this.
Field: foo.fits
Field center: (RA,Dec) = (22.863853, 30.476194) deg.
Field center: (RA H:M:S, Dec D:M:S) = (01:31:27.325, +30:28:34.299).
Field size: 5.15412 x 3.44867 degrees
Field rotation angle: up is 86.1826 degrees E of N
Field parity: pos
Creating new FITS file "./
foo.new"...
real 0m12.689s
user 0m11.883s
sys 0m0.487s
The first is correct. The FITD file was created from a NEF-format raw image of the M33 region in Triangulum. The second WCS is way out in the weeds.