GDCM alternatives and similar libraries
Based on the "Image Processing" category.
Alternatively, view GDCM alternatives based on common mentions on social networks and blogs.
-
-
-
-
OpenMVG (open Multiple View Geometry)
open Multiple View Geometry library. Basis for 3D computer vision and Structure from Motion. -
-
OpenImageIO
Reading, writing, and processing images in a wide variety of file formats, using a format-agnostic API, aimed at VFX applications. -
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
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. -
-
-
-
-
-
-
-
AVIR
High-quality pro HDR image resizing / scaling C++ library, including a very fast, precise, SIMD Lanczos resizer (header-only C++) -
-
-
CxImage
DISCONTINUED. 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] -
FreeImage
A custom distribution of FreeImage, with a CMake-based build system. Used by the Athena Game Framework. -
-
FLOP
FLOꟼ - An MIT-licensed image viewer equipped with a GPU-accelerated perceptual image diffing algorithm based on ꟻLIP
InfluxDB – Built for High-Performance Time Series Workloads
* 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?
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
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:
In Particular:
- http://gdcm.sourceforge.net/wiki/index.php/GDCM_Release_2.0
- http://gdcm.sourceforge.net/wiki/index.php/FAQ
And a page describing each tool can be found at:
Eg:
Need VTK: