a bug in querying target by using different form of coordinates in ESASky

Ming Yang 7 months ago updated by Jeffrey Simons 4 weeks ago 4

Dear whom it may concern, I just found out that there might be a bug in querying target by using different form of coordinates. For example, if I use the name of NGC291 or sexagesimal coordiante of 00:53:29.931-08:46:03.48, ESASky shows correct image of the target. However, if I use the decimal coordiante of 13.374713 -08.767633, ESASky shows incorrect field without target in the FOV. Could you check it please? Thanks~

I am still waiting for the next ESASky update because even with this version, I'm still experiencing some bugs. Ever since gacha life 2 has come out, I haven't taken a look at some other features of ESASky but I hope that they'll be even better when the next update arrives.

Dear Ming Yang,

This issue is about to be fixed in the next version of ESASky which is planned for release in mid September.

Many thanks,



Dear Ming Yang,

Thanks for pointing this out. Currently in ESASky the decimal coordinates require three numbers before the decimal point, e.g. 013.374713 -08.767633  goes to the correct target. Otherwise ESASky interprets the first coordinate as RA in 'decimal' hours, but probably we should assume 13.374713 -08.767633 is decimal, and if users want hours then they specify it as 13.374713h -08.767633d.

We'll make the change and let you know when it's updated!

Many thanks and regards,

Deborah, on behalf of the ESASky team