Dear Bruno,

Thank you for reporting this. We are working with the HST team to produce updated HST HiPS and expose them in ESASky as soon as possible.

Kind regards,

Deborah

Dear Nora,

Yes we agree! We are currently working on this (for all ESA missions in operation), firstly for the mission metadata and footprints, then at a later date on the HiPS that the ESASky team generate. 

We'll let you know when it's ready for testing.

Many thanks and regards,

Debbie

Dear Karl,

I don't know where you can find DS9 region files for the JWST instrument footprints but I've been advised by JWST colleagues to direct you to the official JWST Helpdesk at STSCI:

https://stsci.service-now.com/jwst

If the information isn't there, someone on that helpdesk will be able to answer your question.

Kind regards,

Deborah

Dear Karl,

We are working on this feature but currently don't have it available in ESASky, apologies. We'll also work on a possibility using pyESASky, the ESASky python widget. We'll let you know when these features are available.

Kind regards,

Deborah, on behalf of the ESASky team

Dear User,

Thanks for the warning. We already have an HTTPS version of ESASky. Currently, we have kept the HTTP connection in order to use SAMP (Simple Application Messaging Protocol) which is not HTTPS native "friendly". Can you give us more details to better understand the issue?

Best regards,

Deborah, on behalf of the ESASky Team

Dear Bart,

Many thanks for informing us, we'll get on to fixing this right away and let you know when it's done.

Best regards,

Deborah, on behalf of the ESASky Team

Dear Alvaro,

The issue has now been fixed in the ESASky astroquery module. If you update astroquery you should find the module working correctly now. 

Many thanks for reporting this to us!

Best regards,

Debbie, on behalf of the ESASky team

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