<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi there,<br><br>That is a great discussion and I applause Evens efforts and all the contributions, so but don't get me wrong by asking that:<br><br>What do we want to accomplish with that class hierarchy?<br><br>Will GDAL 2.0 be able to do thinks like:<br><br>$ gdalinfo <dataset><br><br>And the proposed classes will be able to figure out what kind of dataset is that?<br><br>It could be:<br><br>- raster file<br>- vector file<br>- cvs file or dbf file<br>- some kind of server-based connection string for raster or vector<br>- some kind of service connection string for raster or vector<br>- multi-dataset raster file like HDF, NetCDF<br><br>Will the GDAL Open mechanism probe for all those possibilities?<br><br>My best regards,<br><br>Ivan<br><br><div>> From: mateusz@loskot.net<br>> Date: Thu, 27 Mar 2014 14:05:29 +0100<br>> To: etourigny.dev@gmail.com<br>> CC: gdal-dev@lists.osgeo.org<br>> Subject: Re: [gdal-dev] Draft GDAL/OGR class hierarchy for GDAL 2.0<br>> <br>> On 27 March 2014 13:40, Etienne Tourigny <etourigny.dev@gmail.com> wrote:<br>> > How about multiple inheritance for mixed class? Say you have a class for<br>> > rasters and a class for vectors, and a dataset that would support both types<br>> > would inherit from these two base classes. Is that what you mean by<br>> > composite?<br>> <br>> I meant separate base class for mixed dataset, then use "has a"<br>> relationship, like in<br>> <br>> class MixedDataset<br>> {<br>> public:<br>> //<br>> private:<br>> RasterDataset* pDtsR<br>> VectorDataset* pDtsV;<br>> }<br>> <br>> <br>> Best regards,<br>> -- <br>> Mateusz Łoskot, http://mateusz.loskot.net<br>> _______________________________________________<br>> gdal-dev mailing list<br>> gdal-dev@lists.osgeo.org<br>> http://lists.osgeo.org/mailman/listinfo/gdal-dev<br></div> </div></body>
</html>