<feed xmlns='http://www.w3.org/2005/Atom'>
<title>PROJ/docs/source/operations/options/lat_ts.rst, branch azp</title>
<subtitle>Forked from https://github.com/OSGeo/PROJ</subtitle>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/PROJ/'/>
<entry>
<title>Use Sphinx option directives to document PROJ options</title>
<updated>2018-03-30T22:10:09+00:00</updated>
<author>
<name>Kristian Evers</name>
<email>kristianevers@gmail.com</email>
</author>
<published>2018-03-30T22:10:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/PROJ/commit/?id=038e3f0a508b7908f16f3517dcb0bc87d6275ab5'/>
<id>038e3f0a508b7908f16f3517dcb0bc87d6275ab5</id>
<content type='text'>
Instead of listing the various projection options in a table we write
them as :option: tags instead. This makes it easier to write a more
elaborate description of the parameter. Additionally we can create
"master"-description of commonly used parameters such as +lon_0 and +k_0
and include them where necessary. This is handled in separate files, one
for each common parameters, that are stored in
docs/source/operations/options/.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of listing the various projection options in a table we write
them as :option: tags instead. This makes it easier to write a more
elaborate description of the parameter. Additionally we can create
"master"-description of commonly used parameters such as +lon_0 and +k_0
and include them where necessary. This is handled in separate files, one
for each common parameters, that are stored in
docs/source/operations/options/.
</pre>
</div>
</content>
</entry>
</feed>
