<feed xmlns='http://www.w3.org/2005/Atom'>
<title>PROJ/docs/source/operations/options, branch 7.1.1</title>
<subtitle>Forked from https://github.com/OSGeo/PROJ</subtitle>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/PROJ/'/>
<entry>
<title>Add an hardcoded +ellps=GRS80 when there is no datum/ellipsoid specification (refs #201)</title>
<updated>2018-12-27T15:22:09+00:00</updated>
<author>
<name>Even Rouault</name>
<email>even.rouault@spatialys.com</email>
</author>
<published>2018-12-27T15:22:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/PROJ/commit/?id=6bb14fa874562eb4879a3b80b51b22cd2add058e'/>
<id>6bb14fa874562eb4879a3b80b51b22cd2add058e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Temporal gridshifting (#1015)</title>
<updated>2018-05-24T13:22:43+00:00</updated>
<author>
<name>Kristian Evers</name>
<email>kristianevers@gmail.com</email>
</author>
<published>2018-05-24T13:22:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/PROJ/commit/?id=0b5c3622e37dcf697db45e8db05fd4ebf045674b'/>
<id>0b5c3622e37dcf697db45e8db05fd4ebf045674b</id>
<content type='text'>
Temporal gridshifts allow [h|v]gridshift operations to be used as step functions
in a pipeline. This is useful in transformations dealing with deformations caused
by earthquakes.

See the included documentation for details.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Temporal gridshifts allow [h|v]gridshift operations to be used as step functions
in a pipeline. This is useful in transformations dealing with deformations caused
by earthquakes.

See the included documentation for details.</pre>
</div>
</content>
</entry>
<entry>
<title>Refactor operation doc pages</title>
<updated>2018-04-30T20:57:05+00:00</updated>
<author>
<name>Kristian Evers</name>
<email>kristianevers@gmail.com</email>
</author>
<published>2018-04-30T20:42:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.otimperi.dev/PROJ/commit/?id=970d708ff9d796f7d9ec00b22023e835fbdc7f2d'/>
<id>970d708ff9d796f7d9ec00b22023e835fbdc7f2d</id>
<content type='text'>
Extended the use of the :option: directive to all currently written
operation doc pages. In the process several more default parameters were
added for easy inclusion in other doc pages.

Expanded the info tables for each operation with "domain", "alias",
"input type" and "output type".

Corrected various errors along the way. Mainly formatting errors and
references to invalid parameters such as +sym in hatano.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Extended the use of the :option: directive to all currently written
operation doc pages. In the process several more default parameters were
added for easy inclusion in other doc pages.

Expanded the info tables for each operation with "domain", "alias",
"input type" and "output type".

Corrected various errors along the way. Mainly formatting errors and
references to invalid parameters such as +sym in hatano.
</pre>
</div>
</content>
</entry>
<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>
