Dear Becky,

Great feedback, we've added it to our backlog and will let you know when it's implemented!

Regards,

Deborah, on behalf of the ESASky team

Dear Anthony,

Thanks for the feedback. We're looking into this (it's a complicated set up to test!) and will get back to you after the holiday period.

Kind regards,

Deborah, on behalf of the ESASky team

Dear Pedro,

Would you for example like to be able to minimise and maximise the menu of icons? Please send a screenshot of the issue if I haven't understood it correctly.

Kind regards,

Deborah, on behalf of the ESASky team

Dear Pedro,

Many thanks for feedback. We've had similar requests to add a scale and / or a grid and we'll therefor increase the priority of this in our backlog.

If I understand correctly your last sentence, you can take a screenshot of ESASky using the screenshot icon, which removes the menus and data panels but keeps the footprints / sources / background image etc.

Kind regards,

Deborah, on behalf of the ESASky team

Dear Pedro,

Many thanks, we'll add your suggestion to our backlog!

Kind regards,

Deborah

Dear Pedro,

Before we add any new ESA mission data we consult and validate with the mission. In the case of the Gaia catalogue, it was decided by the Gaia mission that the best approach is to provide the coordinates in the same epoch as the catalogue: exactly the same as what is provided by the ESA Gaia archive. The issue here is that not everything in ESASky is in epoch 2000. The background images (HiPS) are in the epoch of the observations. The same with most catalogues. You can move these images to J2000 only if you know the proper motions and these are known only to Hipparcos and Gaia objects. Also there are a few hundred million Gaia DR2 sources which do not have proper motions therefore we cannot propagate them to epoch 2000 and we have the problem of either not showing them on the sky or mixing sources on the sky from the Gaia catalogue with epoch 2015.5 and epoch 2000. 

In most cases the proper motions in the epoch range 2000 to 2015.5 are so small that this is not relevant (you can see this by having to zoom in on an object until a solid line appears). The dotted lines are showing a representation of the proper motion but do *not* represent the precise movement. Please see the lower part of this section for more information: https://www.cosmos.esa.int/web/esdc/esasky-interface#datapanel

If you are looking in a region with sources of high proper motion, the Gaia archive provides detailed information on how to propagate the coordinates to your desired epoch (under section ADQL syntax -> Epoch Propagation): http://gea.esac.esa.int/archive-help/index.html

I hope this all helps and answers your questions.

Kind regards,

Deborah, on behalf of the ESASky team

Dear Nora,

Thank you for the feedback. We are working on automatically updating the HiPS and MOCS for all missions in operation. Once this is completed, ESASky will always have the updated MOCS.

We will let you know when this is impletmented.

Kind regards,

Debbie

Dear Becky,

ESASky and the XMM-Newton Science Archive use the name resolver from SIMBAD, CDS, to find astronomical sources. If the source is not in SIMBAD, the tools will not be able to find it. As you said, this source indeed is not in SIMBAD. As a work around, these types of sources have the coordinates in their name, I'd suggest searching for the source taking the numbers from the name '215022.4–055108' and searching for the source by coordinates: 21 50 22.4 -05 51 08
The source can then be identified in ESASky by loading the XMM-Newton 3XMM EPIC and Chandra CSC1.1 catalogues.

The ESDC are working on solutions to allow users to search for objects that are in ESA catalogues, we hope to add this functionality to ESASky and our archives soon.

Kind regards,

Deborah

Hi,

Many thanks for your feedback. We've tested this with Ubuntu 16.04 and Firefox 61.0 and it's working. Can you try again after hard refreshing your browser and let us know.

Many thanks,

Debbie, on behalf of the ESASky team

Dear John,

Many thanks for the request, it's useful functionality to add therefore we've added it to our backlog. We will let you know once this has been implemented.

Kind regards,

Debbie, on behalf of the ESASky team