Even,
On Tue, Oct 29, 2013 at 10:04 AM, Even Rouault
wrote:
>> I'm thinking that there is rarely any reason to separate the
>> connections, except if, maybe we'd like to support multiple accounts,
>> so that you can get table A using account A, and table B with account
>> B. But then again why do
Wolf,
> >
> > The boilerplate code is quite typical of the standard OGR driver. You would
> > need/want a shared connection among different OGRGMEDataSource ? That would
> be
> > the point of moving it at the driver level. Actually I've coded something
> like
> > that in the FGDB driver since ther
Even,
>
> I don't know the GME API, so the following might be non relevant, but I'm
> wondering why you couldn't keep the current connection logic. You would "just"
> need to establish the list of vector tables from a "GetMapContent" request (or
> whatever it is called) and you would instanciate t
Le mardi 29 octobre 2013 00:24:37, Wolf Bergenheim a écrit :
> Hi all,
>
> I'm working on the GDAL Google Maps Engine (GME) driver over then next few
> months for a school project. I've set up a wiki page for it where you can
> track my progress. It's here:
>
> http://trac.osgeo.org/gdal/wiki/GME
Hi all,
I'm working on the GDAL Google Maps Engine (GME) driver over then next few
months for a school project. I've set up a wiki page for it where you can
track my progress. It's here:
http://trac.osgeo.org/gdal/wiki/GMEDriver
I'm picking up from where Frank and I left off a few months ago.
F
