[gdal-dev] New OGR driver for DB2 Spatial support

Even Rouault even.rouault at spatialys.com
Mon Oct 26 11:12:25 PDT 2015


Le lundi 26 octobre 2015 18:48:47, David Adler a écrit :
> I am close to finished with this driver which was delayed significantly
> getting access to a DB2 for z/OS test environment to verify that it
> works across IBM DB2 platforms.
> 
> What is the proper way to handle authorship in the source code? The DB2
> driver is based on the MS SQL driver with significant changes to support
> the DB2 environment. Current prologues have information like:
> 
> * * Author:   Tamas Szekeres, szekerest at gmail.com
>   *
>  
> **************************************************************************
> **** * Copyright (c) 2010, Tamas Szekeres
>   * Copyright (c) 2010-2012, Even Rouault <even dot rouault at
> mines-paris dot org>*

Put yourself as author, add yourself (or your company depending on in which 
context you contribute this) in copyright and retain copyright attributions of 
portions of code you derive from. Which can be hard to determine in practice. 
So I'd say retain Tamas ones and you can probably remove mine, which must be 
anectodical in the case of the MSSQL driver.

> 
> I've mostly been testing using the apps test_ogrsf, ogr2ogr and ogrinfo.
> 
> Is there any documentation on the autotest system?

Well, itself is assumed to be self documented ;-) look at a few existing 
scripts close to what you want to do and do the same...

> It was interesting to
> find that there was a 2003 DB2 test driver for DB2 V7

You mean the ogr/ogr_db2_hack.py file ? I'm not sure if/which was the 
corresponding driver. Perhaps the generic OBDC one.

> - we are now at
> V10.5.
> 
> Regards,
> David
> 
> On 6/12/2015 5:50 PM, Even Rouault wrote:
> >>> 3. What is the plan for the transition to GDAL 2.0?  My driver was
> >>> developed against GDAL 1.11.2 and parallels similar drivers for MSSQL,
> >>> PostGIS, Oracle, etc.
> >> 
> >> Current trunk is 2.0,
> > 
> > 2.1dev actually ;-)
> > 
> >> with a release candidate out.  You may have to
> >> do a little work to update the driver.
> > 
> > Should be covered by
> > https://svn.osgeo.org/gdal/trunk/gdal/MIGRATION_GUIDE.TXT
> > 
> >>> ---
> >>> This email has been checked for viruses by Avast antivirus software.
> >>> https://www.avast.com/antivirus
> >>> 
> >>> _______________________________________________
> >>> gdal-dev mailing list
> >>> gdal-dev at lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com


More information about the gdal-dev mailing list