[gdal-dev] Draft GDAL/OGR class hierarchy for GDAL 2.0

[Even Rouault]

Selon Ivan Lucena <lucena_ivan at hotmail.com>:

> Hi there,
>
> That is a great discussion and I applause Evens efforts and all the
> contributions, so but don't get me wrong by asking that:
>
> What do we want to accomplish with that class hierarchy?
>
> Will GDAL 2.0 be able to do thinks like:
>
> $ gdalinfo <dataset>
>
> And the proposed classes will be able to figure out what kind of dataset is
> that?

Well, I've completely dropped off the idea of the complex schema of classes.
This was just to make people afraid and comment, and have fun myself with UML
schemas ;-) But the ultimate goal remains to have a GDALDataset object that
handle both raster bands and vectors. So yes an upgraded gdalinfo could
potentially handle any of the below datasets. However I'm not sure of what we
want to do with the current utilities. For example if you combine both
gdal_translate and ogr2ogr in a single utility, it will have like hundred of
options... But the idea is to have the API to make it possible.

>
> It could be:
>
> - raster file
> - vector file
> - cvs file or dbf file
> - some kind of server-based connection string for raster or vector
> - some kind of service connection string for raster or vector
> - multi-dataset raster file like HDF, NetCDF
>
> Will the GDAL Open mechanism probe for all those possibilities?
>
> My best regards,
>
> Ivan
>
> > From: mateusz at loskot.net
> > Date: Thu, 27 Mar 2014 14:05:29 +0100
> > To: etourigny.dev at gmail.com
> > CC: gdal-dev at lists.osgeo.org
> > Subject: Re: [gdal-dev] Draft GDAL/OGR class hierarchy for GDAL 2.0
> >
> > On 27 March 2014 13:40, Etienne Tourigny <etourigny.dev at gmail.com> wrote:
> > > How about multiple inheritance for mixed class?  Say you have a class for
> > > rasters and a class for vectors, and a dataset that would support both
> types
> > > would inherit from these two base classes.  Is that what you mean by
> > > composite?
> >
> > I meant separate base class for mixed dataset, then use "has a"
> > relationship, like in
> >
> > class MixedDataset
> > {
> > public:
> > //
> > private:
> > RasterDataset* pDtsR
> > VectorDataset* pDtsV;
> > }
> >
> >
> > Best regards,
> > --
> > Mateusz  £oskot, http://mateusz.loskot.net
> > _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/gdal-dev
>