GDCM alternatives and similar libraries

Based on the "Image Processing" category.
Alternatively, view GDCM alternatives based on common mentions on social networks and blogs.

OpenCV

10.0 9.6 L1 GDCM VS OpenCV

Open Source Computer Vision Library
tesseract-ocr

9.9 8.5 L1 GDCM VS tesseract-ocr

Tesseract Open Source OCR Engine (main repository)

Free Global Payroll designed for tech teams

Building a great tech team takes more than a paycheck. Zero payroll costs, get AI-driven insights to retain best talent, and delight them with amazing local benefits. 100% free and compliant.

Promo try.revelo.com

libvips

8.8 0.0 L3 GDCM VS libvips

A fast image processing library with low memory needs.
OpenMVG (open Multiple View Geometry)

8.6 0.0 GDCM VS OpenMVG (open Multiple View Geometry)

open Multiple View Geometry library. Basis for 3D computer vision and Structure from Motion.
VTK

7.8 9.6 L1 GDCM VS VTK

Mirror of Visualization Toolkit repository
OpenImageIO

7.0 0.0 L1 GDCM VS OpenImageIO

Reading, writing, and processing images in a wide variety of file formats, using a format-agnostic API, aimed at VFX applications.
OpenEXR

6.9 0.0 L1 GDCM VS OpenEXR

The OpenEXR project provides the specification and reference implementation of the EXR file format, the professional-grade image storage format of the motion picture industry.
ITK

6.7 9.4 L2 GDCM VS ITK

Insight Toolkit (ITK) -- Official Repository. ITK builds on a proven, spatially-oriented architecture for processing, segmentation, and registration of scientific images in two, three, or more dimensions.
Magick++

6.2 5.4 GDCM VS Magick++

Go binding to ImageMagick's MagickWand C API
CImg

6.1 0.0 GDCM VS CImg

The CImg Library is a small and open-source C++ toolkit for image processing
GD

5.6 0.0 L2 GDCM VS GD

GD Graphics Library
Video++

4.9 0.0 L2 GDCM VS Video++

Video++, a C++14 high performance video and image processing library.
VIGRA

4.6 6.5 L1 GDCM VS VIGRA

a generic C++ library for image analysis
hiptext

4.4 0.0 L3 GDCM VS hiptext

Turn images into text better than caca/aalib
SVG++

4.3 0.0 L3 GDCM VS SVG++

C++ SVG library
Boost.GIL

3.7 0.0 L3 GDCM VS Boost.GIL

Boost.GIL - Generic Image Library | Requires C++14 since Boost 1.80
CxImage

3.2 0.0 L1 GDCM VS CxImage

An image processing and conversion library to load, save, display, transform BMP, JPEG, GIF, PNG, TIFF, MNG, ICO, PCX, TGA, WMF, WBMP, JBG, J2K images. [zlib]
SAIL

3.1 10.0 GDCM VS SAIL

The missing small and fast image decoding library for humans (not for machines) ⛵ https://sail.software
FreeImage

2.4 0.0 L2 GDCM VS FreeImage

A custom distribution of FreeImage, with a CMake-based build system. Used by the Athena Game Framework.
FLOP

1.9 0.0 GDCM VS FLOP

FLOꟼ - An MIT-licensed image viewer equipped with a GPU-accelerated perceptual image diffing algorithm based on ꟻLIP
ULIS

1.8 6.7 GDCM VS ULIS

Utility Library for Imaging Systems
DCMTK

- GDCM VS DCMTK

DICOM Toolkit.

* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.

Do you think we are missing an alternative of GDCM or a related project?

Add another 'Image Processing' Library

Popular Comparisons

README

This is the source code of GDCM. It is available from sf.net website. Official GIT repository is at:

https://sourceforge.net/p/gdcm/gdcm/

For a general introduction/features/limitations/requirement please refer to

http://gdcm.sourceforge.net/

Just a quick note on the build process of GDCM. GDCM build process make use of the cmake software(*). This allow us:

To get rid of the autoconf/autotools insanity
Transparently generate Unix Makefiles, NMake Makefiles, VS8/9/10 Solution, Xcode projects, etc.
Automatic nightly testing, one of the most important things for a robust library/software development process. GDCM development is develop based on the XP definition, and to preserve backward compatibility make sure that code is working from one release to another: each night we configure, we build and we test GDCM. The result are then sent to the dashboard located at:

https://open.cdash.org/index.php?project=GDCM

A continuous dashboard also makes sure that any commit did not introduce any error on another platform, a warning or a broken test...

Therefore you should be able to use GDCM from the bleeding edge without knowing too much about what is going on. All you need to do is have a look at the GDCM dashboard, and if your platform is 'green' then you can update your git copy and compile safely knowing that there is very little chance that something won't work. Cheers !

(*) http://www.cmake.org for more information

For more help you can go online in the GDCM Wiki: