This file is indexed.

/usr/share/doc/stilts/sun256/location-syntax.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
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
<html>
   
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <link rel="stylesheet" type="text/css" href="sun-style.css">
      <title>Table Locations</title>
   </head>
   
   <body>
      <hr>
      <a href="sec5.2.html">Next</a> <a href="io.html">Previous</a> <a href="io.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="sec5.2.html">Table Formats</a><br>
       <b>Up: </b><a href="io.html">Table I/O</a><br>
       <b>Previous: </b><a href="io.html">Table I/O</a><br>
      
      <hr>
      <h3><a name="location-syntax">5.1 Table Locations</a></h3>
      <p>The location of tables for input and output are usually given using
         the <code>in</code> and <code>out</code> parameters respectively.
         These are often, but not always, filenames.  The possibilities are these:
         
         <dl>
            <dt><strong>Filename</strong></dt>
            <dd>Very often, you will simply specify a filename as location, and
               the tool will just read from/write to it in the usual way.
               
            </dd>
            <dt><strong>URL</strong></dt>
            <dd>Tables can be read from URLs directly, and in some cases written
               to them as well.  Some non-standard URL protocols are supported 
               as well as the usual ones.  The list is:
               
               <dl>
                  <dt><strong><code>http:</code></strong></dt>
                  <dd>Read from HTTP resources.</dd>
                  <dt><strong><code>ftp:</code></strong></dt>
                  <dd>Read from anonymous FTP resources.</dd>
                  <dt><strong><code>file:</code></strong></dt>
                  <dd>Read from local files.
                     This is not particularly useful since you can
                     do much the same using just the filename.
                     There is a difference: using this form forces reads to be sequential
                     rather than random access, which may allow you to experience
                     a different set of different performance characteristics
                     and bugs.
                  </dd>
                  <dt><strong><code>jar:</code></strong></dt>
                  <dd>Specialised protocol for looking inside Java Archive files -
                     see <a href="http://docs.oracle.com/javase/6/docs/api/java/net/JarURLConnection.html">JarURLConnection</a> documentation.
                  </dd>
                  <dt><strong><code>myspace:</code></strong></dt>
                  <dd>Accesses files in the AstroGrid "MySpace" virtual file store.
                     These URLs look something like 
                     "<code>myspace:/survey/iras_psc.xml</code>",
                     and can access files in the myspace are that the user is currently
                     logged into.
                     These URLs can be used for both input and output of tables.
                     To use them you must have an AstroGrid account and the AstroGrid
                     WorkBench or similar must be running; if you're not currently
                     logged in a dialogue will pop up to ask you for name and 
                     password.
                  </dd>
                  <dt><strong><code>ivo:</code></strong></dt>
                  <dd>Understands ivo-type URLs which signify files in the
                     AstroGrid "MySpace" virtual file store.  
                     These URLs look something like
                     "<code>ivo://uk.ac.le.star/filemanager#node-2583</code>".
                     These URLs can be used for both input and output of tables.
                     To use them you must have an AstroGrid account and the AstroGrid
                     WorkBench or similar must be running; if you're not currently
                     logged in a dialogue will pop up to ask you for name and 
                     password.
                  </dd>
                  <dt><strong><code>jdbc:</code></strong></dt>
                  <dd>Used for communicating with SQL-compliant relational databases.
                     These are a bit different to normal URLs -
                     see section <a href="jdbcConfig.html">Section 3.4</a>.
                  </dd>
               </dl>
               
            </dd>
            <dt><strong>Minus sign ("<code>-</code>")</strong></dt>
            <dd>The special location "-" (minus sign) indicates standard input 
               (for reading) or standard output (for writing).
               This allows you to use STILTS commands in a normal Unix pipeline.
               
            </dd>
            <dt><strong>System command ("<code>&lt;</code><em>syscmd</em>" or
                  "<em>syscmd</em><code>|</code>)</strong></dt>
            <dd>If the location starts with a "<code>&lt;</code>" character
               or ends with a "<code>|</code>" character,
               the rest of the string is taken as a command line to be executed
               by the system shell.
               For instance a location like
               "<code>&lt;cat header.txt data.txt</code>"
               (or equivalently
               "<code>cat header.txt data.txt|</code>")
               could be used to prepend a header line to an ASCII data file
               before it is passed to the STILTS ASCII-format input handler.
               Note this syntax will probably only work on Unix-like systems.
               
            </dd>
         </dl>
         
      </p>
      <p>In any of these cases, for input locations compression is taken care
         of automatically.  That means that you can give the filename or URL
         of a file which is compressed using <code>gzip</code>, <code>bzip2</code>
         or Unix <code>compress</code> and the program will uncompress it on the fly.
         
      </p>
      <hr><a href="sec5.2.html">Next</a> <a href="io.html">Previous</a> <a href="io.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="sec5.2.html">Table Formats</a><br>
       <b>Up: </b><a href="io.html">Table I/O</a><br>
       <b>Previous: </b><a href="io.html">Table I/O</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>