| Version 18 (modified by , 16 years ago) ( diff ) |
|---|
GDAL/OGR In CSharp
The GDAL project (primarily Tamas Szekeres) maintains SWIG generated CSharp bindings for GDAL and OGR. Generally speaking the classes and methods mostly match those of the GDAL and OGR C++ classes, but there is currently no CSharp specific documentation beyond this site. The CSharp bindings are also usable from other .NET languages, such as VB .Net.
The CSharp interface has been build upon a common ground as the other SWIG generated wrappers (like Perl, Python, Java, PHP and Ruby). In this regard the class names and class member names along with the method signatures are fairly predestinated and might not follow the conventional .NET naming guidelines. However, one can easily identify the counterpars of the members in the GDAL/OGR API documentation.
The GDAL/OGR CSharp classes use the .NET P/Invoke mechanism for the communication between the managed and unmanaged code. Every class implements the IDisposable interface to control the finalization of the underlying unmanaged memory referenced by every the wrapper class.
Supported platforms
Currently the interface is compilable and supports the various Win32 and Win64 platforms targeting the Microsoft.NET and the MONO framework. The interface is also compilable under the GNU Linux/OSX systems for the MONO framework. The compilation steps for the various platforms have been added to the GDAL buildbot and tested regularly.
Related Documents
- GDAL/OGR CSharp interface versions
- GDAL/OGR CSharp Raster Operations
- GDAL/OGR CSharp Compilation
- Using the GDAL/OGR CSharp interface
Useful Links
- A variety of example programs in CSharp are available at the /swig/csharp/apps folder of the GDAL project tree.
- This projetct make images tiles (Superoverlay method) for Google Earthhttp://www.codeplex.com/gdal2tilescsharp
FWTools
One way to get the CSharp bindings is to use FWTools 1.2.0+ for windows. To use these it should be sufficient to add the assemblies in FWTools\csharp to your project, and to ensure that FWTools\bin is in your path. See FWTools: Open Source GIS Binary Kit for Windows and Linux
