| Age | Commit message (Collapse) | Author |
|
proj_create_crs_to_crs() (refs #1223)
|
|
make proj_create() do more or less what proj_create_from_user_input() did before (fixes #1214)
|
|
vs the ones of the C++ API (fixes #1213) (#1215)
|
|
The rest of the C API is structured such that type definitions goes into
one page and functions to another. This commit makes sure the same is
done for the C bindings to the ISO19111 C++ API by defining two doxygen
groups in proj.h, which is then organized into the proper pages with
Sphinx and breathe.
|
|
Added Fortran-Proj, bindings for PROJ in Fortran.
|
|
This work mostly consists of:
- a C++ implementation of the ISO-19111:2018 / OGC Topic 2
"Referencing by coordinates" classes to represent Datums,
Coordinate systems, CRSs (Coordinate Reference Systems) and
Coordinate Operations.
- methods to convert between this C++ modeling and WKT1, WKT2
and PROJ string representations of those objects
- management and query of a SQLite3 database of CRS and Coordinate Operation definition
- a C API binding part of those capabilities
This is all-in-one squashed commit of the work of
https://github.com/OSGeo/proj.4/pull/1040
|
|
Closes #1107
|
|
|
|
With projects.h not being available to outside users anymore we need to
define PJ_UNITS, PJ_ELLPS, PJ_PRIME_MERIDIANS and PJ_OPERATIONS
elsewhere.
Related pj_get_*_ref() functions have been removed in favour
of their proj_ namespaced counterparts.
char pointers have been changed to const char pointers.
Resolves #983
Resolved #1147
Make char pointers const
|
|
|
|
|
|
This was left out when documented the various proj_create_*
functions. Added proj_context_errno description as well
since it was undocumented and is needed when creating PJs
for a specific context.
|
|
|
|
Internally PROJ uses radians so of course that is what we
need to convert our input coordinates to before processing
with proj_trans().
|
|
|
|
|
|
Mailing list section from frontpage moved to the new section. So is the
contributing and for_proj_contributors pages.
|
|
|
|
|
|
docs/source/contributing.rst to doc/source/development/for_proj_contributors.rst
|
|
(fixes #862)
|
|
|
|
Add proj_errno_string function
|
|
Equivalent to pj_strerrno.
|
|
Changes use of 'PJ_COORD coo' to 'PJ_COORD coord' so that variable names in
public function prototypes are consistent.
Closes #842.
|
|
|
|
Some minor linguistic corrections + general update to make the documentation reflect the updates in PR #775
|
|
|
|
|
|
Brazenly stolen from mailing list post by Thomas Knudsen [0] and
modified slightly to fit the context.
[0] http://lists.maptools.org/pipermail/proj/2018-February/007995.html
|
|
|
|
docs-release-4.10.0
|
|
|
|
|
|
This version takes to add the include path to the target definition for
cmake 2.8.11 and later. Also the documentation sticks to the existing
convention of using cmake variables ${PROJ4_LIBRARIES} and
${PROJ4_INCLUDE_DIRS}. However, the namespace variables are still being
included.
Here's the roll-out plan
(0) Version 4.9.x: The target is proj and PROJ4_LIBRARIES is set to
this.
(1) Version 5.0.x: Two targets, proj and PROJ4::proj, are defined;
PROJ4_LIBRARIES = proj.
(2) In a year or two: Two targets, proj and PROJ4::proj, are defined;
PROJ4_LIBRARIES = PROJ4::proj.
(3) With a change in the library which breaks backwards compatibility:
The target is PROJ4::proj and PROJ4_LIBRARIES = PROJ4::proj.
|
|
|
|
|
|
|
|
PROJ.4.
[skip ci]
|
|
|
|
|
|
|
|
|
|
section named 'deprecated'. Created a quickstart page for the development chapter. Scaffolding in place for the rest of the chapter.
|
|
|
|
A section on "Using PROJ.4" has been introduced giving a introduction
on how to use PROJ.4. The Parameters section has been removed and the
content reworked into other sections. Additionally the order of chapters
has been changed to provide a more complete and readable experience for
users of the documentation.
|
|
* Get PDF build output with Sphinx healthy
* copy pdf to branch for upload on website
|
|
|