The GaiaDR2 Source Names are so long that all my programs can only deal with them as strings. In ESASky 3.4 they were displayed correctly in full length in the calatog window but not on the popup when clicking on a star. Now with the updated version the correct name is neither shown in the catalog view nor in the pop window. The Name in the catalog window has nothing to do with the source name. Where can I find to correct Gaia names? As an example my target GaiaDR2 0530685166960018816 is shown in the popup as 530685166960018800 and in the catalog as 3 704 192. What does that number even mean?

Typing RA as 14.4 and 014.4 sends user to two very different placess on the sky. EsaSky correctly interprets 014.4 and incorrectly 14.4. Obviously, most people (all?) will not type 014.4 but will type it as 14.4. Also, most catalogs have coordinates this way!  This will lead to countless and serious mistakes by students and also researchers.

It seems that this has been a problem for >6 months (at least it was reported that long ago). If this is not possible to fix, for some reason, a BIG WARNING MESSAGE IN RED needs to be placed on top of the main EsaSky page to prevent users from making many frustrating mistakes.

Thank you,

Oleg Kargaltsev

I'm new to the website, having used the CDS/Aladin database before, and I tried copying and pasting the designation of a quasar from SIMBAD in order to look to any evidence of it using sub-millimetre and other wavelengths on ESASky. I can copy from SIMBAD/CDS, but the software in ESASky doesn't seem to allow pasting a target name in the search window. Is it just me making a mistake, or is there a limitation in the system? Thanks in advance for any help, Phil Rushton

Hi Guys.

I have been trying to figure out if it is possible to supply a MOC as an python object or a FITS file and plot it in the pyesasky display?

So far I have not had luck with it, perhaps I am looking the wrong places.

If this is not possible yet I would encourage that as method to develop, and perhaps also add one allowing for basic overlap checking with the built-in MOCs.

cheers

Jonas 

It would be great whether ESASky would allow to search by Target Of Interest ID from the Kepler and TESS missions.

We got a question about an interesting object in this image in asteroidhunter.org:

https://www.zooniverse.org/projects/sandorkruk/hubble-asteroid-hunter/talk/2451/1355798?comment=2210409&page=1

When I went with  ESASky to the region to visualise the observation and plot the objects for which there are publications, I discovered that the ACS HiPS background image does not show anything in the position of that observation. Then I realise that it is an observation from 2016 and the HST HiPS were done in August 2015. But then this means that we are now close to five years outdated in these HiPS. Is there a way to re-create them with all the public observations from August 2015 until 2019?

Is it possible to upload one's own FITS image with a WCS? For the JWST planning stuff most of the sky surveys are not deep enough

Example: Betelgeuse ISO observation 692019800 links to 

http://archives.esac.esa.int/ida/aio/jsp/createPostcards.jsp?obsno=6920198

Which does not exist

If you manually add a 0 to the URL it works:

http://archives.esac.esa.int/ida/aio/jsp/createPostcards.jsp?obsno=69201980

Please add https to the site, otherwise it is easily susceptible to MITM attacks.

As requested by Twitter user @Todd_Scheve, it would be great to have the catalogue names of stars and/or objects in the images on hover. Probably this would require some sort of toggle to activate or deactivate it depending on the user workflow..