Re: [gdal-dev] Regarding libkml driver

2015-08-20 Thread Sebastiaan Couwenberg
On 20-08-15 13:46, Sebastiaan Couwenberg wrote: > I'm working on a patch to try and support both the old Automake based & > new CMake based libkml by adding support for libkml.pc. I've got a working patch for the Debian package, forwarded in: https://trac.osgeo.org/gdal/ticket/6077 Kind Regards,

Re: [gdal-dev] Regarding libkml driver

2015-08-20 Thread Sebastiaan Couwenberg
On 20-08-15 16:48, Even Rouault wrote: > On Thursday 20 August 2015 13:46:52 Sebastiaan Couwenberg wrote: >> I'm working on a patch to try and support both the old Automake based & >> new CMake based libkml by adding support for libkml.pc. > > Are there differences in the installed files from libk

Re: [gdal-dev] Regarding libkml driver

2015-08-20 Thread Even Rouault
On Thursday 20 August 2015 13:46:52 Sebastiaan Couwenberg wrote: > On 02-08-15 21:05, Even Rouault wrote: > > On 02-08-15 20:45, Rashad M wrote: > >> No API changes. it make building and configuring libkml easier! > >> > >> Correct me If I am wrong, I guess with a pkg-config would be easier to > >

Re: [gdal-dev] Regarding libkml driver

2015-08-20 Thread Sebastiaan Couwenberg
On 02-08-15 21:05, Even Rouault wrote: > On 02-08-15 20:45, Rashad M wrote: >> No API changes. it make building and configuring libkml easier! >> >> Correct me If I am wrong, I guess with a pkg-config would be easier to find >> and configure libkml libs. > > Yes, that would probably be better. Tha

Re: [gdal-dev] Regarding libkml driver

2015-08-12 Thread Wolf Bergenheim
Sounds good. Let's move this discussion to https://github.com/google/libkml/issues/4 On 12 August 2015 at 15:31, Sebastiaan Couwenberg wrote: > On 12-08-15 15:13, Wolf Bergenheim wrote: > > I'm beginning to wonder if we should have our own libkml mailinglist, > since > > all this talk is strictl

Re: [gdal-dev] Regarding libkml driver

2015-08-12 Thread Sebastiaan Couwenberg
On 12-08-15 15:13, Wolf Bergenheim wrote: > I'm beginning to wonder if we should have our own libkml mailinglist, since > all this talk is strictly not GDAL... But as long as no-one objects. But > that's also something to think about for the future. Most of this discussion can be continued in the

Re: [gdal-dev] Regarding libkml driver

2015-08-12 Thread Wolf Bergenheim
On 12 August 2015 at 13:04, Sebastiaan Couwenberg wrote: > > > I've also commented on the Project status GitHub issue: > https://github.com/google/libkml/issues/4 > > As I wrote in an earlier comment: > > " > I'd love to see all GIS developers rally around the new preferred > repository to colla

Re: [gdal-dev] Regarding libkml driver

2015-08-12 Thread Sebastiaan Couwenberg
On 12-08-15 00:55, Wolf Bergenheim wrote: > On 11 August 2015 at 18:56, Sebastiaan Couwenberg wrote: >> On 11-08-15 18:37, Kurt Schwehr wrote: >>> Wolf and I have joined in working on libkml. We will be getting more >>> transitioned from the old code.google.com site to >>> https://github.com/googl

Re: [gdal-dev] Regarding libkml driver

2015-08-11 Thread Wolf Bergenheim
On 11 August 2015 at 18:56, Sebastiaan Couwenberg wrote: > On 11-08-15 18:37, Kurt Schwehr wrote: > > Wolf and I have joined in working on libkml. We will be getting more > > transitioned from the old code.google.com site to > > https://github.com/google/libkml, will be pushing some general > ma

Re: [gdal-dev] Regarding libkml driver

2015-08-11 Thread Donovan Cameron
I've compiled libkml from the libkml/libkml git repo and really like that minizip for example is an external dependency. This makes it so that other applications that require minizip can be compiled easily now. Donovan On 11/08/15 09:56 AM, Sebastiaan Couwenberg wrote: On 11-08-15 18:37, Ku

Re: [gdal-dev] Regarding libkml driver

2015-08-11 Thread Sebastiaan Couwenberg
On 11-08-15 18:37, Kurt Schwehr wrote: > Wolf and I have joined in working on libkml. We will be getting more > transitioned from the old code.google.com site to > https://github.com/google/libkml, will be pushing some general maintanence > patches and will be getting the pull request processed.

Re: [gdal-dev] Regarding libkml driver

2015-08-11 Thread Kurt Schwehr
Hi Rashad and all, Wolf and I have joined in working on libkml. We will be getting more transitioned from the old code.google.com site to https://github.com/google/libkml, will be pushing some general maintanence patches and will be getting the pull request processed. We look forward to collabor

Re: [gdal-dev] Regarding libkml driver

2015-08-04 Thread Kurt Schwehr
Hi Rashad, I am starting to look into libkml from the Google side. I will chat with mashbridge in next week and see if we can get some motion on libkml. -kurt Engineer at Google On Sun, Aug 2, 2015 at 12:22 PM, Rashad M wrote: > > > On Sun, Aug 2, 2015 at 9:05 PM, Even Rouault > wrote: > >>

Re: [gdal-dev] Regarding libkml driver

2015-08-02 Thread Rashad M
On Sun, Aug 2, 2015 at 9:05 PM, Even Rouault wrote: > > > > No API changes. it make building and configuring libkml easier! > > > > Correct me If I am wrong, I guess with a pkg-config would be easier to > find > > and configure libkml libs. > > Yes, that would probably be better. That said my exp

Re: [gdal-dev] Regarding libkml driver

2015-08-02 Thread Even Rouault
> > No API changes. it make building and configuring libkml easier! > > Correct me If I am wrong, I guess with a pkg-config would be easier to find > and configure libkml libs. Yes, that would probably be better. That said my experience with GDAL configure --with-libkml has been good up to now.

Re: [gdal-dev] Regarding libkml driver

2015-08-02 Thread Rashad M
On Sun, Aug 2, 2015 at 8:12 PM, Even Rouault wrote: > Rashad, > > > Hello all, > > > > We have been working on a new fork of libkml library on github. The > primary > > interest to detach from google/libkml was that various modification in > the > > library are fragmented in the github forks and

Re: [gdal-dev] Regarding libkml driver

2015-08-02 Thread Even Rouault
Rashad, > Hello all, > > We have been working on a new fork of libkml library on github. The primary > interest to detach from google/libkml was that various modification in the > library are fragmented in the github forks and nothing gets merged. There > is no activity or interest by original au

[gdal-dev] Regarding libkml driver

2015-08-02 Thread Rashad M
Hello all, We have been working on a new fork of libkml library on github. The primary interest to detach from google/libkml was that various modification in the library are fragmented in the github forks and nothing gets merged. There is no activity or interest by original authors and all efforts