When having a catalog active and you update the FOV, the "Sources in chosen area" tag that displays the number of observations in the current area hides the catalog source that is currently selected with is a little annoying.

I use EsaSky (among others) to prepare ground-based observations. At Phase II you can provided a finding chart for the resident astronomer to use. The usually ask for the N and E direction and the scale.

The scale could be ala Google maps in with you represent 1 arcdeg, 1 arcmin, 1 arcsec depending on the scale you have selected.

N and E directions should be particularly useful if a previous ticket, regarding FoV rotation and inversion is implemented.

The capability of generating a finding chart without menus, etc would be also extremely useful.

The feature of having an URL is great, you copy Google maps here :-). It would be even greater if a shortener version  (e.g. goo.gl) is provided

GAIA DR2  coordinates  epoch is 2015.5 which is the native one provided by GAIA. It would be useful to provide in more usual J2000.0 or at least in addition with 2015.5

The current form can be misleading. For example you could be preparing an observation and by error assume that the coordinates are in J2000.0, the error is substancial.

If you go to sky.esa.int/?action=goto&target=246.80577685364196%20-24.517894672834654&hips=AllWISE%20color&fov=6.616839145259243&cooframe=J2000 and try to show the Gaia DR2 catalogue, the query never ends..

A user is requesting  XMM-Newton MOCs, as the ones provided for Chandra (http://cxc.harvard.edu/cda/cda_moc.html) it would be good to have them updated and easily accesible.

We could provide the fits files also from the XSA web page

I cannot find source 3XMM J215022.4–055108, which is the topic of a recent nature paper about a black hole hosting stellar cluster: https://www.nature.com/articles/s41550-018-0493-1

Being this an XMM-Newton source probably from the 3XMM catalogue, shouldn't it be possible to find it directly by name in ESASky? I cannot find in SIMBAD nor in the XMM archive..

Hi ESASky team,

I think it would be extremely useful to give the user the possibility to hide the central crosshair from the FOV. That would simplify a lot using RGB images from ESAsky.

Thank you very much,

Alejandro Borlaff

The interface only supports string equality. Please add numerical comparison operators.

I am playing around a little bit with Jupyter notebooks, and I was wondering whether would it be a good idea to implement something in python or any other  programming languaje, that allows to send a request to ESASky in order to perform a crossmatch between a determined resultset, provided by the user, and the observations made by a specific science mission for that same area. 

For example, imagine that I am a user that wants to perform a study about x-ray objects. I have a resulset produced by the data retrieved from XSA TAP service and reduced following a determined critera that will help me to find ... ????. 

Now I want to cross my results with the observations made by Chandra mission, for that same area of interest, with a determined filtering, a specific background map and any other aditional flag like for example the publications available for the sources contained in that area, and finally,  display those results in ESASky. 

This would it be reasonable or useful from the user point of view? 

Furthemore, that service could be useful for the rest of the archives. For example, going back to X-rays example. If a  XSA user mades a filtering of data and now, from the XSA interface, we wants to cross those results with Chandra and display them in ESASky. Perhaps, could it be possible to send a json file to ESASky with all the information that it needs to do this and display the results in ESASky.

Does this make sense?