PROJ-JNI
PROJ-JNI copied to clipboard
OSGeo
Java Native Interface for PROJ
PROJ-JNI uses `java.util.logging` for reporting warnings. But other logging frameworks such as SLF4J are popular. Since Java 9, a more framework-neutral API is available with `System.Logger`. We should replace our...
This is probably not super unexpected since this has not been tested on OS X at all. Anyway, it is possibly a problem that occurs on more that OS X....
PROJ-JNI is currently an implementation of GeoAPI 3.0.1 interfaces, which were defined from ISO 19111 standard published in 2007. It does not yet incorporate the improvements done in the ISO...
I started to work through this a little this morning. @desruisseaux it looks like you went down this path before, per commit 3a2a611fa884e2f67226386d0c22bea92043fb52: "Abandon the attempt to provide native files...
The project is currently a single Maven project, without modules. In support for #40 we may need to switch to a multi-modules Maven project. A project layout proposal is [on...
There is no mapping from ISO 19111 "Datum ensemble" to PROJ-JNI. When a geographic CRS is associated to a datum ensemble, the `datum` property value is null in current version....
Task #4 allows the horizontal component of the area of interest to be given to PROJ when searching for a coordinate operation. However the vertical and temporal components are not...
`DerivedCRS` other than `ProjectedCRS` are not yet supported. We need different implementation classes for the various derived CRS kinds (derived geographic, derived vertical, derived temporal, _etc._).
The `BoundCRS` type is supported by PROJ 6, but is not defined by GeoAPI 3.0.1. We should creating binding for it, but this task depends on #10
PROJ C++ API defines an `osgeo::proj::common::UnitOfMeasure::Type` enumeration with the `UNKNOWN`, `NONE`, `ANGULAR`, `LINEAR`, `SCALE`, `TIME` and `PARAMETRIC` values. For example the `METRE` is declared of the `LINEAR`, which is fine....