aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKristian Evers <kristianevers@gmail.com>2020-01-21 20:24:52 +0100
committerGitHub <noreply@github.com>2020-01-21 20:24:52 +0100
commit709717899c3d7ebd6c21b0d7d0a697acc505b61b (patch)
treea2056443dc96bdc2df7349ff3e0ae3d0e9d85dc2 /docs
parent1f649f8a991a7a3abd1a93499a2b8747a8d5074d (diff)
parentb13a34f3e0332d23acc9393df827d57c8386da41 (diff)
downloadPROJ-709717899c3d7ebd6c21b0d7d0a697acc505b61b.tar.gz
PROJ-709717899c3d7ebd6c21b0d7d0a697acc505b61b.zip
Merge pull request #1862 from kbevers/update-faq
Add explanation of the PROJ.4 -> PROJ shift to FAQ
Diffstat (limited to 'docs')
-rw-r--r--docs/source/faq.rst19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/source/faq.rst b/docs/source/faq.rst
index 88ca5b5b..d3cdb50f 100644
--- a/docs/source/faq.rst
+++ b/docs/source/faq.rst
@@ -172,3 +172,22 @@ paths. In most cases, the following paths are checked in order:
Note that if you're using conda, activating an environment sets
:envvar:`PROJ_LIB` to a resource directory located in that environment.
+
+What happend to PROJ.4?
+--------------------------------------------------------------------------------
+
+The first incarnation of PROJ saw the light of day in 1983. Back then it
+was simply known as PROJ. Eventually a new version was released, known
+as PROJ.2 in order to distinguish between the two versions. Later on both
+PROJ.3 and PROJ.4 was released. By the time PROJ.4 was released the
+software had matured enough that a new major version release wasn't an
+immediate necesity. PROJ.4 was around for more than 25 years before it
+again became time for an update. This left the project in a bit of a
+conundrum regarding the name. For the majority of the life-time of the product it was known as PROJ.4, but with the release of version 5 the name
+was no longer aligned with the version number. As a consequence, it was
+decided to decouple the name from the version number and once again simply
+call the software PROJ.
+
+Use of name PROJ.4 is now strictly reserved for describing legacy behaviour
+of the software, e.g. "PROJ.4 strings" as seen in :program:`projinfo`
+output.