GDCM alternatives and similar libraries
Based on the "Image Processing" category
-
VTK
Open-source, freely available software system for 3D computer graphics, image processing and visualization. [BSD] -
OpenImageIO
Powerful image and texture wrangling library with support for a wide number of common lossy and RAW formats. [Modified BSD] -
OpenMVG (open Multiple View Geometry)
Promoting 3d reconstruction from images through multiple-view geometry algorithms and ready to use pipelines. -
GD
GD Graphics Library, famously used in PHP for image loading/manipulation & thumbnail generation. [custom permissive license, requires mention in user docs] website -
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] -
FreeImage
An open source library that supports popular graphics image formats and others as needed by today's multimedia applications. [GPL2 or GPL3]
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of GDCM or a related project?
|
Monitor and correlate metrics, traces, and logs in one platform. Free 14-day trial.
More from our partner
|
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
More from our team
|
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: