This is in part motivated by the discussion in astropy/astropy#733 . There was (and is) a discussion there about whether or not Galactic extinction should be included in the astropy core vs. astroquery.
Regardless of what goes in the core, it is clear that quite a few different online queryable source exist for all-sky or large-field dust maps, either in E(B-V) form or as dust columns or the like. Some possible examples include
So this issue calls for creating an interface that might allow various sources like this to be queried and return the same/similar type of object. That is, it would be really nice to be able to just do something like:
ebmv1 = query_ebmv(coordinates, 'SFD')
ebmv2 = query_ebmv(coordinates, 'ogle-vvv')
and have ebmv1 and ebmv2 be exactly comparable.
(of course it should match the general API plan for astroquery, but the result object should be something consistent across the disperate tools.)
This is in part motivated by the discussion in astropy/astropy#733 . There was (and is) a discussion there about whether or not Galactic extinction should be included in the astropy core vs. astroquery.
Regardless of what goes in the core, it is clear that quite a few different online queryable source exist for all-sky or large-field dust maps, either in E(B-V) form or as dust columns or the like. Some possible examples include
So this issue calls for creating an interface that might allow various sources like this to be queried and return the same/similar type of object. That is, it would be really nice to be able to just do something like:
and have
ebmv1andebmv2be exactly comparable.(of course it should match the general API plan for astroquery, but the result object should be something consistent across the disperate tools.)