Hi all,
pull request here:
https://github.com/geotools/geotools/pull/1872
Cheers
Andrea
On Wed, Apr 4, 2018 at 2:07 PM, Andrea Aime
wrote:
> Hi Ben,
> I've already inquired to Even about those failures, looks like signature
> of a few methods changes in OGR 1.11.
> Both JNI and BridJ bindings
Hey guys. Definitely ok with moving the jni based module back to
unsupported. As you know I havent been much of a maintainer for quite some
time now so I'm fine with whatever you guys think best.
On Sat, Apr 21, 2018, 2:19 AM Andrea Aime
wrote:
> On Sat, Apr 21, 2018 at 12:08 AM, Ben Caradoc-Dav
On Sat, Apr 21, 2018 at 12:08 AM, Ben Caradoc-Davies
wrote:
> On 20/04/18 18:24, Andrea Aime wrote:
>
>> On Fri, Apr 20, 2018 at 1:16 AM, Jody Garnett
>> wrote:
>>
>>> Andrea, I often often been frustrated with build difficulties on this one
>>> over the years. I understand it is not supported,
On 20/04/18 18:24, Andrea Aime wrote:
On Fri, Apr 20, 2018 at 1:16 AM, Jody Garnett
wrote:
Andrea, I often often been frustrated with build difficulties on this one
over the years. I understand it is not supported, so just remain frustrated
- usually removing GDAL when it showed up on my path.
On Fri, Apr 20, 2018 at 1:16 AM, Jody Garnett
wrote:
> Andrea, I often often been frustrated with build difficulties on this one
> over the years. I understand it is not supported, so just remain frustrated
> - usually removing GDAL when it showed up on my path.
>
Well, the module is actually in
Andrea, I often often been frustrated with build difficulties on this one
over the years. I understand it is not supported, so just remain frustrated
- usually removing GDAL when it showed up on my path.
--
Jody Garnett
On 18 April 2018 at 05:30, Andrea Aime wrote:
> Hi all,
> any feedback?
Thanks for clarifying - I suppose it would be possible to segment the level of
support to levels:
Level 1 would be is reading and writing the geometry, crs and tabular data,
level 2 would be the styling - I'm currently examining the MITAB source to see
how big a task this should be.
-Jesper
>
As I recall just importing the basic geometries from a MapInfo file wasn't
too hard but there is a whole bunch of styling and other junk in there too
that people wanted to read in.
Plus whoever was doing it would need a MapInfo licence to generate/check
input files.
So not impossible but not chea
Hi list
Ugh - removing OGR support will make it impossible for Java tools to access
MapInfo files. We're using BridJ for now, as it's easier to get the GDAL bits
without the corresponding JNI shared object.
Is there anything I could do to help? How big a job is building MapInfo support
in Java
Hi Jesper,
you can take over maintainership of the BridJ module and fix the build, or
sponsor
someone to do it for you.
Writing mapinfo support in java would be best of course, but also believe
it's a sizable effort
(take a look at the OGR mapinfo source code, something similar would have
to be bu
Hi all,
any feedback? If not, I plan to remove the module sometimes soon.
(mind, the JNI module will be broken just the same at runtime, but won't
fail the build unless the JNI native lib is around, which is normally not)
Cheers
Andrea
On Wed, Apr 4, 2018 at 2:07 PM, Andrea Aime
wrote:
> Hi Ben
Hi Ben,
I've already inquired to Even about those failures, looks like signature of
a few methods changes in OGR 1.11.
Both JNI and BridJ bindings fail, the difference is that BridJ does not
need the "bridge" JNI native library so it
runs most of the time, while the JNI one skip the tests.
Now, wi
12 matches
Mail list logo
