Missing SITELAT and SITELONG

[Bill Tschumy]

I have been trying to use FIT files generated by ASIAir in ASTAP. I keep getting:

Error decoding site longitude or latitude!

in the log. It appears the SITELAT and SITELONG key are missing. It seems like some features don't work without the observer's location, although possibly I'm doing something else wrong.

Are these required for proper functioning? How are others dealing with this?

[han.k]

Hello Bill,

Latitude and longitude have only a small influence on the position of asteroids only. I haven't tested the asiair files for some time. Can you give me one sample file for testing. E.g. upload to
https://ufile.io/

and give me the link.

Han

[Bill Tschumy]

Han,

Thanks for responding. Here is wha comes out in the status window:

06:30:17 Instructions:
06:30:17 1: Synchronise the mount and take one image.
06:30:17 2: Slew the mount to a second point in the sky and take a second image without synchronising the mount.
06:30:17 Conditions: The image header should contain the correct time, observer location and mount position. Images should be solvable.
06:30:17 Error decoding site longitude or latitude!
06:30:17 Error decoding site longitude or latitude!
06:30:17 Error decoding site longitude or latitude!
06:30:17 Image 1: /Users/bill/Desktop/Live/Light/M1/Stack30_Light_M1_10.0s_Bin1_20220128-205629.fit
06:30:17 Skipped image /Users/bill/Desktop/Live/Light/Alnitak/Stack40_Light_Alnitak_10.0s_Bin1_20220128-201609.fit. The angular distance between the two images is 0.0° and too small!
06:30:17 Skipped image /Users/bill/Desktop/Live/Light/M35/Stack25_Light_M35_10.0s_Bin1_20220128-195057.fit. The angular distance between the two images is 0.0° and too small!
06:30:17 Error decoding site longitude or latitude!
06:30:17 Error decoding site longitude or latitude!
06:30:17 Error decoding site longitude or latitude!

So, looking at the instructions in the log, maybe my problem was "take a second image without synchronising the mount." I am using ASIAir to take the images. I assume it does synchronize the mount after each plate solve for centering? Maybe that is the issue? I can still upload my images if you think it is something else.

[han.k]

If you upload one image, then I can see the latitude and longitude format in the header. I assume ZWO is not following the standard. But I can only check if I can inspect the image header.

[Bud MacCloud]

I too am having this exact same issue. Was there ever a resolution to this?

[han.k]

Hi Bud,

Give me a fits image for testing. I have not received a fits file for testing. E.g. upload to https://ufile.io/

and give me the link either here or by personal message.

Han

[Bud MacCloud]

Thanks han.k
https://ufile.io/lj5hd0k2

[han.k]

Hi Bud,

The information is just not there (in the header). Maybe it is optional in the ZWO software? For the long run you could ask ZWO to improve their software. by adding it to the FITS header.

For ASTAP just enter the values manually in the program once. Then your fine.

Han

[andy nikolenko]

Han, can you please tell me how to enter long/lat position manually ? I cannot seems find place to enter it in application manually?
I try to use astrometric alignment to combine images but getting errors mentioned above ( Error decoding site longitude or latitude! ). Images come directly from DSLR so they don't have long/lat info...
Thanks!

[han.k]

Short cut: Ctrl+R

Menu: Annotation of asteroids abd comets. See attached.

I agree not the most logical place.

Han

[andy nikolenko]

Thank you !
May be it would be reasonable to create common Settings panel, where such info like Long/lat, default values for example for Focal length, pixel size etc can be stored permanently ?