@@ -45,10 +45,11 @@ If you know the names of all the available maps missions you can use
4545 Query an object
4646---------------
4747
48- There are two query objects methods in this module :meth: `~query_object_catalogs `
49- and :meth: `~query_object_maps `. They both work in almost the same way except
50- that one has catalogs as input and output and the other one has mission
51- names and observations as input and output.
48+ There are two query objects methods in this module
49+ :meth: `~astroquery.esasky.ESASkyClass.query_object_catalogs ` and
50+ :meth: `~astroquery.esasky.ESASkyClass.query_object_maps `. They both work in
51+ almost the same way except that one has catalogs as input and output and the
52+ other one has mission names and observations as input and output.
5253
5354For catalogs, the query returns a maximum of 2000 sources per mission.
5455To account for observation errors, this method will search for any sources
@@ -112,9 +113,9 @@ dictionary:
112113 ... # table is now an `astropy.table.Table` object
113114 ... # some code to apply on table
114115
115- As mentioned earlier, :meth: `query_object_maps ` works extremely similar. It will
116- return all maps that contain the chosen object or coordinate.
117- To execute the same command as above you write this:
116+ As mentioned earlier, :meth: `astroquery.esasky.ESASkyClass. query_object_maps `
117+ works extremely similar. It will return all maps that contain the chosen object
118+ or coordinate. To execute the same command as above you write this:
118119
119120.. code-block :: python
120121
0 commit comments