From wayne@helix.nih.gov Tue Feb 1 20:16:31 1994 X-VM-Summary-Format: "%n %*%a %-17.17F %-3.3m %2d %4l/%-5c %I\"%s\"\n" X-VM-Labels: nil X-VM-VHeader: ("Resent-" "From:" "Sender:" "To:" "Apparently-To:" "Cc:" "Subject:" "Date:") nil X-VM-Bookmark: 11 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["499" "Tue" " 1" "February" "1994" "17:23:31" "GMT" "Wayne Rasband" "wayne@helix.nih.gov" "" "15" "Re: multi file tiff example" "^From:" nil nil "2" "1994020117:23:31" "multi file tiff example" (number " " mark " Wayne Rasband Feb 1 15/499 " thread-indent "\"Re: multi file tiff example\"\n") "<2ib9qk$eu@meaddata.meaddata.com>"] nil) Newsgroups: sci.image.processing Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!darwin.sura.net!nih-csl!pico.nimh.nih.gov!user Message-ID: Followup-To: sci.image.processing Organization: NIH References: <2ib9qk$eu@meaddata.meaddata.com> Lines: 15 From: wayne@helix.nih.gov (Wayne Rasband) Sender: postman@alw.nih.gov (AMDS Postmaster) Subject: Re: multi file tiff example Date: Tue, 1 Feb 1994 17:23:31 GMT In article <2ib9qk$eu@meaddata.meaddata.com>, stever@meaddata.com (Steve Rothenberg) wrote: > can anyone point me to a sample TIFF that has multiple pictures in the > file, i.e has multiple IFD's? > > is there an ftp site for tiffs? > Try zippy.nimh.nih.gov, in the /pub/nih-image/stacks directory. The files are MacBinary encoded, so you will probably need a Macintosh to decode them. I know of only two Mac programs (NIH Image and DIP Station) that can read multi-image TIFF files. --wayne From mvivino@helix.nih.gov Wed Feb 2 09:46:06 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["479" "Wed" " 2" "February" "1994" "13:43:13" "GMT" "Mark A. Vivino" "mvivino@helix.nih.gov" "" "15" "Re: Where can I find NCSA Image and NIH Image?" "^From:" nil nil "2" "1994020213:43:13" "Where can I find NCSA Image and NIH Image?" (number " " mark " Mark A. Vivino Feb 2 15/479 " thread-indent "\"Re: Where can I find NCSA Image and NIH Image?\"\n") "<2in4qb$r69@oak.oakland.edu>"] nil) Newsgroups: sci.image.processing Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!darwin.sura.net!nih-csl!mavmac.dcrt.nih.gov!user Message-ID: Followup-To: sci.image.processing Organization: National Institutes of Health References: <2in4qb$r69@oak.oakland.edu> Lines: 15 From: mvivino@helix.nih.gov (Mark A Vivino) Sender: postman@alw.nih.gov (AMDS Postmaster) Subject: Re: Where can I find NCSA Image and NIH Image? Date: Wed, 2 Feb 1994 13:43:13 GMT In article cjd@sun.chem.wayne.edu (Chris Demos) wrote: > I need to locate either (or both) NCSA Image and NIH Image. > Could someone please email me ftp sites where these packages are available? For NIH-Image try zippy.nimh.nih.gov [128.231.98.32] in the /pub/nih-image directory. I think NCSA Image is on this machine also. -- Mark Vivino mvivino@helix.nih.gov Computational Biosciences and Engineering Lab Image Processing Research Section National Institutes of Health From moore@yellow.mmm.com Wed Feb 2 19:28:24 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["450" "" " 2" "February" "1994" "15:10:15" "GMT" "Richard Moore" "moore@yellow.mmm.com" "" "21" "Re: HIPS format to any other formaT??" "^From:" nil nil "2" "1994020215:10:15" "HIPS format to any other formaT??" (number " " mark " Richard Moore Feb 2 21/450 " thread-indent "\"Re: HIPS format to any other formaT??\"\n") "<2ijmkg$o5@s.ms.uky.edu>"] nil) Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-2.peachnet.edu!news-feed-1.peachnet.edu!umn.edu!dawn.mmm.com!mmm.com!moore Newsgroups: sci.image.processing Organization: 3M - St. Paul, MN 55144-1000 US Lines: 21 Message-ID: References: <2ijmkg$o5@s.ms.uky.edu> NNTP-Posting-Host: yellow.mmm.com From: moore@yellow.mmm.com (Richard Moore) Subject: Re: HIPS format to any other formaT?? Date: 2 Feb 94 15:10:15 GMT mani@ms.uky.edu (Rao Surapaneni) writes: >Hi, > I have some images in HIPS format. > Can anyone point me to any utilities which can convert them > to any other format? >thanx >mani >mani@s.ms.uky.edu ftp to ftp.x.org and get the portable bitmap utilities from the /contrib directory. This are a set up Unix functions to convert image file formats to the portable bitmap format and back to other image formats. Richard Moore rjmoore@mmm.com From ceder@gdwest.gd.com Sat Feb 5 15:31:01 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1297" "" " 4" "February" "1994" "11:47:13" "-0800" "Gary D. Cederquist" "ceder@gdwest.gd.com" "<2iu8o1$lfc@gdwest.gd.com>" "27" "Re: File Formats - Recommendations anyone?" "^From:" nil nil "2" "1994020419:47:13" "File Formats - Recommendations anyone?" (number " " mark " Gary D. Cederquis Feb 4 27/1297 " thread-indent "\"Re: File Formats - Recommendations anyone?\"\n") ""] nil) Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-2.peachnet.edu!ukma!nic.hookup.net!yeshua.marcam.com!news.kei.com!sol.ctr.columbia.edu!ucsnews!gdwest.gd.com!gdwest.gd.com!not-for-mail Newsgroups: sci.image.processing Organization: GDE System Inc. Lines: 27 Message-ID: <2iu8o1$lfc@gdwest.gd.com> References: NNTP-Posting-Host: gdwest From: ceder@gdwest.gd.com (Gary D Cederquist GDE) Subject: Re: File Formats - Recommendations anyone? Date: 4 Feb 1994 11:47:13 -0800 In article , D.M.P. Hagyard ESE PG wrote: >Hello out there, > I am shortly to be writing a small test package for manipulating >images. I would like to be able to be able to transfer my C programs >between the DEC and SUN platforms. What file format would be best to use >to avoid problems with different architectures. I would have small and >reasonably sized images in 1 - 8 bits per pixel formats, exclusively >in monochrome, and would probably like to use one of the formats supported >by xview et al. What would be the easiest to use for an input/output >format on the program. I would pick up a copy of XV 3.0 from your favorite FTP site. It is an image manipulation product supporting multiple formats. It is shareware at $25 a copy, but it's well worth it. You probably won't have to write your own image manipulation routines with XV available, but you could extend its functionality. If I were writing something from scratch I would probably pick GIF. Seems everyone is using it these days though I'm not sure where there's a support library for GIF. Use archie to look for "xv-3.00a*". Hope I've helped. -- Gary D. Cederquist GDE Systems Inc ceder@gdwest.gd.com San Diego, CA From ctyau@cs.cuhk.hk Tue Feb 8 10:21:53 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["917" "Tue" " 8" "February" "1994" "12:36:06" "GMT" "YAU Chor Tung ~{SN4!6+~}" "ctyau@cs.cuhk.hk" "" "28" "Re: HIPS format to any other formaT??" "^From:" nil nil "2" "1994020812:36:06" "HIPS format to any other formaT??" (number " " mark " YAU Chor Tung ~{S Feb 8 28/917 " thread-indent "\"Re: HIPS format to any other formaT??\"\n") "<2ijmkg$o5@s.ms.uky.edu>"] nil) Newsgroups: sci.image.processing Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-1.peachnet.edu!emory!sol.ctr.columbia.edu!howland.reston.ans.net!usenet.ins.cwru.edu!lerc.nasa.gov!news.larc.nasa.gov!saimiri.primate.wisc.edu!hpg30a.csc.cuhk.hk!eng_ser1!ctyau Message-ID: Organization: Engineering Faculty, The Chinese U. of Hong Kong References: <2ijmkg$o5@s.ms.uky.edu> Lines: 28 From: ctyau@cs.cuhk.hk (YAU Chor Tung ~{SN4!6+~}) Sender: news@eng_ser1.ie.cuhk.hk Subject: Re: HIPS format to any other formaT?? Date: Tue, 8 Feb 1994 12:36:06 GMT mani@ms.uky.edu (Rao Surapaneni) writes: >Hi, > I have some images in HIPS format. > Can anyone point me to any utilities which can convert them > to any other format? >thanx >mani >mani@s.ms.uky.edu There is a utility program hipstotiff within the HIPS package that converts HIPS format image file to 24bit tiff images file. There is also a tifftohips that do the reverse. There are many utility programs that converts tiff to other formats and vice versa. There is also a utility program stripheader within the HIPS package that strip off the image header in HIPS format image, resulting in raw pixel data that can be read into Matlab or IMSL/IDL. -- | YAU, Chor Tung ~{SN4!6+~}, ctyau@cs.cuhk.hk | | M. Phil. student, (852)609-8395 | | Computer Science Department, 905, HSH Eng. Bldg. | | The Chinese University of Hong Kong. | From kutner@acsu.buffalo.edu Fri Feb 11 13:02:27 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1429" "Fri" "11" "February" "1994" "16:37:42" "GMT" "Andrew C. Kutner" "kutner@acsu.buffalo.edu" "" "31" "Re: erdas (sic) satellite image file format" "^From:" nil nil "2" "1994021116:37:42" "erdas (sic) satellite image file format" (number " " mark " Andrew C. Kutner Feb 11 31/1429 " thread-indent "\"Re: erdas (sic) satellite image file format\"\n") "<2jbukb$rki@dlsn31>"] nil) Newsgroups: sci.image.processing Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!corpgate!news.utdallas.edu!convex!cs.utexas.edu!math.ohio-state.edu!sol.ctr.columbia.edu!news.kei.com!ub!acsu.buffalo.edu!kutner Message-ID: Originator: kutner@skat.acsu.buffalo.edu Nntp-Posting-Host: skat.acsu.buffalo.edu Organization: UB References: <2jbukb$rki@dlsn31> Lines: 31 From: kutner@acsu.buffalo.edu (Andrew C Kutner) Sender: nntp@acsu.buffalo.edu Subject: Re: erdas (sic) satellite image file format Date: Fri, 11 Feb 1994 16:37:42 GMT If the Erdas file is in the older 7.5 format, I believe the images have only a 128 byte header on the front of the image, and then some trailing information that's limited to 1024 bytes. I worked with those files too long ago to remember the specific numbers, but I remember that there wasn't a huge amount of extra data added to the images. If you already know the size, i.e. scanned or satellite, then just play around with getting rid of the header size... 128,256,512 or 1024 bytes. It shouldn't be that difficult because you should see a shift in the picture of XX number of bytes when you view the picture. With any image viewer, ex. xv, you can get a zoom of a section of the image (the upper left) and then use the pixel numbers to figure the offset. The offset is the same for all images under the 7.5 version of the software. Andy ------------------------------------------------------------------- Andrew Kutner Unix Technical Support kutner@acsu.buffalo.edu Computing and Information Technology Voice: (716) 829-2096 State University of New York at Buffalo Fax: (716) 645-5972 201 Computing Center, Buffalo, NY 14260 ------------------------------------------------------------------- -- ------------------------------------------------------------------- Andrew Kutner Unix Technical Support kutner@acsu.buffalo.edu Computing and Information Technology From fogel@geog.ucsb.edu Sat Feb 12 22:12:29 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["3194" "" "12" "February" "1994" "20:25:05" "GMT" "fogel@geog.ucsb.edu" "fogel@geog.ucsb.edu" "<2jjdv2$69l@hub.ucsb.edu>" "63" "Re: erdas (sic) satellite image file format" "^From:" nil nil "2" "1994021220:25:05" "erdas (sic) satellite image file format" (number " " mark " fogel@geog.ucsb.e Feb 12 63/3194 " thread-indent "\"Re: erdas (sic) satellite image file format\"\n") ""] nil) Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!corpgate!news.utdallas.edu!wupost!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!library.ucla.edu!nntp.ucsb.edu!eos.crseo.ucsb.edu!fogel Newsgroups: sci.image.processing Organization: University of California, Santa Barbara Lines: 63 Distribution: world Message-ID: <2jjdv2$69l@hub.ucsb.edu> References: <2jbukb$rki@dlsn31> NNTP-Posting-Host: crseo-gw.ucsb.edu fcc: flame From: fogel@geog.ucsb.edu Sender: fogel@eos.crseo.ucsb.edu (-J. N. Fogel(Joel Michaelson.)) Subject: Re: erdas (sic) satellite image file format Date: 12 Feb 1994 20:25:05 GMT In article , kutner@acsu.buffalo.edu (Andrew C Kutner) writes: |> |> |> If the Erdas file is in the older 7.5 format, I believe the images have only |> a 128 byte header on the front of the image, and then some trailing information |> that's limited to 1024 bytes. |> |> I worked with those files too long ago to remember the specific numbers, but |> I remember that there wasn't a huge amount of extra data added to the images. |> |> If you already know the size, i.e. scanned or satellite, then just play around |> with getting rid of the header size... 128,256,512 or 1024 bytes. It shouldn't |> be that difficult because you should see a shift in the picture of XX number |> of bytes when you view the picture. With any image viewer, ex. xv, you can |> get a zoom of a section of the image (the upper left) and then use the pixel |> numbers to figure the offset. |> |> The offset is the same for all images under the 7.5 version of the software. |> |> |> Andy |> ------------------------------------------------------------------- |> Andrew Kutner Unix Technical Support |> kutner@acsu.buffalo.edu Computing and Information Technology |> Voice: (716) 829-2096 State University of New York at Buffalo |> Fax: (716) 645-5972 201 Computing Center, Buffalo, NY 14260 |> ------------------------------------------------------------------- |> -- |> |> ------------------------------------------------------------------- |> Andrew Kutner Unix Technical Support |> kutner@acsu.buffalo.edu Computing and Information Technology The "lan" format does indeed have a 128-byte header. The images are stored in 512-byte records. This means the end of the *.lan file is essentially zero-filled unless bands*lines*samples + 128 is divides "evenly" by 512. The information on LAN files is detailed in the ERDAS "Field Guide." Perhaps Image Alchemy (?) or a similar package deals with *.lan files. Keep in mind that the file structure dates back to the early INTEL installations. Some byte-swapping may be necessary to make sense of the imagery (e.g., no. of bands, lines, ...). I have some code to read single band lan files using xv-2.21 which is not very elegant. However, you can export to other xv image formats. I have not tried to port it to xv-3.0x(?). Perhaps someone else has done this? Depending on interest I make this avail. to one or many. *Flame on* I am not an ERDAS fan. The registration/rectification routines in ver. 7.5 (lrectify and nrectify) have produced different results in the resampling stage of the transformation process with a first-order polynomial fit (approximation) and nearest neighbor resampling. It only gets worse with their new product, "Imagine." Now I have three "different" images. Darn if inconsistent information on image origins didn't make it worse (v8.01). This will be documented in a report for a DOE subcontractor in the very near future. The company was, oh, so responsive to my queries ;). Where does product liability begin and end? Did YOUR results depend on some measure of radiometric fidelity? *Flame off* -- David N. Fogel fogel@geog.ucsb.edu From DJA@cardio.hosp.wisc.edu Thu Feb 24 11:49:13 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["393" "" "23" "February" "1994" "16:09:34" "GMT" "DJA@cardio.hosp.wisc.edu" "DJA@cardio.hosp.wisc.edu" "<2kfv3u$e1p@news.doit.wisc.edu>" "10" "Re: WANTED: ACR-NEMA file format" "^From:" nil nil "2" "1994022316:09:34" "WANTED: ACR-NEMA file format" (number " " mark " DJA@cardio.hosp.w Feb 23 10/393 " thread-indent "\"Re: WANTED: ACR-NEMA file format\"\n") "<2kdioa$alp@nntp.ucs.ubc.ca>"] nil) Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-2.peachnet.edu!gatech!usenet.ins.cwru.edu!lerc.nasa.gov!news.larc.nasa.gov!saimiri.primate.wisc.edu!news.doit.wisc.edu!news Newsgroups: sci.image.processing Organization: University of Wisconsion, Cardiology Section Lines: 10 Distribution: world Message-ID: <2kfv3u$e1p@news.doit.wisc.edu> References: <2kdioa$alp@nntp.ucs.ubc.ca> NNTP-Posting-Host: cardio.hosp.wisc.edu X-News-Reader: VMS NEWS v1.25 In-Reply-To: keith@mspc4.msmri.med.ubc.ca's message of 22 Feb 1994 18:26:18 GMT From: DJA@cardio.hosp.wisc.edu () Subject: Re: WANTED: ACR-NEMA file format Date: 23 Feb 1994 16:09:34 GMT In <2kdioa$alp@nntp.ucs.ubc.ca> keith@mspc4.msmri.med.ubc.ca writes: > I am trying to get a copy of the ACR-NEMA file > format for medical images. Does any one know > where I can get a copy. If some one could > point me to a copy on the net, that would be > even better. > try FTPing to FTP.XRAY.HMC.PSU.EDU and look in /pub/dicom. The DICOM standard supercedes the ACR-NEMA documents. From dsc@xray.hmc.psu.edu Thu Feb 24 11:49:17 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["72" "" "23" "February" "1994" "20:12:10" "GMT" "David S. Channin" "dsc@xray.hmc.psu.edu" "<2kgdaq$svj@genesis.ait.psu.edu>" "4" "Re: WANTED: ACR-NEMA file format" "^From:" nil nil "2" "1994022320:12:10" "WANTED: ACR-NEMA file format" (number " " mark " David S. Channin Feb 23 4/72 " thread-indent "\"Re: WANTED: ACR-NEMA file format\"\n") "<2kfv3u$e1p@news.doit.wisc.edu>"] nil) Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!caen!destroyer!newsxfer.itd.umich.edu!gatech!howland.reston.ans.net!news2.cac.psu.edu!news.cac.psu.edu!chasse-spleen!dsc Newsgroups: sci.image.processing Organization: Dept. of Radiology, Hershey Medical Center, Hershey PA Lines: 4 Distribution: world Message-ID: <2kgdaq$svj@genesis.ait.psu.edu> References: <2kfv3u$e1p@news.doit.wisc.edu> Reply-To: dsc@xray.hmc.psu.edu NNTP-Posting-Host: chasse-spleen.xray.hmc.psu.edu From: dsc@xray.hmc.psu.edu (David S. Channin) Subject: Re: WANTED: ACR-NEMA file format Date: 23 Feb 1994 20:12:10 GMT Actually the ftp tree has changed: Look in /dicom_docs/dicom_3.0. dsc From keith@mspc4.msmri.med.ubc.ca Thu Feb 24 11:49:23 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["408" "" "23" "February" "1994" "21:41:19" "GMT" "Keith S. Cover" "keith@mspc4.msmri.med.ubc.ca" "<2kgihv$g8t@nntp.ucs.ubc.ca>" "18" "Re: WANTED: ACR-NEMA file format" "^From:" nil nil "2" "1994022321:41:19" "WANTED: ACR-NEMA file format" (number " " mark " Keith S. Cover Feb 23 18/408 " thread-indent "\"Re: WANTED: ACR-NEMA file format\"\n") "<2kgdaq$svj@genesis.ait.psu.edu>"] nil) Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!corpgate!news.utdallas.edu!convex!cs.utexas.edu!howland.reston.ans.net!europa.eng.gtefsd.com!library.ucla.edu!news.mic.ucla.edu!unixg.ubc.ca!not-for-mail Newsgroups: sci.image.processing Organization: Physics, University of British Columbia Lines: 18 Distribution: world Message-ID: <2kgihv$g8t@nntp.ucs.ubc.ca> References: <2kfv3u$e1p@news.doit.wisc.edu> <2kgdaq$svj@genesis.ait.psu.edu> Reply-To: keith@msmri.med.ubc.ca (Keith S Cover) NNTP-Posting-Host: mspc4.msmri.med.ubc.ca X-Newsreader: IBM NewsReader/2 v1.00 From: keith@mspc4.msmri.med.ubc.ca (Keith S Cover) Subject: Re: WANTED: ACR-NEMA file format Date: 23 Feb 1994 21:41:19 GMT In <2kgdaq$svj@genesis.ait.psu.edu>, dsc@xray.hmc.psu.edu (David S. Channin) writes: >Actually the ftp tree has changed: Look in /dicom_docs/dicom_3.0. > >dsc > It turns out there is a USENET group dedicated to DICOM, which is the new name for ACR-NEMA. The group is comp.protocols.dicom. It even has a FAQ. Thanks for all the help. Keith S Cover Physics, UBC Vancouver, Canada keith@msmri.med.ubc.ca From rjh@world.std.com Thu Feb 24 11:49:32 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["439" "Wed" "23" "February" "1994" "23:04:22" "GMT" "Robert J. Horn" "rjh@world.std.com" "" "9" "Re: WANTED: ACR-NEMA file format" "^From:" nil nil "2" "1994022323:04:22" "WANTED: ACR-NEMA file format" (number " " mark " Robert J. Horn Feb 23 9/439 " thread-indent "\"Re: WANTED: ACR-NEMA file format\"\n") "<2kgdaq$svj@genesis.ait.psu.edu>"] nil) Newsgroups: sci.image.processing Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!corpgate!news.utdallas.edu!convex!cs.utexas.edu!uunet!world!rjh Message-ID: Organization: The World Public Access UNIX, Brookline, MA References: <2kfv3u$e1p@news.doit.wisc.edu> <2kgdaq$svj@genesis.ait.psu.edu> Lines: 9 From: rjh@world.std.com (Robert J Horn) Subject: Re: WANTED: ACR-NEMA file format Date: Wed, 23 Feb 1994 23:04:22 GMT Also, look specifically at Parts 10, 11(arriving soon), 12(not there yet) for definition of the formats that are proposed for removable media. The other parts address the networking usage and the basic common objects and their encoding. My experience with novices to DICOM V3.0 is that the best start is with the conformance statements (to get a feel for DICOM) and then the other detailed parts. Rob Horn horn@temerity.polaroid.com