= Google Summer of Code = GDAL participates in the [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] under the OSGeo umbrella. * [wiki:SoCProjects Selected Projects] == 2014 Ideas List == '''1. Automatic Geo-referencer'''[[BR]] * Presently the geo-referencing of images is done by selecting points manually.[[BR]] * By this project we aim to automate this task. This Project has two parts: [[BR]] 1. There is a GDAL-Correlator project which implemented '''Simple''' SURF algorithm. Modification of that to support '''Multi Band Images''' and '''Large Data sets'''[[BR]] 2. Applying the modified algorithm for geo-referencing. Mentor: Chaitanya Kumar CH (chaitanya[dot]ch[at]gmail.com) '''2. AutoCAD DWG OGR Driver based on libredwg.''' Note that libredwg development seems to be stalled, but the original library, [http://libdwg.sourceforge.net/en/index.html libdwg], that served as a starting point for libredwg has seen some recent activity in late 2013. Some review of status would be appropriate before committing. This would be an alternative to the more proprietary Open Design Alliance library based driver. Currently GDAL support AutoCAD DWG file via Open Design Alliance Teiga library which is not freely available and has strict license. There is a project libredwg (GNU GPL v3) which provide DWG support (R13, R14 and R2000 version). Need to rewrite (http://gdal.org/ogr/drv_dwg.html) or write the new driver for DWG. * programming skills needed - C/C++[[BR]] * difficulty level - high Possible mentor/co-mentor: Dmitry Baryshnikov (polimax@mail.ru) '''3. Adding support for "M" dimension in OGR Geometries in''' a fashion inline with modern OGC and ISO simple features geometry standards. Note, GEOS does not yet support M which will be a limiting factor. * programming skills needed - C/C++[[BR]] * difficulty level - moderate Possible mentor/co-mentor: Even Rouault( even.rouault at mines-paris.org ) '''4. Adding support for VERT_CS'''. GDAL support of VERT_CS is very limited. OGRSpatialReference::SetVertCS only supports name, datum name and VertDatumClass. Moreover drivers such as GeoTIFF and SHP cannot store Vertical CS information. No reprojection from different Vertical CS is present. More support for VERT_CS in GDAL need to proceed SAR and LAS data, and more accurate reprojecting using Vertical Coordinate System transformation. * programming skills needed - C/C++[[BR]] * difficulty level - moderate Possible mentor/co-mentor: Dmitry Baryshnikov (polimax@mail.ru) '''5. Geography Network support'''. Using any OGR driver to create abstract network model with capabilities: routing, rules, references etc. There is lack of open source common network mode to store network data (engineering networks, road routing and etc.). Need to create such model to store network data in preferable OGR format. Also model should support some algorithms: compute shortest path (Dijkstra), create path array using different criteria (K shortest path), searching disconnected segments, etc. Related projects : PostGIS topology, PgRouting, ... * programming skills needed - C/C++[[BR]] * difficulty level - high Possible mentor/co-mentor: Dmitry Baryshnikov (polimax@mail.ru) '''6. Bring up to speed the OGR style support'''. Feature Style Specification is outdated. There are several popular formats sld, svg and etc. which can be support by OGRLayer. Some format conversion maybe implemented. Need to select new style specification format, rewrite GDAL code to support it and add such functionality to such drivers as DXF, KML, MapInfo tab, etc. Possible further work could be to study what changes need to be done in MapServer project, so it can use it. * programming skills needed - C/C++[[BR]] * difficulty level - moderate Possible mentor/co-mentor: Even Rouault( even.rouault at mines-paris.org ) == 2013 Ideas List == 1. '''OGC WMTS Driver''' - likely as an extension to the existing WMS driver which does various tiling schemes too. OGC WMTS is the [http://www.opengeospatial.org/standards/wmts OGC Web Map Tile Service] 2. '''AutoCAD DWG OGR Driver based on libredwg'''. Note that libredwg development seems to be stalled. Some review of status would be appropriate before committing. This would be an alternative to the more proprietary Open Design Alliance library based driver. 3. '''Adding support for "M" dimension in OGR Geometries''' in a fashion inline with modern OGC and ISO simple features geometry standards. Note, GEOS does not yet support M which will be a limiting factor. 4. '''OSGeo4W 64 builds''' - update scripts, OSGeo4W installer, etc to build GDAL and related components for 64bit windows deployments. 5. '''WCS time series (1D dataset) support''' - compatible with RASDAMAN & compliant with the WCS spec. In line with this: [https://wiki.services.eoportal.org/tiki-download_forum_attachment.php?attId=53] 6. '''GDAL/OGR on the Web''' - A Django/GeoDjango based Web Application for doing ogr or gdal conversions on the Web. 7. '''Raster / Vector Geo-referencer on the Web''' Upload your unreferenced vectors/rasters and georeference them. Similar to this: http://www.youtube.com/watch?feature=player_embedded&v=88gt1gj2dbs but entirely based on GDAL and completely reusable. 8.- '''Support for Multiple Geometry libraries in GDAL/OGR''' Currently, instead of only supporting GEOS (LGPL), we could add support for Boost Geometry Library, too http://www.boost.org/doc/libs/1_53_0/libs/geometry/doc/html/index.html. This would allow a licensing scheme that would enable GDAL/OGR apps in iOS. == 2010 Mentors == * Frank Warmerdam (warmerdam at pobox.com) * Howard Butler (hobu.inc at gmail.com) OGR-related items * Philippe Vachon (philippe at cowpig.ca) - general raster, threading/parallelism items == 2010 Ideas List == Google will be sponsoring another [http://code.google.com/soc/ Summer of Code] for 2010. 1. '''OpenEV2''': [http://openev.sourceforge.net/ OpenEV] is a GUI tool for efficient displaying and analyzing geospatial data formats supported by GDAL/OGR (including GeoTIFF, MrSID, ECW, .. ESRI Shape files, ..), it is able to convert between file formats, reproject, crop, display by OpenGL a 3D terrain based on elevation from DEM files on Linux, Windows and Mac. Have a look at [http://openev.sourceforge.net/index.php?page=screenshots screenshots] or [http://fwtools.maptools.org/ try it]. It has almost finished port to GTK 2.0 and GDAL python-ng which needs a bit of work, packaging and improvement, more info at [http://www.nabble.com/OpenEV2-updated-td21101297.html OpenEV2 updated post]. Knowledge: Python, GNU tools, GTK 2.0, Linux and partly C, C++. 2. '''PNG Driver''': Implement efficient PNG driver using libPNG with support for optimization of PNG images exported by GDAL (info: [http://www.gdal.org/gdal_drivertut.html tutorial] + [http://svn.osgeo.org/gdal/trunk/gdal/frmts/png png driver]). You can reuse existing open-source [http://members.ozemail.com.au/~dekker/NEUQUANT.HTML NeuQuant algorithm] for RGBA and RGB export. [http://members.ozemail.com.au/~dekker/NEUQUANT.HTML NeuQuant] is easy-to-use practical demonstration of power of the Kohonen Neural Networks. It's source code can be included into GDAL from [http://members.ozemail.com.au/~dekker/NEUQUANT.C original implementation of the algorithm] and/or from [http://pngnq.sourceforge.net/ pngnq utility]. There are also other open-source tools implementing optimization of PNG which can be reused ([http://advancemame.sourceforge.net/doc-advpng.html AdvPNG], [http://optipng.sourceforge.net/ OptiPNG], [http://pmt.sourceforge.net/pngcrush/ PNGcrush]) or can be a source of inspiration ([http://www.advsys.net/ken/util/pngout.htm PNGOut]). Result should be an improved PNG driver for GDAL together with color quantization functions which will produce png files with optimized file-size. Result of this work is going to be usable in MapServer, GRASS, MapTiler and other GDAL-based projects. Knowledge: C, C++ 3. '''ODBC Driver''': Implement write support for the ODBC driver and include support for MSSQL2008 spatial database. The current ODBC driver should be extended to create or transfer spatial data into the ODBC data sources like Microsoft SQL Server. The driver must have built-in support to auto create the XMIN, YMIN, XMAX and YMAX shape envelope values for the non-spatial databases and the spatial index for the MSSQL2008 spatial databases. (info: [http://www.gdal.org/ogr/drv_odbc.html]). Result of this work is going to be usable in any project using the OGR libraries. Knowledge: C, C++, MSSQL2008 Spatial Note : a [http://gdal.org/ogr/drv_mssqlspatial.html MSSQLSpatial driver] now exists. 4. '''OGR SQL .NET Data Provider''': Implement a .NET Data Provider inteface for the OGR SQL API. This sample application would allow the user to use OgrSqlDataAdapter to read the result of an OGR SQL query into a DataSet which could be used as the datasource of the bindable .NET controls. The provider would also support transactions and batch queries and read the multiple results into multiple data tables within the same DataSet. The OgrSqlDataReader would provide a convenient way to retrieve the records sequentially for the user. (info: [http://www.gdal.org/ogr/ogr_sql.html]). Result of this work would go to the sample application section of the C# interface. Knowledge: C#, .NET Framework Class Libraries 5. '''OGR WFS read (or read/write) driver''' using existing OGR GML driver for feature parsing. * [http://portal.opengeospatial.org/files/?artifact_id=14145 OGC WFS Specification] * [http://www.opengeospatial.org/standards/wfs The OpenGIS Web Feature Service (WFS) Implementation Specification] * [http://www.gdal.org/ogr/ogr_drivertut.html OGR Driver Tutorial] Note : a [http://gdal.org/ogr/drv_wfs.html OGR WFS driver] now exists 6. '''Develop a driver for IBM DB2 and its Spatial Extender''' * [http://www-306.ibm.com/software/data/spatial/db2spatial/ DB2 Spatial Extender] 7. '''GDAL_CALC.PY''' - Development of a simple raster calculator based on Python+GDAL. Use sample: % gdal_calc a=img1.tif b=img2.tif c=img3.tif -calc c=((a+b)/2) Note : a [http://trac.osgeo.org/gdal/browser/trunk/gdal/swig/python/scripts/gdal_calc.py gdal_calc.py] script now exists. 8. '''Multithreading''' - Work to make GDAL and/or OGR threadsafe, and develop a test suite to validate. ''or your own ideas..'' == 2009 Ideas List == 1. '''KML Driver''': Develop an enhanced KML driver using Google's [http://code.google.com/p/libkml/ libkml] library. A new driver based around Google's reference implementation would fix some limitations in the current driver (no multi-geometries, no KMZ support, etc), make it easier to keep the driver up to date as KML evolves, and should generally make it easier for GDAL software to exchange data with Google Earth. Both OGR (vector) and GDAL (raster) KML drivers could be developed. Note : a [http://gdal.org/ogr/drv_libkml.html OGR LIBKML driver] now exists 2. '''OpenEV2''': [http://openev.sourceforge.net/ OpenEV] is a GUI tool for efficient displaying and analyzing geospatial data formats supported by GDAL/OGR (including GeoTIFF, MrSID, ECW, .. ESRI Shape files, ..), it is able to convert between file formats, reproject, crop, display by OpenGL a 3D terrain based on elevation from DEM files on Linux, Windows and Mac. Have a look at [http://openev.sourceforge.net/index.php?page=screenshots screenshots] or [http://fwtools.maptools.org/ try it]. It has almost finished port to GTK 2.0 and GDAL python-ng which needs a bit of work, packaging and improvement, more info at [http://www.nabble.com/OpenEV2-updated-td21101297.html OpenEV2 updated post]. Knowledge: Python, GNU tools, GTK 2.0, Linux and partly C, C++. 3. '''PNG Driver''': Implement efficient PNG driver using libPNG with support for optimization of PNG images exported by GDAL (info: [http://www.gdal.org/gdal_drivertut.html tutorial] + [http://svn.osgeo.org/gdal/trunk/gdal/frmts/png png driver]). You can reuse existing open-source [http://members.ozemail.com.au/~dekker/NEUQUANT.HTML NeuQuant algorithm] for RGBA and RGB export. [http://members.ozemail.com.au/~dekker/NEUQUANT.HTML NeuQuant] is easy-to-use practical demonstration of power of the Kohonen Neural Networks. It's source code can be included into GDAL from [http://members.ozemail.com.au/~dekker/NEUQUANT.C original implementation of the algorithm] and/or from [http://pngnq.sourceforge.net/ pngnq utility]. There are also other open-source tools implementing optimization of PNG which can be reused ([http://advancemame.sourceforge.net/doc-advpng.html AdvPNG], [http://optipng.sourceforge.net/ OptiPNG], [http://pmt.sourceforge.net/pngcrush/ PNGcrush]) or can be a source of inspiration ([http://www.advsys.net/ken/util/pngout.htm PNGOut]). Result should be an improved PNG driver for GDAL together with color quantization functions which will produce png files with optimized file-size. Result of this work is going to be usable in MapServer, GRASS, MapTiler and other GDAL-based projects. Knowledge: C, C++ 4. '''ODBC Driver''': Implement write support for the ODBC driver and include support for MSSQL2008 spatial database. The current ODBC driver should be extended to create or transfer spatial data into the ODBC data sources like Microsoft SQL Server. The driver must have built-in support to auto create the XMIN, YMIN, XMAX and YMAX shape envelope values for the non-spatial databases and the spatial index for the MSSQL2008 spatial databases. (info: [http://www.gdal.org/ogr/drv_odbc.html]). Result of this work is going to be usable in any project using the OGR libraries. Knowledge: C, C++, MSSQL2008 Spatial 5. '''GDAL2Tiles/MapTiler''': Implementation of the coming [http://www.opengeospatial.org/standards/requests/54 OGC WMTS] standard, implementation of the pixel-precise warping (by warped VRT editing), implementation of the [http://www.maptiler.org/google-maps-overlay-opacity-control/ opacity slider control] as one of the official OpenLayers Addins, direct tiling of global maps into Spherical Mercator from WGS84 ([http://code.google.com/p/maptiler/issues/detail?id=6 bug]), support for JPEG tiles, support for cutline clipping, NODATA transparency, bug-fixing of [http://code.google.com/p/maptiler/issues/list open issues]. Code is going to be submitted into GDAL SVN and MapTiler SVN. Project MapTiler (the GUI for GDAL2Tiles) is going to be published as a stable version 1.0 with all binary installers (Windows/Linux/Mac) and with support for localization. Knowledge: Python, JavaScript, GNU tools, partly C, C++ 6. '''PostGIS / WKT Raster Driver''': Implementation of read-only GDAL [http://gdal.org/gdal_drivertut.html driver] for [http://postgis.refractions.net/support/wiki/index.php?WKTRasterHomePage WKT Raster] extension to [http://postgis.refractions.net/ PostGIS]. The WKT Raster is ''is an ongoing project aiming at developing raster support in PostGIS (...) goal is to implement the RASTER type as much as possible like the GEOMETRY type is implemented in PostGIS''. [http://mateusz.loskot.net/?p=291 WKT Raster crash course #1] gives detailed overview of the project background. In short, implementation steps will include parsing of [http://svn.osgeo.org/postgis/spike/wktraster/doc/RFC2-WellKnownBinaryFormat WKB format], define specializations of [http://gdal.org/classGDALDataset.html GDALDataset] and [http://gdal.org/classGDALRasterBand.html GDALRasterBand], implement read operations for bands. The idea behind WKT Raster in GSoC 2009 is to deliver a prototype (or proof of concept) that can be used as a base for further development, so only two raster types are considered: 1 band of [http://gdal.org/gdal_8h.html GDT_Byte] ([http://en.wikipedia.org/wiki/Grayscale Grayscale]), 3 x 1 band of GDT_Byte ([http://en.wikipedia.org/wiki/RGB_color_model RGB]). Knowledge: [http://en.wikipedia.org/wiki/Raster_graphics raster] graphics, basic understanding of [http://en.wikipedia.org/wiki/Well_known_binary Well-Known-Binary]-like formats, [http://www.postgresql.org/docs/8.3/static/libpq.html libpq], C (strong), C++ (basic). 7. '''OGR SQL .NET Data Provider''': Implement a .NET Data Provider inteface for the OGR SQL API. This sample application would allow the user to use OgrSqlDataAdapter to read the result of an OGR SQL query into a DataSet which could be used as the datasource of the bindable .NET controls. The provider would also support transactions and batch queries and read the multiple results into multiple data tables within the same DataSet. The OgrSqlDataReader would provide a convenient way to retrieve the records sequentially for the user. (info: [http://www.gdal.org/ogr/ogr_sql.html]). Result of this work would go to the sample application section of the C# interface. Knowledge: C#, .NET Framework Class Libraries ''or your own ideas..'' inspiration also from: == 2008 Ideas List == These are suggestions. Students are encouraged to come up with their own ideas as well. 1. Implement GeoPNG/GeoJPEG by embedding coordinate system and geotransformation information (possibly in GML) as chunks in PNG and JPEG files (see GML JP2 for a model of how this might be done). * [http://portal.opengeospatial.org/files/?artifact_id=13252 GMLJP2 Specification] * GMLJP2 Code: [http://svn.osgeo.org/gdal/trunk/gdal/gcore/gdaljp2metadata.cpp gdaljp2metadata.cpp] [http://svn.osgeo.org/gdal/trunk/gdal/gcore/gdalgmlcoverage.cpp gdalgmlcoverage.cpp] * [http://trac.osgeo.org/gdal/ticket/1742] was an attempt to provide georeferencing to PNG, GIF and JPEG datasets. The format itself used lacks standardization, but the mechanisms used can be usefull. 2. [http://svn.osgeo.org/gdal/trunk/gdal/frmts/png PNG Driver (using libpng)] * [http://svn.osgeo.org/gdal/trunk/gdal/frmts/jpeg JPEG Driver (using libjpeg)] 3. OGR WFS read (or read/write) driver using existing OGR GML driver for feature parsing. * [http://portal.opengeospatial.org/files/?artifact_id=14145 OGC WFS Specification] * [http://www.opengeospatial.org/standards/wfs The OpenGIS Web Feature Service (WFS) Implementation Specification] * [http://www.gdal.org/ogr/ogr_drivertut.html OGR Driver Tutorial] 4. Implementation of alternative driver for GML 2 and GML 3 using [http://expat.sourceforge.net/ Expat XML Parser] 5. Implementation of read-only WFS driver using GML driver based on the Expat XML Parser. 6. Develop a driver for GeoRSS * [http://georss.org GeoRSS specification] 7. Develop a driver for [http://www.openstreetmap.org/ OpenStreetMap] protocol * [http://wiki.openstreetmap.org/index.php/Protocol OSM Protocol Stack] 8. Develop a driver for IBM DB2 and its Spatial Extender * [http://www-306.ibm.com/software/data/spatial/db2spatial/ DB2 Spatial Extender] 9. Extend [http://gdal.org/ogr/drv_geojson.html GeoJSON] driver with cashing capabilities when accessing remote datasource. 10. Development of Java bindings. 11. GDAL/OGR for Windows CE: porting new drivers 12. Development of [http://en.wikipedia.org/wiki/C_Sharp_%28programming_language%29 C# language] [http://www.swig.org SWIG] bindings for [http://en.wikipedia.org/wiki/.NET_Compact_Framework .NET Compact Framework] and creating test applications for it. 13. Creating an ASP.NET multithreading testbed for the GDAL C# bindings, by using the [http://msdn2.microsoft.com/en-us/library/3dasc8as(VS.80).aspx thread pool] approach. 14. Development of bindings for new programming languages: [http://www.lua.org/ Lua], [http://en.wikipedia.org/wiki/Ada_%28programming_language%29 Ada] ([http://en.wikipedia.org/wiki/GNAT GNAT]), ''put your favorite language here'' 15. Development of GDAL Read/Write Driver for tiles, derived from [http://www.gdal.org/gdal2tiles.html GDAL2Tiles utility]. 16. GDAL2Tiles - support for TMS tiles with global-mercator profile to make overlays with Google Maps, MS Virtual Earth, etc. possible. 17. Extend the HDF5 driver to support writing datasets. This should include an effort to produce HDF5 datasets according to NASA HDF5 metadata conventions where possible. HDF5 is a new generation format expected to be widely used for science data products from NASA and other agencies. 18. GDAL_CALC.PY - Development of a simple raster calculator based on Python+GDAL. Use sample: % gdal_calc a=img1.tif b=img2.tif c=img3.tif -calc c=((a+b)/2) 19. Develop an enhanced KML driver using Google's [http://code.google.com/p/libkml/ libkml] library. A new driver based around Google's reference implementation would fix some limitations in the current driver (no multi-geometries, no KMZ support, etc), make it easier to keep the driver up to date as KML evolves, and should generally make it easier for GDAL software to exchange data with Google Earth. Both OGR (vector) and GDAL (raster) KML drivers could be developed.