<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello all</p>
<p>A version 1.0 of Java Native Interface (JNI) binding for PROJ has
been completed a few months ago [1]. Those bindings map PROJ C++
API to GeoAPI 3.0.1 (it was less practical to map the C API
because of large conceptual model differences). The code is under
the same license (MIT) than PROJ. Is there an interest for moving
those binding under the wings of the PROJ project, not necessarily
in the main Git repository but possibly as another product
maintained by the project, similarly to PROJ-data? I would
volunteer for maintaining those JNI bindings. I didn't maintained
the previous bindings because the fact that it didn't implemented
GeoAPI made it less usable for me, to the point that I was
maintaining another binding of Proj.4 [2]. But with the new
bindings under PROJ wing I would delete the other binding, so my
focus would be on the PROJ one only.</p>
<p>What peoples think?</p>
<p> Martin<br>
</p>
<pre>[1] <a class="moz-txt-link-freetext" href="https://github.com/Kortforsyningen/PROJ-JNI/">https://github.com/Kortforsyningen/PROJ-JNI/</a>
[2] <a class="moz-txt-link-freetext" href="https://github.com/opengeospatial/geoapi/tree/fd10ad11d1cb0e8ad27f89942ed54db0f406cb5e/geoapi-proj4">https://github.com/opengeospatial/geoapi/tree/fd10ad11d1cb0e8ad27f89942ed54db0f406cb5e/geoapi-proj4</a>
</pre>
</body>
</html>