Sharpcap saves WCS data in FITS header
Posted: Tue Nov 11, 2025 3:40 pm
Hello all,
I use SharpCap for double star astrometry and I use platesolve3 (configured in SharpCap and set-up as default solver) to go to the correct target. In my last session somehow, after plate solving within SharpCap and sync the mount to center to the target, I found the following WCS data all in my FITS headers of all my frames (Image01). They also had the line which says the solution was provided by SharpSolve (image02).
This is however strange... As shown in image03 and image04, SharpSolve is even not set up or configured and I remember the positions were clearly solved by platesolve3 as I saw the popup.
Now for me this is problematic as I need to solve these images separately to have the correct CD matrix for each image. Now the images are populated already with the WCS data of the last platesolve during the imaging session. This seem to be a recent change as before, even using platesolving to position on the correct target, SharpCap did never write WCS data into the fits headers.
So my question.. is this a new behavior ? And most important... how to avoid SharpCap writing WCS or any other astrometric data to the FITS headers ?
I use SharpCap for double star astrometry and I use platesolve3 (configured in SharpCap and set-up as default solver) to go to the correct target. In my last session somehow, after plate solving within SharpCap and sync the mount to center to the target, I found the following WCS data all in my FITS headers of all my frames (Image01). They also had the line which says the solution was provided by SharpSolve (image02).
This is however strange... As shown in image03 and image04, SharpSolve is even not set up or configured and I remember the positions were clearly solved by platesolve3 as I saw the popup.
Now for me this is problematic as I need to solve these images separately to have the correct CD matrix for each image. Now the images are populated already with the WCS data of the last platesolve during the imaging session. This seem to be a recent change as before, even using platesolving to position on the correct target, SharpCap did never write WCS data into the fits headers.
So my question.. is this a new behavior ? And most important... how to avoid SharpCap writing WCS or any other astrometric data to the FITS headers ?