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

I love the high res DSS but is there a way to add my scopes FOV for imaging various targets? I find so many interesting areas but have no idea of size in my frame.  I'm sure MANY would love to see their frame FOV over possible future targets. 

https://www.facebook.com/Ron.R.Kramer/

An attempt to upload the target list (one-column ASCII with pulsar names from the ATNF catalog; 2000+ entries like PSR J0002+6216) does not seem to work with the following error "Upload of file ATNF_psr_names.txt failed due to [HTTP_ERROR]: Unsuccessful server response code of: 503".

Geat tool! Improved by a lot lately. However, these would make it even more useful:

1. Being able to adjust the contrast and brightness in of the images in an easy way

2. Allow for Gaussian smoothing of the displayed part of the image

2. Overlay multiwavelength images with different transparency and coloring options.

3. Adding images from new optical/NIR surveys (DEC, PanStarrs, VPHAS+,...)

4. Scale bar (in the angular distance units) in the bottom corner

5. The obvious way to display Simbad objects. Currently, this sort of can be done by clicking "Explore publications..." but this does not look the same as Simbad button to click on

Oleg Kargaltsev

Sometimes HST Images appear as double images. Not sure if they are two images with different WCS or the same image repeated.

For example see HST ACS at 10:01:20.78 +55:53:49

Screenshot attached

I wanted to visualize publications in several sources from a target list so I clicked on the publications toggle button and then started the spiral galaxies target list but when I moved from one galaxy to the next,the publications would only display if I click twice on the publications button in each field. This obviously limits a lot the exploration of data that I can do and I understand it is not the way the toggle button should work. Am I doing something wrong?

Hi,

If I rescale the size of the web browser window (without zooming in/out), I would expect the FOV value in the top left corner to change since I am viewing a different portion of the sky, but this is not the case. So, it is not readily obvious what this FOV value corresponds to. Perhaps being able to toggle on/off a circle with diameter equal to the FOV value would be easy to implement.

Thanks

Reproduce:

• Optical - DSS2 color - change Color Pallete from Native to Greyscale

Expected result: Greyscale equivalent of the current, color image image

Actual result: White screen

If that's a feature, not a bug, I'd recommend changing Color Pallete drop-down to gray-out options which do not have any actual data in them.

Right now there's an option to import targets list. It has no documented format, which is a big issue for random newcomers that would like to use this feature. It'd be great to export one of the existing target lists as an example and to use as a base for custom lists.