diff options
| author | Joris Van den Bossche <jorisvandenbossche@gmail.com> | 2019-04-10 07:40:04 +0000 |
|---|---|---|
| committer | Joris Van den Bossche <jorisvandenbossche@gmail.com> | 2019-04-10 07:40:04 +0000 |
| commit | f7f6b9760e4dc2e3d4296b34e05f868148b2deb2 (patch) | |
| tree | 11c14adc3979799f2c2f699c54708b001b167bc4 /docs/source/development | |
| parent | 1940d63aea9a97c1fbe558b78f8c128b7d6afb51 (diff) | |
| download | PROJ-f7f6b9760e4dc2e3d4296b34e05f868148b2deb2.tar.gz PROJ-f7f6b9760e4dc2e3d4296b34e05f868148b2deb2.zip | |
convert remaining links + reflow text
Diffstat (limited to 'docs/source/development')
| -rw-r--r-- | docs/source/development/quickstart.rst | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/docs/source/development/quickstart.rst b/docs/source/development/quickstart.rst index 5fc2d394..b6c5d17c 100644 --- a/docs/source/development/quickstart.rst +++ b/docs/source/development/quickstart.rst @@ -39,14 +39,14 @@ this in detail. :dedent: 4 Next we create the :c:type:`PJ` transformation object ``P`` with the function -:c:func:`proj_create`. ``proj_create`` takes the threading context ``C`` created above, -and a proj-string that defines the desired transformation. Here we transform -from geodetic coordinate to UTM zone 32N. +:c:func:`proj_create`. :c:func:`proj_create` takes the threading context ``C`` +created above, and a proj-string that defines the desired transformation. +Here we transform from geodetic coordinate to UTM zone 32N. It is recommended to create one threading-context per thread used by the program. -This ensures that all ``PJ`` objects created in the same context will be sharing -resources such as error-numbers and loaded grids. -In case the creation of the ``PJ`` object fails an error message is displayed and -the program returns. See :doc:`errorhandling` for further +This ensures that all :c:type:`PJ` objects created in the same context will be +sharing resources such as error-numbers and loaded grids. +In case the creation of the :c:type:`PJ` object fails an error message is +displayed and the program returns. See :doc:`errorhandling` for further details. .. literalinclude:: ../../../examples/pj_obs_api_mini_demo.c @@ -55,9 +55,9 @@ details. :dedent: 4 PROJ uses it's own data structures for handling coordinates. Here we use a -:c:type:`PJ_COORD` which is easily assigned with the function :c:func:`proj_coord`. Note -that the input values are converted to radians with :c:func:`proj_torad`. This is -necessary since PROJ is using radians internally. See :doc:`transformations` +:c:type:`PJ_COORD` which is easily assigned with the function :c:func:`proj_coord`. +Note that the input values are converted to radians with :c:func:`proj_torad`. +This is necessary since PROJ is using radians internally. See :doc:`transformations` for further details. .. literalinclude:: ../../../examples/pj_obs_api_mini_demo.c @@ -66,9 +66,9 @@ for further details. :dedent: 4 The coordinate defined above is transformed with :c:func:`proj_trans`. For this -a ``PJ`` object, a transformation direction (either forward or inverse) and the -coordinate is needed. The transformed coordinate is returned in ``b``. -Here the forward (``PJ_FWD``) transformation from geodetic to UTM is made. +a :c:type:`PJ` object, a transformation direction (either forward or inverse) +and the coordinate is needed. The transformed coordinate is returned in ``b``. +Here the forward (:c:type:`PJ_FWD`) transformation from geodetic to UTM is made. .. literalinclude:: ../../../examples/pj_obs_api_mini_demo.c :language: c @@ -76,7 +76,7 @@ Here the forward (``PJ_FWD``) transformation from geodetic to UTM is made. :dedent: 4 The inverse transformation (UTM to geodetic) is done similar to above, -this time using ``PJ_INV`` as the direction. +this time using :c:type:`PJ_INV` as the direction. .. literalinclude:: ../../../examples/pj_obs_api_mini_demo.c :language: c |