Your comments

Thanks Becky, these are actually two requests in one.  ;)

I have added both user stories to our backlog and you will be notified when they are available in the operational version.

Thanks Andrew, we have added your suggestion to our backlog. It will be prioritized according to the number of "likes" in this platform plus other technical considerations.

Thanks Belén, those use cases make sense indeed. I have added them to the backlog and will be prioritized according to the likes to this request and other criteria.

Thanks Belén, but this would benefit from a bit more specific user story: what does the user wants to do with a selected region in the sky? visualize it? limit the queries to it? or download all data from it?

Thanks Belén. Good suggestion too. Added to the backlog.

Thanks Belén. Indeed, this request has come already often. I have added it to our backlog.

Thanks Andy!

That is easy enough to fix. We will make these modifications and let you know when they are done.

That exists already: we have an astroquery module in astropy that allows you to do exactly that already. See the documentation here:


https://www.cosmos.esa.int/web/esdc/esasky-astroquery-module


and a couple of video tutorials here:


https://www.cosmos.esa.int/web/esdc/esasky-how-to

Thanks Pedro!

Understood, certainly a cool use-case. We will let you know when it goes into out planning..

Cheers,

Bruno

Dear Pedro,


Thanks for the suggestions. We can include them as sub-user-stories for the future feature to allow users to upload their custom Fields of View for observation planning. I would like to understand the flipping though.. what is the usecase there? You have a definition of the instrument but not as projected in the sky?


Thanks, we will keep you posted.


Bruno

On behalf of the ESDC