Astroquery: shrinking box size towards the celestial poles?

Created on 4 Apr 2018  路  1Comment  路  Source: astropy/astroquery

https://github.com/astropy/astroquery/blob/ac719ee24bdf5b66bd93b84100f13a7099c0d1f7/astroquery/sdss/core.py#L1009

I think using "(ra - dr / cos_dec, ra + dr / cos_dec, ..." is better. Otherwise the actual box size will shrink towards the celestial poles. Also, adding boundary detection near RA~0/360 might be helpful.

I've been using astroquery for a while, which helped a lot in my research. Thanks anyway!

bug sdss

Most helpful comment

Actually it would be good to get rid of this workaround and use what sdss does with their radius search:

SELECT  TOP 10 p.objid,
   p.run, p.rerun, p.camcol, p.field, p.obj,
   p.type, p.ra, p.dec, p.u,p.g,p.r,p.i,p.z,
   p.Err_u, p.Err_g, p.Err_r,p.Err_i,p.Err_z
   FROM fGetNearbyObjEq(258.25,64.05,3) n,   PhotoPrimary p
   WHERE n.objID=p.objID 

alternatively define a dr_ra and dr_dec separately and use that one.

>All comments

Actually it would be good to get rid of this workaround and use what sdss does with their radius search:

SELECT  TOP 10 p.objid,
   p.run, p.rerun, p.camcol, p.field, p.obj,
   p.type, p.ra, p.dec, p.u,p.g,p.r,p.i,p.z,
   p.Err_u, p.Err_g, p.Err_r,p.Err_i,p.Err_z
   FROM fGetNearbyObjEq(258.25,64.05,3) n,   PhotoPrimary p
   WHERE n.objID=p.objID 

alternatively define a dr_ra and dr_dec separately and use that one.

Was this page helpful?
0 / 5 - 0 ratings