T O P I C R E V I E W |
Dave |
Posted - Jan 07 2014 : 06:59:17 Hello,
Having some trouble with a Dicom Tag, if anybody can help me, feel free.
I create a TImageEnView object.
If I do nothing the tag 0002,0010 is '1.2.840.10008.1.2.1 ', the problem is the space in the back, this is the reason why I can't read the dicom file in DBSWIN. if I set the tag to '1.2.840.10008.1.2.1' or (as a test) to '1.2.840.10008.1.2.1666' then I still have the same problem, after saving as DICOM file I still have '1.2.840.10008.1.2.1 ' (with blanc in the back).
Part of code
aImage := TImageEnView.Create(nil);
aImage.IO.Params.DICOM_TagsSetTagString($0002,$0010, AnsiString('1.2.840.10008.1.2.1'));
aImage.IO.SaveToFileDICOM( aFileName); |
5 L A T E S T R E P L I E S (Newest First) |
xequte |
Posted - Apr 15 2014 : 14:50:46 Yes, tag types need to have an even length for the Dicom standard, but some types (Unique identifiers and byte streams) should be padded with #0 rather than spaces
Nigel Xequte Software www.xequte.com nigel@xequte.com
|
jwest |
Posted - Apr 15 2014 : 07:27:12 If I remember the dicom standard says you need to have even length in that tags. The extra space on trail is to obey the dicom standard. |
xequte |
Posted - Jan 10 2014 : 02:32:47 Hi Dave
It will be released in February.
If you need the fix sooner please email me and I will forward the source changes.
Nigel Xequte Software www.xequte.com nigel@xequte.com
|
Dave |
Posted - Jan 09 2014 : 04:43:49 Thanx for the reply.
I know it's asked a lot but is it posible to let me know when this release will be available, or to provide a hotfix because the project I'm doing is for the Belgium army and like every project there's a deadline. Don't worry, we're not talking weapens but tooth ;-)
Grtz,
Dave |
xequte |
Posted - Jan 08 2014 : 17:38:34 Hi
Upon invesigation, this is due to our misinterpretation of a Dicom standard. We will address for v5.0.6.
Nigel Xequte Software www.xequte.com nigel@xequte.com
|