@@ -10,10 +10,13 @@ Getting started
10
10
===============
11
11
12
12
This is a python interface for querying the `ESASky web service
13
- <http://www.cosmos.esa.int/web/esdc/esasky> `__. This supports querying an object
14
- as well as querying a region around the target. For region queries, the region
15
- dimensions may be specified as a radius. The queries may be further constrained
16
- by specifying a choice of catalogs, missions, or spectra. `Documentation on the ESASky
13
+ <http://www.cosmos.esa.int/web/esdc/esasky> `__. This module supports cone
14
+ searches and download of data products from all missions available in ESASky.
15
+ You can also use the ESASky Solar System Object crossmatch methods to get
16
+ all observations (both targeted and serendipitous) of a solar system object.
17
+
18
+ There are 4 categories of methods, based on the type of data:
19
+ catalogs, observations, spectra, and SSO. `Documentation on the ESASky
17
20
web service can be found here. <http://www.cosmos.esa.int/web/esdc/esasky-help> `__
18
21
19
22
Get the available catalog names
@@ -49,7 +52,7 @@ If you know the names of all the available maps missions you can use
49
52
' XMM-OM-UV' , ' HST-UV' , ' HST-OPTICAL' , ' HST-IR' , ' ISO-IR' ,
50
53
' Herschel' , ' AKARI' , ' Spitzer' , ' ALMA' ]
51
54
52
- Get the available maps mission names
55
+ Get the available spectra mission names
53
56
------------------------------------
54
57
55
58
If you know the names of all the available spectra you can use
@@ -62,14 +65,29 @@ If you know the names of all the available spectra you can use
62
65
[' XMM-NEWTON' , ' Chandra' , ' IUE' , ' HST-UV' ,
63
66
' HST-OPTICAL' , ' HST-IR' , ' ISO-IR' , ' Herschel' , ' LAMOST' ]
64
67
68
+ Get the available SSO mission names
69
+ ------------------------------------
70
+
71
+ If you know the names of all the available missions with SSO cross
72
+ match data, you can use
73
+ :meth: `~astroquery.esasky.ESASkyClass.list_sso `:
74
+
75
+ .. code-block :: python
76
+
77
+ >> > sso_list = ESASky.list_sso()
78
+ >> > print (sso_list)
79
+ [' Herschel' , ' HST' , ' XMM' ]
80
+
65
81
Query an object
66
82
---------------
67
83
68
- There are three query objects methods in this module
84
+ There are three very similar query objects methods in this module
69
85
:meth: `~astroquery.esasky.ESASkyClass.query_object_catalogs `,
70
86
:meth: `~astroquery.esasky.ESASkyClass.query_object_maps `, and
71
- :meth: `~astroquery.esasky.ESASkyClass.query_object_spectra `, which all work in
72
- almost the same way.
87
+ :meth: `~astroquery.esasky.ESASkyClass.query_object_spectra `.
88
+ There is also a method for querying SSO object
89
+ :meth: `~astroquery.esasky.ESASkyClass.query_sso_maps `
90
+ which is covered in its own section further down.
73
91
74
92
For catalogs, the query returns a maximum of 10000 sources per mission by
75
93
default. However, this can be modified by the row_limit parameter.
355
373
... missions = [' Herschel' , ' XMM-NEWTON' ])
356
374
>> > spectra = ESASky.get_spectra_from_table(query_table_list = table_list, download_dir = " /home/user/esasky" )
357
375
358
- The response is structured in a dictionary like this:
376
+ The return value is structured in a dictionary like this:
359
377
360
378
.. code-block :: python
361
379
@@ -380,6 +398,97 @@ Here is another example for Herschel, since it is a bit special:
380
398
>> > spectra[' HERSCHEL' ][' 1342211195' ][' red' ].keys()
381
399
>> > spectra[' HERSCHEL' ][' 1342211195' ][' red' ][' HPSTBRRS' ].info()
382
400
401
+ Solar System Object Crossmatch
402
+ ------------------------------
403
+ ESASky has a solar system object crossmatch feature which
404
+ performs a crossmatch on the SSO orbits against the entire
405
+ mission archives to find observations in which the SSO fell
406
+ within the imaging instrument' s field of view during the
407
+ time the images were being taken.
408
+ `Read more about the ESASky SSO feature
409
+ < https:// www.cosmos.esa.int/ web/ esdc/ esasky- interface# SSO>`__
410
+ You can access the results of this crossmatch by using
411
+ :meth:`astroquery.esasky.ESASkyClass.query_sso_maps` which
412
+ works like the other query methods, but it takes an SSO
413
+ name as input instead of a position.
414
+
415
+ .. code- block:: python
416
+
417
+ >> > from astroquery.esasky import ESASky
418
+ >> > result = ESASky.query_sso_maps(sso_name = " Pallas" , missions = [" XMM" , " HST" ])
419
+
420
+ In some cases an SSO name is ambiguous, in which case you
421
+ may need to use a more precise SSO name or specify the
422
+ SSO type of the desired object . For example:
423
+
424
+ .. code- block:: python
425
+
426
+ >> > from astroquery.esasky import ESASky
427
+ >> > ESASky.query_sso_maps(sso_name = " 503" )
428
+ INFO : Found 4 SSO ' s with name: 503.
429
+ Try narrowing your search by typing a more specific sso_name.
430
+ You can also narrow your search by specifying the sso_type.
431
+ Allowed values are ALL , ASTEROID , COMET , SATELLITE , PLANET , DWARF_PLANET , SPACECRAFT , SPACEJUNK , EXOPLANET , STAR .
432
+ The following SSO ' s were found:
433
+ {' aliases' : [' 503' , ' J-3' , ' J-III' ], ' sso_name' : ' Ganymede' , ' sso_type' : ' SATELLITE' }
434
+ {' aliases' : [], ' sso_name' : ' TOI-503 b' , ' sso_type' : ' EXOPLANET' }
435
+ {' aliases' : [], ' sso_name' : ' Wolf 503 b' , ' sso_type' : ' EXOPLANET' }
436
+ {' aliases' : [' 00503' , ' 1899 GA' , ' 1903 BL' , ' 1948 BA' , ' 1948 DA' , ' 2000503' , ' 503' , ' I99G00A' , ' J03B00L' , ' J48B00A' , ' J48D00A' ], ' sso_name' : ' Evelyn' , ' sso_type' : ' ASTEROID' }
437
+
438
+
439
+ In this case, you can specify the sso_type
440
+
441
+ .. code- block:: python
442
+ >> > from astroquery.esasky import ESASky
443
+ >> > ESASky.query_sso_maps(sso_name = " 503" , sso_type = " SATELLITE" )
444
+
445
+
446
+ You can see the available missions with :
447
+
448
+ .. code- block:: python
449
+ >> > from astroquery.esasky import ESASky
450
+ >> > ESASky.list_sso()
451
+
452
+
453
+ Other parameters and the return value are structured in the
454
+ same manner as the other query methods.
455
+
456
+ You can also download the observation for a given SSO with
457
+ :meth:`astroquery.esasky.ESASkyClass.get_images_sso` .
458
+ This function works very similar to
459
+ :meth:`astroquery.esasky.ESASkyClass.get_images` and
460
+ :meth:`astroquery.esasky.ESASkyClass.get_maps` , as it
461
+ structures the return values in the same way, and
462
+ most parameters are the same.
463
+ You can for example, download a table list just like
464
+ in get_maps by doing something like this:
465
+
466
+ .. code- block:: python
467
+ >> > from astroquery.esasky import ESASky
468
+ >> > table_list_from_query_maps=ESASky.query_sso_maps(sso_name = " ganymede" , missions = " XMM" )
469
+ >> > table_list_from_query_maps[' XMM' ].remove_rows(list (range (0 , 32 )))
470
+ >> > images=ESASky.get_images_sso(table_list = table_list_from_query_maps)
471
+
472
+ Or download everything on an SSO by something like this:
473
+
474
+ .. code- block:: python
475
+ >> > from astroquery.esasky import ESASky
476
+ >> > images=ESASky.get_images(sso_name = " ganymede" )
477
+
478
+
479
+ This module also offers access to IMCCE ' s SsODNet resolver,
480
+ which allows you to find solar and extra solar system
481
+ objects with a given name. Here you can see all matches
482
+ and there aliases and types. You can use this method to
483
+ help you specify which SSO you are after. Use
484
+ :meth:`astroquery.esasky.ESASkyClass.find_sso`
485
+ like this:
486
+
487
+ .. code- block:: python
488
+ >> > from astroquery.esasky import ESASky
489
+ >> > list_of_matches=ESASky.find_sso(sso_name = " Io" )
490
+
491
+
383
492
Reference/ API
384
493
============ =
385
494
0 commit comments