ESASky User Forum / Whiteboard
Welcome to the ESASky user forum! The aim of this forum is to have a place to collect feature requests from users, allow conversations between users and gauge the Astronomy community's priorities related to the ESASky application. We welcome requests for the ESASky, its documentation, its ways of interacting with the community, and any functionality which you think would be widely useful to the Astronomy community.
Please suggest and vote on feature requests below. Before adding a new suggestion, use the search function to see if the idea has already been posted. Please include links to relevant repositories and existing issues in the description of the feature request. Also consider including links to code or images demonstrating the requested functionality.
You can also use this forum to report bugs or request small improvements to existing functionality.
Other places to get help and communicate with the ESASky team are:
- @ESAESDC on Twitter
- The ESASky newsletter
- The team's info email address (esaskyinfo at sciops.esa.int)
- The ESASky helpdesk (requires registration)
The ESASky Project is dedicated to maintaining a positive, inclusive, successful, and growing community. Please observe the usual basic internet citizen rules before posting to this forum.
Make this Userecho more easy to find, should be possible to click it from the main panel
Users that want to comment something do not find how to do it
Allow decimal format of coodinate
is it possible also to show decimal format of coodinate, which is much more convenient in some cases?
Right ascension format
The right ascension of Gaia DR1 2067784619950643072 == Cyg OB2-8A, for example, is shown as 20h 33' 15.07". It should be 20h 33m 15.07s. The declination coordinate is not wrong but would look better, if this were possible, with a degree symbol rather than "d".
Are there plans for an API for ESASky?
this would allow programmatic access to the tool & the data, for example to use ESASky inside a jupyter notebook.
https://www.cosmos.esa.int/web/esdc/esasky-astroquery-module
and a couple of video tutorials here:
Allow magnitude filtering in catalogues
It would be great to have filtering capability over the catalog results. In particular over the magnitude fields but it could be also useful to other fields. This would make ESASky much more useful at for example preparing observations...
Dear Pedro,
We are pleased to announced that the filtering functionality is already available in ESASky v2.0: which has been released today at http://sky.esa.int.
Best regards,
Bruno Merín
On behalf of the ESAC Science Data Centre
Data panel usability: Allow selecting unique catalogues and/or Imaging observation more easily
In the data panel when you are interested in only one source or image catalog you need to one by one deselect the others. I think it should be the other way around or having a button to deselect all of them, so you can select only one more easily. Other option would be to double-clicking to select only one...
I think this is cheap to implement and would greatly improve the usability of the data panel.
Dear Pedro,
We are glad to announce that the functionality you requested is already available in ESASky version 2.0, which has been released today.
Enjoy filtering!
Best regards,
Bruno Merin
On behalf of the ESAC Science Data Centre
export the output of an esasky session as a table or a ascii file
would it be possible to export the output of an esasky session as a table or a ascii file, in addition to the screeenshot?
Inaccuracy in the description of the positional error in the Chandra catalogue.
In the description of the Chandra catalogue, the column related to the positional error is defined as
Position error radius at 95% confidence level // arcsec // Position error 95% confidence level circle radius (column also called err_ellipse_r0)
While in the Chandra web page, err_ellipse_r0 is said to be something different
Three of the parameters specifying the geometry of each error ellipse are the semi-major and semi-minor radii (/err_ellipse_r0/, /err_ellipse_r1/), and the position angle θ that the major axis of the ellipse makes with respect to the tangent plane /y/ axis (/err_ellipse_ang/).
What is not actually the same. The difference can be specially relevant when cross matching several set of catalogues/source lists at once.
Dear Ricardo,
We are happy to report that the problem you reported has been fixed in version 2.0 of the ESASky application: http://sky.esa.int
Enjoy!
Bruno
on behalf of the ESASky team
Auto-import of gamma-ray bursts or other transient events
The Gamma-ray Coordinates Network (GCN) or Transient Astronomy Network (TAN) distributes information about gamma-ray bursts or other transient events in (near-real) time via different services, including VOEvents.
This is an idea for the longer term.
Customer support service by UserEcho
