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..

I am having issues querying ESASky through astroquery. When following the examples here, running the following three lines yieldsa Table Parse Error (below). 

>>> from astroquery.esasky import ESASky
>>> import astropy.units as u
>>> result = ESASky.query_region_catalogs("M51", 10 * u.arcmin, "integral")

This seems to happens with different catalogs. Has anyone encountered this issue before?

Thanks a lot!

---------------------------------------------------------------------------
IndexError Traceback (most recent call last)
~/opt/anaconda3/lib/python3.7/site-packages/astroquery/esasky/core.py in _parse_xml_table(self, response)
861 vo_table = votable.parse(tf, pedantic=False)
--> 862 first_table = vo_table.get_first_table()
863 table = first_table.to_table(use_names_over_ids=True)

~/opt/anaconda3/lib/python3.7/site-packages/astropy/io/votable/tree.py in get_first_table(self)
3492 return table
-> 3493 raise IndexError("No table found in VOTABLE file.")
3494

IndexError: No table found in VOTABLE file.

During handling of the above exception, another exception occurred:

TableParseError Traceback (most recent call last)
in
1 from astroquery.esasky import ESASky
2 import astropy.units as u
----> 3 result = ESASky.query_region_catalogs("M51", 10 * u.arcmin, "integral")

~/opt/anaconda3/lib/python3.7/site-packages/astroquery/esasky/core.py in query_region_catalogs(self, position, radius, catalogs, row_limit, get_query_payload, cache)
303 coordinates, sanitized_radius,
304 sanitized_row_limit,
--> 305 get_query_payload, cache)
306
307 if (get_query_payload):

~/opt/anaconda3/lib/python3.7/site-packages/astroquery/esasky/core.py in _store_query_result_catalogs(self, query_result, catalogs, coordinates, radius, row_limit, get_query_payload, cache)
767 catalog_table = self._query_region_catalog(coordinates, radius,
768 catalog, row_limit,
--> 769 get_query_payload, cache)
770 if (len(catalog_table) > 0):
771 query_result[catalog.upper()] = catalog_table

~/opt/anaconda3/lib/python3.7/site-packages/astroquery/esasky/core.py in _query_region_catalog(self, coordinates, radius, catalog_name, row_limit, get_query_payload, cache)
688 if (get_query_payload):
689 return request_payload
--> 690 return self._get_and_parse_from_tap(request_payload, cache)
691
692 def _build_observation_query(self, coordinates, radius, json):

~/opt/anaconda3/lib/python3.7/site-packages/astroquery/esasky/core.py in _get_and_parse_from_tap(self, request_payload, cache)
843 def _get_and_parse_from_tap(self, request_payload, cache):
844 response = self._send_get_request("/tap/sync", request_payload, cache)
--> 845 return self._parse_xml_table(response)
846
847 def _send_get_request(self, url_extension, request_payload, cache):

~/opt/anaconda3/lib/python3.7/site-packages/astroquery/esasky/core.py in _parse_xml_table(self, response)
867 self.table_parse_error = ex
868 raise TableParseError(
--> 869 "Failed to parse ESASky VOTABLE result! The raw response can be "
870 "found in self.response, and the error in "
871 "self.table_parse_error.")

TableParseError: Failed to parse ESASky VOTABLE result! The raw response can be found in self.response, and the error in self.table_parse_error.

EsaSky is getting better and better! Great job!

Suggested additions:

1. Swift XRT and UVOT images

2. Toggle on/off Galactic/Equatorial coordinate grid

3. Ability to change the view in the webpage so that Galactic equator is horizontal

4. Show not only equatorial but also Galactic coordinates of the crosshair in the corner

Oleg Kargaltsev