You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm planning to build modules for the following services: Minor Planet Center: astroquery.mpc JPL Solar System Dynamics tools: astroquery.jpl Solar System Object Search: astroquery.ssos IMCCE: astroquery.imcce
I note that the API asks modules to have a get_images(); astroquery.ssos will provide that, but the other services are purely ephemerides and orbital elements providers, they do not link to image catalogues.
SSOS currently provides a VOTable return option, IMCCE provides full VO interaction, the other two provide only webpages that would have to be scraped and parsed.
OK, this sounds great. At .astronomy, we had a lot of success using the Fermi tool as an approximate template because it's fairly simple. I'm working on generating a "template module" module to assist in development, but it's not quite ready yet - I'll inform you once I've done that, and you can use it as a starting point.
get_images is certainly only needed for image services. query_object probably ought to query solar system objects by name rather than by coordinates, but perhaps it would make sense to have a query_orbital_elements to search based on, e.g., eccentricity, orbital major axis, or some other parameter that is likely to be catalogued (accurately?).
In terms of the non-VOTable return, that's OK, it just means we'll need to put some extra effort in to finding an astropy table parser that matches the return type from that service.
Activity
keflavich commentedon Sep 20, 2013
OK, this sounds great. At .astronomy, we had a lot of success using the Fermi tool as an approximate template because it's fairly simple. I'm working on generating a "template module" module to assist in development, but it's not quite ready yet - I'll inform you once I've done that, and you can use it as a starting point.
get_imagesis certainly only needed for image services.query_objectprobably ought to query solar system objects by name rather than by coordinates, but perhaps it would make sense to have aquery_orbital_elementsto search based on, e.g., eccentricity, orbital major axis, or some other parameter that is likely to be catalogued (accurately?).In terms of the non-VOTable return, that's OK, it just means we'll need to put some extra effort in to finding an astropy table parser that matches the return type from that service.
here come the modules according to the proposal in astropy#222
here come the modules according to the proposal in astropy#222
bsipocz commentedon Nov 4, 2021
These modules have been added to astroquery for a while as part of the sbpy efforts.