Auto-Fil Lat and Lon

[Ned Smith]

My FITS heder uses negative West for Longitude. The Asteroid & Comets Annotation form seems to expect Positive West. Anyting I can do about that excpet entering data by hand?

[han.k]

I changed it in ASTAP 0.9.379 since the FITS header records normally east as positive (based on ESA https://indico.esa.int/event/124/attachments/711/771/06_ESA-SSA-NEO-RS-0003_1_6_FITS_keyword_requirements_2014-08-01.pdf and same for Maxim DL by Diffractionlimited)

I also found and fixed a major bug. The longtude was interpretated as hours rather then degrees.

Both the Windows version as Linux versions are updated. The Mac version will follow later in the day.

Clear skies, Han

[han.k]

For ASTAP 0.9.380 I made an other correction in the midpoint time calculation. Annotation is now more accurate.

[Ned Smith]

Using version 0.9.3.380. When I solve an imae and cliclk on Tools>Asteroids & Comets annotation, the Lat/Lon boxes are red. The file name is in the window. I assume the red means the program has not picked up those values from the FITS file. Proceding with the annotation seems to work correctly anyway.

[han.k]

Red means conversion failure. The position error based on the position on earth is small so it will be difficult to see the effect.

Can you copy the two lines from the header containing the position so I can look why it doesn't work? You could send me a personal message if you want to keep it private or change a digit.

[Ned Smith]

SIMPLE  =                    T / C# FITS: 06/16/2020 04:33:05
rest header removed by administrator for privacy reasons.

On 6/26/20 13:01, han.k wrote:

Red means conversion failure. The position error based on the position
on earth is small so it will be difficult to see the effect.

Can you copy the two lines from the header containing the position so
I can look why it doesn't work? You could send me a personal message
if you want to keep it private or change a digit.

---

Auto-Fil Lat and Lon
https://sourceforge.net/p/astap-program/discussion/general/thread/cd79d4a105/?limit=25#a5d3

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/astap-program/discussion/general/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Ned Smith

[han.k]

Thanks for the info. Found and fixed the problem is the development version 0.9.381:

http://www.hnsky.org/astap_setup.exe

The problem was cause by the unknown keywords OBSLONG, OBSLAT. I have added them to the fits file reader. I also added keyword OBS-LONG, OBS-LAT. With SITELONG, SITELAT that should work for most FITS files.

The different keywords used is a problem. There is no complete central standard of fits keywords.

Clear skies, Han

[Ned Smith]

Trying to solve the attached image I noticed that the RA taken from the FITS header does not match the RA in the header.

[han.k]

That could be interesting to investigate. Upload the file to:

https://ufile.io/

and give the link. This link works for large files

Han

[han.k]

Okay, got the file

[han.k]

RA in header and ASTAP match. Note the RA in the header is in 0 .. 360 degrees while normally it is in 0.. 24 hours. You have to correct with a factor 24/360. See attached:

The image doesn't solve since there is severe tracking error problem. All stars are oval/elongated