Log-in to SkyMapper

By using this forum, you agree to abide by the Skymapper Online Discussion Forum Disclaimer and Terms of Use.


crossmatch dr1p1_fs_photometry table with a list of known targets

crossmatch dr1p1_fs_photometry table with a list of known targets  

  By: Ming Yang on May 17, 2018, 4:18 a.m.

First post~ I'm just wondering is there any way to crossmatch dr1p1_fs_photometry table with a list of known targets? I have a list of ~20,000 targets which needs time-series data. However, the upload option is unavailable for SkyMapper TAP service. I cannot download all time-series data for the whole region (~100 deg^2). Many thanks!

Re: crossmatch dr1p1_fs_photometry table with a list of known targets  

  By: Christopher Onken on June 12, 2018, 4:46 p.m.

[Edited March 2019 to reflect updated URLs]

The best way to currently match a large list of objects against any SkyMapper table is to use TOPCAT's Multicone join feature. First, load your list into TOPCAT, then open the Joins->Multicone menu. Place the following into the Cone Search URL:

  • http://skymapper.anu.edu.au/sm-cone/public/query?CATALOG=dr1.fs_photometry

Then specify the RA and Dec columns from your own table, select a fairly small search radius to avoid contamination (2-3", unless your sources have large proper motions), and hit 'Go'.

Alternatively, you can script up a set of 'wget' commands to the URL above. For example, to get the closest SkyMapper detections within 2" matched to your targets and place the outputs into separate CSV files, you could do something like the following, using one of your RA, Dec positions for each line:

  • wget -q -O - "http://skymapper.anu.edu.au/sm-cone/public/query?CATALOG=dr1.fs_photometry&RA=100.1&DEC=-31.1&SR=0.000556&RESPONSEFORMAT=CSV" > series1.csv
  • wget -q -O - "http://skymapper.anu.edu.au/sm-cone/public/query?CATALOG=dr1.fs_photometry&RA=100.2&DEC=-32.2&SR=0.000556&RESPONSEFORMAT=CSV" > series2.csv

...

(Note that the outputs won't be time-ordered, but you can do that using each row's image_id, which is very nearly the UTC date-time of the observation: YYYYMMDDHHMMSS.)

Cheers,

Christopher Onken

SkyMapper Team

 Last edited by: Christopher Onken on March 25, 2019, 1:41 p.m., edited 2 times in total.