/usr/share/doc/stilts/sun256/tapskymatch.html is in stilts-doc 3.1.2-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>tapskymatch:
Crossmatches table on sky position against TAP table
</title>
</head>
<body>
<hr>
<a href="tapskymatch-usage.html">Next</a> <a href="secB.22.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="tapskymatch-usage.html">Usage</a><br>
<b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
<b>Previous: </b><a href="secB.22.2.html">Examples</a><br>
<hr>
<hr>
<h2><a name="tapskymatch">B.23 <code>tapskymatch</code>:
Crossmatches table on sky position against TAP table</a></h2>
<p><code>tapskymatch</code> allows you to perform a positional crossmatch
of a local table with one held in a remote TAP service, as long as
that TAP supports upload queries.
This task does three main jobs.
First, it prepares the ADQL queries and TAP negotiations for you
so that you don't need to remember the syntax for performing
positional crossmatches against a TAP service.
Second, it organises data transfer so that only those columns
required (basically the positional ones) are transmitted to and
from the service, to save on bandwidth.
And third it divides the job up into chunks,
so that the TAP service only has to perform a manageable-sized
query at a time.
If the job is large this chunking can be useful to monitor
progress of the job,
and it also allows you to perform a match which would otherwise
hit the upload or output limits imposed by the service.
</p>
<p>The positional match may be done in any spherical coordinate system,
it's up to the user to ensure that the same coordinates are provided
for the local and remote tables.
</p>
<p>Note that <a href="cdsskymatch.html"><code>cdsskymatch</code></a>
provides similar functionality by accessing a different external service,
which is usually much faster;
if the table you wish to match is part of the VizieR database,
you may wish to use that command instead.
</p>
<ul>
<li><a href="tapskymatch-usage.html">B.23.1 Usage</a></li>
<li><a href="secB.23.2.html">B.23.2 Examples</a></li>
</ul>
<hr><a href="tapskymatch-usage.html">Next</a> <a href="secB.22.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="tapskymatch-usage.html">Usage</a><br>
<b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
<b>Previous: </b><a href="secB.22.2.html">Examples</a><br>
<hr><i>STILTS - Starlink Tables Infrastructure Library Tool Set<br>Starlink User Note256<br>STILTS web page:
<a href="http://www.starlink.ac.uk/stilts/">http://www.starlink.ac.uk/stilts/</a><br>Author email:
<a href="mailto:m.b.taylor@bristol.ac.uk">m.b.taylor@bristol.ac.uk</a><br>Mailing list:
<a href="mailto:topcat-user@jiscmail.ac.uk">topcat-user@jiscmail.ac.uk</a><br></i></body>
</html>
|