New initial commit

.gitignore

@@ -0,0 +1,36 @@
+index.html
+index.js
+package.html
+lib
+
+project/boot
+project/plugins/project
+project/plugins/target
+project/target
+target
+.ensime
+\#*#
+*~
+.#*
+.lib
+*.aux.xml
+*.jar
+*.crc
+_SUCCESS
+
+*.pyc
+.project
+.classpath
+.cache
+.settings
+.history
+.idea
+.DS_Store
+*.iml
+*.swp
+*.swo
+*.sublime-*
+.vagrant
+
+.ensime*
+tags

CONTRIBUTING.md

@@ -0,0 +1,77 @@
+# Contributing to Proj4j
+
+The Proj4j project is always excited to accept contributions from the community. This document
+contains some guidelines to help users and developers contribute to the project.
+
+ - [Code Style](#code)
+ - [Issues and Bugs](#bugs)
+ - [Discussion Forum](#discuss)
+ - [Submitting Patches](#patches)
+
+## <a name="code">Code Style</a>
+
+Proj4j adheres to (as much as possible) the
+[Google Java Style](https://google.github.io/styleguide/javaguide.html) conventions. If a patch
+or commit deviates from these guidelines a reviewer will likely ask for it to be reformatted.
+
+## <a name="bugs">Issues, Bugs, and Feature Requests</a>
+
+Proj4j utilizes Github for issue tracking. Bugs, issues, and feature requests should be
+filed [here](https://github.com/locationtech/proj4j/issues).
+
+## <a name="discuss">Discussion Forum</a>
+
+Often communication can be carried out through comments on an issue or pull request directly but
+for larger discussions that are more general in nature it is recommended that the project
+[mailing list](https://locationtech.org/mailman/listinfo/proj4j-dev) be used.
+
+## <a name="patches">Submitting Patches</a>
+
+The best way to submit a patch or add a new feature to the code is to submit a [
+pull request](https://help.github.com/articles/using-pull-requests/). Below are some guidelines to
+follow when developing code intended to be submitted via pull request.
+
+This [guide](http://people.redhat.com/rjones/how-to-supply-code-to-open-source-projects/) contains
+some useful guidelines for contributing to open source projects in general. Below are some additionally
+stressed points.
+
+### Send email first
+
+It is never a bad idea to email the mailing list with thoughts about a change you intend to make
+before you make it. This allows the committers to weigh in with thoughts and suggestions that will
+help you make the change and ultimately ensure your successful contribution to the project.
+
+### Sign off on commits, and filing a CLA
+
+Non-committers submitting patches to Proj4j must use the "-s" (sign-off) flag when making
+commits with git. This flag indicates that the author verifies the change is (too the best knowledge
+of the author) in good standing and consistent with the open source license of the project, and that
+if he/she has permission from their employer to contribute the code (if applicable).
+The following is an example of a commit with the sign-off flag.
+
+     git commit -s -m "the commit message"
+
+Once a developer has been elevated to project committer status the sign-off flag is no longer required.
+
+Additionally, a one-time event is to [submit a a CLA](https://projects.eclipse.org/user/sign/cla)
+"Contributor License Agreement".  It's simple and fast to do.
+
+### One patch per one bug/feature
+
+Avoid submitting patches that mix together multiple features and/or bug fixes into a single changeset.
+It is much easier to review and understand a patch that is dedicated to a single purpose.
+
+### No cruft
+
+While working on a patch often developers can't resist the urge to reformat code that is unrelated
+to the patch. This adds unnecessary "noise" that makes the job of the reviewer more difficult. It
+also makes the history of a change harder to analyze after the fact. If a patch contains unnecessary
+whitespace or other formatting changes a reviewer will ask for them to be removed.
+
+### Viewing the entire project history
+
+(Optional) We recommended that developers do this step to be able to view the
+pre-LocationTech history of the project. This can be achieved with the following
+command after the repository has been cloned:
+
+    git fetch origin refs/replace/*:refs/replace/*

LICENSE

@@ -0,0 +1,16 @@
+This software is licensed under the Apache 2 license, quoted below.
+
+Copyright 2011-2016 Azavea [http://www.azavea.com]
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not
+use this file except in compliance with the License. You may obtain a copy of
+the License at
+
+    [http://www.apache.org/licenses/LICENSE-2.0]
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+License for the specific language governing permissions and limitations under
+the License.
+

README.md

@@ -0,0 +1,8 @@
+# Proj4J
+
+Proj4J is a Java library for converting coordinates between different geospatial coordinate reference systems.
+It is designed to be compatible with `proj.4` parameters and derives some of its implementation from the `proj.4` sources.
+
+## Building, Testing and installing locally
+
+`mvn clean install`

about.md

@@ -0,0 +1,17 @@
+## About This Content
+
+February 6, 2017
+
+### License
+
+The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the
+Content is provided to you under the terms and conditions of the Apache License, Version 2.0.  A copy of the Apache
+License, Version 2.0 is available at
+[http://www.apache.org/licenses/LICENSE-2.0.txt](http://www.apache.org/licenses/LICENSE-2.0.txt)
+
+If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another
+party ("Redistributor") and different terms and conditions may apply to your use of any object code in the Content.
+Check the Redistributor’s license that was provided with the Content. If no such license exists, contact the
+Redistributor. Unless otherwise indicated below, the terms and conditions of the Apache License, Version 2.0 still apply
+to any source code in the Content and such source code may be obtained at
+[http://www.eclipse.org](http://www.eclipse.org).

notice.md

@@ -0,0 +1,108 @@
+## Eclipse Foundation Software User Agreement
+
+April 9, 2014
+
+### Usage Of Content
+
+THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE
+PROJECTS (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR
+THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE
+THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
+AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT
+AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY
+NOT USE THE CONTENT.
+
+### Applicable Licenses
+
+Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and
+conditions of the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is provided with this Content and is
+also available at [http://www.eclipse.org/legal/epl-v10.html](http://www.eclipse.org/legal/epl-v10.html). For purposes
+of the EPL, "Program" will mean the Content.
+
+Content includes, but is not limited to, source code, object code, documentation and other files maintained in the
+Eclipse Foundation source code repository ("Repository") in software modules ("Modules") and made available as
+downloadable archives ("Downloads").
+
+*   Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content.
+    Typical modules may include plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and features ("Features").
+*   Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java™ ARchive) in a directory named "plugins".
+*   A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged
+    as a sub-directory in a directory named "features". Within a Feature, files named "feature.xml" may contain a list
+    of the names and version numbers of the Plug-ins and/or Fragments associated with that Feature.
+*   Features may also include other Features ("Included Features"). Within a Feature, files named "feature.xml" may
+    contain a list of the names and version numbers of Included Features.
+
+The terms and conditions governing Plug-ins and Fragments should be contained in files named "about.html" ("Abouts").
+The terms and conditions governing Features and Included Features should be contained in files named "license.html"
+("Feature Licenses"). Abouts and Feature Licenses may be located in any directory of a Download or Module including, but
+not limited to the following locations:
+
+*   The top-level (root) directory
+*   Plug-in and Fragment directories
+*   Inside Plug-ins and Fragments packaged as JARs
+*   Sub-directories of the directory named "src" of certain Plug-ins
+*   Feature directories
+
+Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined
+below), you must agree to a license ("Feature Update License") during the installation process. If the Feature contains
+Included Features, the Feature Update License should either provide you with the terms and conditions governing the
+Included Features or inform you where you can locate them. Feature Update Licenses may be found in the "license"
+property of files named "feature.properties" found within a Feature. Such Abouts, Feature Licenses, and Feature Update
+Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the
+associated Content in that directory.
+
+THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR
+TERMS AND CONDITIONS. SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):
+
+*   Eclipse Distribution License Version 1.0 (available at
+    [http://www.eclipse.org/licenses/edl-v1.0.html](http://www.eclipse.org/licenses/edl-v10.html))
+*   Common Public License Version 1.0 (available at
+    [http://www.eclipse.org/legal/cpl-v10.html](http://www.eclipse.org/legal/cpl-v10.html))
+*   Apache Software License 1.1 (available at
+    [http://www.apache.org/licenses/LICENSE](http://www.apache.org/licenses/LICENSE))
+*   Apache Software License 2.0 (available at
+    [http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
+*   Mozilla Public License Version 1.1 (available at
+    [http://www.mozilla.org/MPL/MPL-1.1.html](http://www.mozilla.org/MPL/MPL-1.1.html))
+
+IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature
+License, or Feature Update License is provided, please contact the Eclipse Foundation to determine what terms and
+conditions govern that particular Content.
+
+### Use of Provisioning Technology
+
+The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and
+the Eclipse Update Manager ("Provisioning Technology") for the purpose of allowing users to install software,
+documentation, information and/or other materials (collectively "Installable Software"). This capability is provided
+with the intent of allowing such users to install, extend and update Eclipse-based products. Information about packaging
+Installable Software is available at
+[http://eclipse.org/equinox/p2/repository_packaging.html](http://eclipse.org/equinox/p2/repository_packaging.html)
+("Specification").
+
+You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for
+enabling the applicable license agreements relating to the Installable Software to be presented to, and accepted by, the
+users of the Provisioning Technology in accordance with the Specification. By using Provisioning Technology in such a
+manner and making it available in accordance with the Specification, you further acknowledge your agreement to, and the
+acquisition of all necessary rights to permit the following:
+
+1.  A series of actions may occur ("Provisioning Process") in which a user may execute the Provisioning Technology on a
+    machine ("Target Machine") with the intent of installing, extending or updating the functionality of an
+    Eclipse-based product.
+2.  During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion
+    thereof to be accessed and copied to the Target Machine.
+3.  Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the
+    Installable Software ("Installable Software Agreement") and such Installable Software Agreement shall be accessed
+    from the Target Machine in accordance with the Specification. Such Installable Software Agreement must inform the
+    user of the terms and conditions that govern the Installable Software and must solicit acceptance by the end user in
+    the manner prescribed in such Installable Software Agreement. Upon such indication of agreement by the user, the
+    provisioning Technology will complete installation of the Installable Software.
+
+### Cryptography
+
+Content may contain encryption software. The country in which you are currently may have restrictions on the import,
+possession, and use, and/or re-export to another country, of encryption software. BEFORE using any encryption software,
+please check the country's laws, regulations and policies concerning the import, possession, or use, and re-export of
+encryption software, to see if this is permitted.
+
+<small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries,
+or both.</small>

pom.xml

@@ -0,0 +1,46 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+    <modelVersion>4.0.0</modelVersion>
+
+    <groupId>org.osgeo</groupId>
+    <artifactId>proj4j</artifactId>
+    <version>0.1.0</version>
+    <packaging>jar</packaging>
+
+    <name>proj4j</name>
+    <url>http://trac.osgeo.org/proj4j/</url>
+
+    <properties>
+        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+    </properties>
+
+    <dependencies>
+        <dependency>
+            <groupId>junit</groupId>
+            <artifactId>junit</artifactId>
+            <version>4.12</version>
+            <scope>test</scope>
+        </dependency>
+    </dependencies>
+
+    <build>
+        <plugins>
+            <plugin>
+                <groupId>org.apache.maven.plugins</groupId>
+                <artifactId>maven-compiler-plugin</artifactId>
+                <version>3.6.0</version>
+                <configuration>
+                    <source>1.7</source>
+                    <target>1.7</target>
+                    <debug>true</debug>
+                    <encoding>UTF-8</encoding>
+                </configuration>
+            </plugin>
+            <plugin>
+                <groupId>org.apache.maven.plugins</groupId>
+                <artifactId>maven-surefire-plugin</artifactId>
+                <version>2.19.1</version>
+            </plugin>
+        </plugins>
+    </build>
+</project>