<!#######################################################################>
<H1>Gdcm Home Page</H1>
<HR size="1"><ADDRESS style="align: right;"></ADDRESS>
+<blink>Note for Google users : </blink><br>
+If you don't see in the left part of your screen
+ the blue 'side bar', <br>
+ starting with 'News', 'Licence', 'Documentation',
+ 'Download', etc better click on : </br>
+ <a
+ href="http://www.creatis.insa-lyon.fr/Public/Gdcm/">
+ http://www.creatis.insa-lyon.fr/Public/Gdcm/ </a> <br>
+
+<HR size="1"><ADDRESS style="align: right;"></ADDRESS>
+<br><br><br>
+
+<H2>(Important note for ITK users)</H2>
+
+ <UL>
+ <LI> ITK (Insight ToolKit) still uses by default gdcm 1.2.x, but can be used with a system installed gdcm 2.x
+ <LI> Current gdcm 1.x version is 1.3.x
+ </UL>
+
+<H2>(Important note for new DICOM users)</H2>
+ <UL>
+ <LI> An other version, called <a href="http://gdcm.sourceforge.net">gdcm2</a> exists, an is a complete ground up rewrite of GDCM 1.x.
+ (have a look at <a href="http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=GDCM_Release_2.0">
+ http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=GDCM_Release_2.0
+ </a>)</br>
+ If you are a new DICOM user, better use gdcm2, because its structure will allow much more features than gdcm1.x does (it's almost exclusively 'image oriented'). gdcm2 is wrapped in python, C# and Java.
+ </UL>
+
+<br><br><br>
+
+
Gdcm is yet another C++ library dedicated to reading/parsing and writing
<A HREF="http://medical.nema.org/">Dicom</A> medical files.
<UL>
<LI>ACR-NEMA version 1 and 2
</LI>
- <LI>Dicom version 3.0 (including various encodings of jpeg, RLE).
+ <LI>Dicom version 3.0 (including various encodings of JPEG -lossless and
+ lossy-, RLE).
Please refer to
<A HREF="ConformanceSummary.html">gdcm conformance summary</A>
for more details.
- <LI>Papyrus V2 and V3 file headers are readable; the user will have to use low level
-accessors if he wants to get the image pixels -sorry-
+ <LI>Papyrus V2 and V3 file headers are readable; the user will have to use
+ low level accessors if he wants to get the image pixels -sorry-.
</LI>
</UL>
+<LI> gdcm includes a lot of heuristics that allow reading all the
+ 'exotic' files (headers with oddities) we had to deal with.<BR>
+ Any king of 'exotic' Dicom file is welcome, to help us to improve our
+ library.
+</LI>
</LI>
<LI>gdcm is distributed with
<A HREF="License.html">Berkeley-like license</A>.
</LI>
+<LI>gdcm is cross platform (it compiles with gcc 2.95, 2.96, 3.0.x, 3.2.x,
+ 3.3.x, 3.4.x, 4.0.x, 4.1.x , icc , cc (SunOS), VisualC++, Borland,
+ nmake... )
+</LI>
+<LI> gdcm has a nightly Dashboard (the whole lib is checked every night)
+</LI>
<LI>gdcm targets both GNU/Un*ces and Windows/VC++
(refer to
<A HREF="Installation.html#gdcmRequirements">requirements</A>
</LI>
<LI>gdcm comes with a
<A HREF="http://public.kitware.com/VTK">VTK</A>
- shallow wrapper class vtkGdcmReader (refer to
+ shallow wrapper class <TT>vtkGdcmReader</TT> (refer to
<A HREF="VtkGdcm.html">VtkGdcm</A>)
to ease the burden of VTK users,
<LI>gdcm also comes with
<UL>
<LI>the Dicom network file exchange protocol (Query/Retrieve),
</LI>
-<LI>the Dicom media storage formats (well ... it knows about the DICOMDIR
--reading and writing- and its parts PATIENT, STUDY, SERIES, IMAGE)
+<LI>the Dicom media storage formats (well ... it knows about the
+ <TT>DICOMDIR</TT> -reading and writing- and its parts <TT>PATIENT</TT>,
+ <TT>STUDY</TT>, <TT>SERIES</TT>, <TT>IMAGE</TT>)
</LI>
<LI>Print, Verification
</LI>
<UL>
<LI>the integration of (optional) overlays on image.
</li>
- <LI>a support to write files according to the
- <A HREF="ConformanceSummary.html">various classical Jpeg encodings</A>
- (only read methods are provided)
- </li>
- <LI>a support to deal with JPEG 2000 encodings</A>
- </li>
+ <LI> ...
+ </li>
</UL>
Gdcm also still needs
<UL>
Dicom file editor.
</LI>
</UL>
+
+<!###################################>
+<UL>
</UL>
<HR size="1"><ADDRESS style="align: right;"></ADDRESS>
git://git.creatis.insa-lyon.fr / gdcm.git / blobdiff