From news.alpha.net!news.mathworks.com!gatech!news.sprintlink.net!noc.netcom.net!netcom.com!jdm Sat Jun 10 11:31:33 1995 Newsgroups: comp.graphics,comp.answers,news.answers Path: news.alpha.net!news.mathworks.com!gatech!news.sprintlink.net!noc.netcom.net!netcom.com!jdm From: jdm@netcom.com Subject: Graphics File Formats FAQ (Part 3 of 4): Where to Get File Format Specifications Message-ID: Followup-To: poster Summary: This document answers many of the most frequently asked questions about graphics file formats on Usenet. Keywords: FAQ, GRAPHICS, FORMAT, IMAGE Sender: jdm@netcom9.netcom.com Supersedes: Reply-To: jdm@netcom.com (James D. Murray) Organization: None Whatsoever References: Date: Thu, 1 Jun 1995 16:01:31 GMT Approved: news-answers-request@MIT.EDU Expires: Sat, 1 Jul 1995 16:01:17 GMT Lines: 1579 Xref: news.alpha.net comp.graphics:77823 comp.answers:12191 news.answers:45354 Posted-By: auto-faq 3.1.1.2 Archive-name: graphics/fileformats-faq/part3 Posting-Frequency: monthly Last-modified: 01Jun95 This FAQ (Frequently Asked Questions) list contains information on graphics file formats, including, raster, vector, metafile, Page Description Language, 3D object, animation, and multimedia formats. This FAQ is divided into four parts, each covering a different area of graphics file format information: Graphics File Formats FAQ: General Graphics Format Questions (Part 1 of 4) Graphics File Formats FAQ: Image Conversion and Display Programs (Part 2 of 4) Graphics File Formats FAQ: Where to Get File Format Specifications (Part 3 of 4) Graphics File Formats FAQ: Tips and Tricks of the Trade (Part 4 of 4) Please email contributions, corrections, and suggestions about this FAQ to jdm@netcom.com. Relevant information posted to newsgroups will not automatically make it into this FAQ. -- James D. Murray ;-{)>>>> ---------------------------------------------------------------------- Subject: 0. Contents of Where to Get File Format Specifications Subjects marked with are new to this FAQ. Subjects marked with have been updated since the last release of this FAQ. I. General questions about this FAQ 0. Maintainer's Comments 1. What's new in this latest FAQ release? II. Where to Get File Format Specifications 0. BMP - Windows Bitmap Format 1. CALS - Computer Aided Acquisition and Logistics Support Raster Format 2. CDF - Cyberspace Description Format 3. CGM - Computer Graphics Metafile 4. DEM - Digital Elevation Model 5. DLG - Digital Line Graph 6. DXF - Autodesk Drawing Exchange Format 7. EPS - Encapsulated PostScript 8. FBM - Fuzzy Bitmap 9. FFIVW - File Format for the Interchange of Virtual Worlds 10. GIF - Graphics Interchange Format 11. GKS - Graphics Kernel System 12. HPGL - Hewlett-Packard Graphics Language 13. HPPCL - Hewlett-Packard Printer Control Language 14. IGES - Initial Graphics Exchange Specification 15. IMJ - Image JPEG 16. JFIF - JPEG File Interchange Format 17. MGF - Materials and Geometry Format 18. MIFF - Magick Image File Format 19. NAPLPS - North American Presentation Layer Protocol Syntax 20. NFF - Neutral File Format 21. NFF - WorldToolKit Neutral File Format 22. NITF - National Imagery Transmission Format 23. OFF - Object File Format 24. PBM - Portable Bitmap 25. PCX - ZSoft Paint 26. PDS - Planetary Data Systems Format 27. PGM - Portable Greymap 28. PIC - Pegasus Imaging Corporation Format 29. PNG - Portable Network Graphics 30. PPM - Portable Pixmap 31. POL - InnovMetric Software Polygon Models Format 32. POV - Persistence of Vision Raytracing 33. RAD - Radience 34. RAS - Sun Rasterfile 35. RAY - Rayshade 36. RIB - Renderman Interface Bytestream 37. RIFF - Microsoft Resource Interchange File Format 38. RIX - ColoRIX Image File 39. SDML - Spacial Data Modeling Language 40. SHG - Segmented Hyper-Graphic 41. STL - Stereolithography Interface Format 42. TGA - Truevision (Targa) File Format 43. TIFF - Tag Image File Format 44. URT - Utah Raster Toolkit 45. VICAR2 - Planetary File Format 46. VIFF - Visualization Image File Format 47. VPF - Vector Product Format 48. VRML - Virtual Reality Modeling Language 49. XBM - X BitMap 50. WebOOGL - Web Object Oriented Graphics Library 51. WMF - Window Meta File 52. WPG - WordPerfect Graphics Metafile 53. XPM - X PixMap 54. XWD - X Window Dump III. Kudos and Assertions 0. Acknowledgments 1. About The Author 2. Disclaimer 3. Copyright Notice ------------------------------ Subject: I. General questions about this FAQ ------------------------------ Subject: 0. Maintainer's Comments One of the reasons you are looking through this FAQ collection is most likely to locate the specification for one or more graphics file formats. That assumption on my part makes this file one of the most important parts of the Graphics File Formats FAQ collection. I therefore wish to make this section as complete as possible. If you have any suggestions for formats to include then please email me at jdm@netcom.com and let me know! And it looks as though I'll be in the O'Reilly & Associates booth at SIGGRAPH in Los Angles on August 8th, 9th, and 10th. I'll be the long-haired computer nerd with the long, braided beard. ;-{)>>>> ------------------------------ Subject: 1. What's new in this latest FAQ release? o Nine new file format specification whereabouts added! o More PNG information added (again!) ------------------------------ Subject: II. Where to Get File Format Specifications This section contains an alphabetical listing of file formats, the names of the creators/caretakers, and where to obtain the official specifications, and a brief description of each format. ------------------------------ Subject: 0. BMP - Windows Bitmap Format BMP is the native bitmap file format of the Microsoft Windows environment. It efficiently stores mapped or unmapped RGB graphics data with pixels 1-, 4-, 8-, or 24-bits in size. Data may be stored raw or compressed using a 4-bit or 8-bit RLE data compression algorithm. BMP is an excellent choice for a simple bitmap format which supports a wide range of RGB image data. The BMP format was created and is maintained by Microsoft Corporation: Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 Voice: 206.882.8080 Fax: 206.936.7329 BBS: 206.637.9009 Additional BMP references: Luse, Marv. "The BMP File Format," Dr. Dobb's Journal, #219 September 1994 (Vol 9, Issue 10), pp. 18-22. ------------------------------ Subject: 1. CALS - Computer Aided Acquisition and Logistics Support Raster Format CALS files are used for document imaging and therefore only store black-and-white, 1-bit image data. CALS Type I files only store a single image per file and the data is always compressed using the CCITT Group 4 encoding algorithm. CALS Type II files may stored multiple images per file, the image data may be tiled, and tiles stored as raw data or as data compressed using CCITT Group 4 encoding. The CALS raster file format is defined primarily in the following military standards documents: MIL-STD-1840A, Automated Interchange of Technical Information MIL-R-28002A, Requirements for Raster Graphics Representation in Binary Format These documents may be obtained from the following sources: Standardization Documents Ordering Desk Building 4D 700 Robbins Avenue Philadelphia, PA 19111-5094 Global Engineering Documents 2805 McGaw Avenue Irvine, CA 92714 USA Voice: 800.854.7179 Voice: 714.261.1455 The CALS raster file format is supported through the CALS office of the United States Department of Defense: CALS Management Support Office (DCLSO) Office of the Assistant Director for Telecommunications and Information Systems Headquarters Defense Logistics Agency Cameron Station Alexandria, VA 22314 USA ------------------------------ Subject: 2. CDF - Cyberspace Description Format CDF is an ASCII-based format used for describing cyberspace decks and virtual worlds. This format provides a standard framework that is used to store, retrieve, modify, and exchange descriptions of cyberspace objects; including object initialization, state, and scheduling, and cyberspase simulation. CDF is based on the CDF format described in Autodesk's Cyberspace Development Kit. Autodesk's CDF is a closed format used to support a proprietary deveoper's tool, while the proposed CDF format is an open format intended to be accepted as an industry standard. The current CDF specification proposal may be obtained from: http://vrml.wired.com/proposals/cdf/cdf.html Questions about CDF should be directed to: Carl Tollander ------------------------------ Subject: 3. CGM - Computer Graphics Metafile The current version of the CGM ANSI/ISO standard (commonly called CGM:1992) is: Information Processing Systems--Computer Graphics Metafile for the Storage and Transfer of Picture Description Information, ANSI/ISO 8632-1992. This standard superseded the early CGM:1986 (ANSI X3.122-1986) ANSI standard. The CGM standard is contained in four ISO standards documents: ISO/IEC 8632-1:1992 Part 1: Functional Specification ISO/IEC 8632-3:1992 Part 2: Character Encoding ISO/IEC 8632-3:1992 Part 3: Binary Encoding ISO/IEC 8632-4:1992 Part 4: Clear Text Encoding These documents may be obtained from the following organizations: International Standards Organization (ISO) 1 rue de Varembe Case Postal 56 CH-1211 Geneva 20 Switzerland Voice: +41 22 749 01 11 Fax: +41 22 733 34 30 American National Standards Institute (ANSI) Sales Department 11 West 42nd Street New York, NY 10036 Voice: 212.642.4900 Canadian Standards Association (CSA) Sales Group 178 Rexdale Blvd. Rexdale, Ontario, M9W 1R3 Voice: 416.747.444 A WWW page devoted to CGM is: http://speckle.ncsl.nist.gov/~lsr/cgm_std.htm ------------------------------ Subject: 4. DEM - Digital Elevation Model The format of DEM map files is described in the publication: Data Users Guide 5 - Digital Elevation Models and is available for $1.00 US from: Earth Science Information Center (ESIC) U. S. Geological Survey 507 National Center Reston, VA 22092 USA Voice: 1.800.USA.MAPS Voice: 703.860.645 ------------------------------ Subject: 5. DLG - Digital Line Graph The format of DLG graph files is described in the publications: Data Users Guide 1 - Digital Line Graphs from 1:24,000-Scale Maps Data Users Guide 2 - Digital Line Graphs from 1:100,000-Scale Maps Data Users Guide 3 - Digital Line Graphs from 1:2,000,000-Scale Maps and each is available for $2.00 US from: Earth Science Information Center (ESIC) U. S. Geological Survey 507 National Center Reston, VA 22092 USA Voice: 1.800.USA.MAPS Voice: 703.860.645 ------------------------------ Subject: 6. DXF - Autodesk Drawing eXchange Format The AutoCAD DXF (Drawing eXchange Format) and AutoCAD DXB (Drawing eXhange Binary) formats are the native vector file formats of Autodesk's AutoCAD CAD application. DXF is probably one of the most widely supported vector formats in the world today. DXF is rich in features, including: support for 3D objects, curves, text, associative dimensioning, and is an easy format to parse. The DXB format is a binary representation of a DXF file and they are usually smaller and faster to load than the equivalent DXF file. The latest "official" DXF revision is Release 12. However, there is an even newer version of DXF containing several changes and additions to the format. Apparently the specification of the latest version of the DXF format is not yet (if it will ever be) freely available. Users are required to pay $4000US for a license to AutoCAD in to obtain the specs for this newest release of DXF file format. The official specification for DXF R12 may be found in the AutoCAD Manual Release 12: AutoCAD Customization Manual, Release 12, Autodesk Inc., 1992, pp. 241-81. The specification for DXF R12 has also been released in electonic form and is available in several of the Internet file format archives. You can also try poking around on Autodesk's FTP site, but not much is usually there: ftp://ftp.autodesk.com Many books detail the DXF format, including: The AutoCAD Database Book, F.H. Jones and L. Martin, Ventana Press, ISBN 0-940087-04-9. Order: 919.490.0062 voice. AutoCAD, The Complete Reference, 2nd Ed., Johnson, N., McGraw-Hill, New York, NY, 1991. Additonal information may be obtained directly from Autodesk: Autodesk Inc. Autodesk Developer Marketing 2320 Marinship Way Sausalito, CA 94965 Voice: 415.491.8719 ------------------------------ Subject: 7. EPS - Encapsulated PostScript The PostScript Language Software Development Kit is available from the creator of PostScript, Adobe Systems: Adobe Systems Inc. Attn: Adobe Systems Developer Support 1585 Charleston Road P.O. Box 7900 Mountain View, CA 94039-7900 Voice: 415.961.7900 Voice: 800.344.8335 Fax: 415.961.3769 ------------------------------ Subject: 8. FBM - Fuzzy Bitmap FBM is the native file format of the Fuzzy pixmap image manipulation and conversion toolkit written by Michael L. Mauldin at Carnegie Mellon University. Code to manipulate FBM (and many other) file formats is found in the FBM distrbution: ftp://nl.cs.cmu.edu/usr/mlm/ftp/fbm.tar.Z ------------------------------ Subject: 9. FFIVW - File Format for the Interchange of Virtual Worlds FFIVM is an ASCII-based, object-oriented format used to describe virtual objects and worlds. This format is not intended to be a native file format of any hardware or software platform, but instead to be used as an interchange medium used for converting one VRML format to another. The FFIVM specification proposal may be found at: http://vrml.wired.com/proposals/ffivw.html Questions about FFIVW should be directed to: Bernie Roehl Kerry Bonin <74367.1630@compuserve.com> ------------------------------ Subject: 10. GIF - Graphics Interchange Format GIF is a data stream-oriented file format used to define the transmission protocol of LZW-encoded bitmap data. GIF images may be up to eight bits (256 colors) in depth and are always compressed. Despite the fact that GIF supports only 8-bits worth of colors, and the multimedia extensions introduced in the 89a release have not been widely utilized, GIF still remains a popular choice for storing lower resolution image data. The GIF89a specification is available via many BBSs and on-line information services. You may also obtain the specification directly from CompuServe: CompuServe Incorporated Attn: Graphics Technology Department 5000 Arlington Center Boulevard Columbus, OH 43220 Voice: 614.457.8600, 800.848.8199 Note: Any software created or modified after 01 January 1995 that supports the capability of reading and/or writing GIF files must obtain a patent license agreement from Unisys Corporation. See Part I of the FAQ for more details on the Unisys GIF-LZW license agreements. ------------------------------ Subject: 11. GKS - Graphics Kernel System GKS is a standard specifying the input and output primitives for displaying 2D and 3D graphical data. Although GKS has no native file format, the CGM (Computer Graphics Metafile) format is often closely associated with its use. The following ISO documents describe the GKS standard: ISO 7942 Functional Specification ISO 8651-1 Fortran Binding ISO 8651-2 Pascal Binding ISO 8651-3 Ada Binding ISO 8651-4 ISO 8805 GKS-3D ISO 8806 GKS-3D Bindings These documents are available from ISO, ANSI, and CSA (see the CGM section for the addresses of these organizations). ------------------------------ Subject: 12. HPGL - Hewlett-Packard Graphics Language Hewlett-Packard Graphics Language (HP-GL/2) ------------------------------ Subject: 13. HPPCL - Hewlett-Packard Printer Control Language PCL is capable of rendering both raster and vector graphics. The official specification and toolkit for PCL is contained in the following Hewlett-Packard manuals: PCL 5 Printer Language Technical Reference Manual PCL 5 Developer's Guide, 3rd Edition, Part No. 5002-1847 The technical reference manual contains a complete description of PCL 5. The developer's guide contains many software examples illustracting how to design PCL-compatable software. These maunals may be obtained directly from Hewlett-Packard ------------------------------ Subject: 14. IGES - Initial Graphics Exchange Specification IGES is a set of protocols for the transfer and display of graphical information on remote devices via a telephone or computer communications network. IGES does not define any new graphical file formats, but instead uses existing formats (such as CGM) to encapsulate graphical data. IGES is associated with the NCGA (National Computer Graphics Association) and is part of the U.S. Product Data Association (USPRO) and the IGES/PDES Organization (IGO). The NCGA administers the National IGES User Group (NIUG), which provides access to information on IGES. To obtain the IGES specification, you must be a member of both NIUG and a Regional Interest Group (RIG). The IGES specification is available through the NCGA for $100US. For more information about the NIUG, RIGs, and IGES, contact: National Computer Graphics Association 2722 Merrilee Drive Suite 3200 Fairfax, VA 22031 USA Voice: 703.698.9600 ------------------------------ Subject: 15. IMJ - Image JPEG IMJ was created by Pegasus Image Corporation as a variation of the JFIF file format. IMJ is essentially a JFIF file with a Microsoft Windows BMP header and enhanced palette optimization. The IMJ format is used in several screensaver applications, and by orgainizations such as Delrina and the National Center for Missing Children. See the section describing the PIC - Pegasus Imaging Corporation Format for more information. ------------------------------ Subject: 16. JFIF - JPEG File Interchange Format JFIF is a data stream-oriented file format used to define the transmission of JPEG-encoded bitmap data. The specification for JFIF may be obtained directly from C-Cube Microsystems: C-Cube Microsystems Attn: Scott Sinclair Corporate Communications 1778 McCarthy Blvd. Milpitas, CA 95035 Voice: 408.944.6300 Fax: 408.944.6314 The Independent JPEG Group archive on ftp.uu.net also contains an on-line copy of the JFIF specification and additional JPEG information as: ftp://ftp.uu.net/graphics/jpeg/jfif.ps.gz ftp://ftp.uu.net/graphics/jpeg/jpeg.documents.gz ------------------------------ Subject: 17. MGF - Materials and Geometry Format MGF is an ASCII-based 3D rendering format designed to model surface geometry and materials for the purpose of visible-light simulation and rendering. The overall objective of this format is to provide a very simple yet fairly complete modeling language that does not place unreasonable demands on the applications programmer or the object library creator. The format specification is available bundled with an MGF file reader and is distributed in the file mgflib0.7.tar.Z on the following sites: http://radsite.lbl.gov/mgf/HOME.html ftp://hobbes.lbl.gov/www/mgf The MGF software is currently in an alpha release stage, which means the language may change in some incompatible ways between now and the first release. Use this software and data in this package at your own risk. Questions about MGF should be directed to: Greg Ward Voice: 510.486.4757 Fax: 510.486.4089 Email: GJWard@lbl.gov ------------------------------ Subject: 18. MIFF - Magick Image File Format MIFF is a bitmap format native to the ImageMagick toolkit which runs under the X Window System. ImageMagick is capable of displaying and converting a variety of still and animated graphics file formats. The specification for MIFF is available in the ImageMagick distribution available from: ftp://ftp.x.org/contrib/applications/ImageMagick/ImageMagick-3.6.1.tar.gz For more information about ImageMagick and MIFF, contact: duPont de Nemour & Company Attn: John Cristy Central Research and Development Experimental Station P.O. Box 80328 Room 162-A Wilmington, DE 19880-0328 Voice: 302.695.1159 Email: cristy@dupont.com ------------------------------ Subject: 19. NAPLPS - North American Presentation Layer Protocol Syntax NAPLPS is a protocol for transferring ASCII-based graphical information to remote terminals via a communications channel (telephone systems, computer networks, and so forth). NAPLPS is used by many Videotext services and Prodigy, the commercial on-line information service, and is specifically designed to provide usable information transfer rates, even at data rates as low as 2400bps. Although there is no NAPLPS file format, NAPLPS data streams are often saved as files, and the files are then referred to as using the "NAPLPS file format". The NAPLPS specification is a standards documents available through ANSI, ISO, or CSA. (See the CGM section for the addresses of these organizations). The CSA document (T500-1983) also contains a supplement (1-1991) which is not included in the ANSI version of this standard. Further information may be found in the February, March, April, and May 1983 issues of Byte Magazine. These articles explain much of the NAPLPS coding system and discuss the potential for NAPLPS. Michael Dillon has authored a paper on NAPLPS and started a NAPLPS section on SIMTEL20. Michael Dillon may be contacted at: CompuServe: 71532,137 Internet: mpdillon@halcyon.halcyon.com BBS: 604.546.2705 The BBS also contains NAPLPS Shareware and art. ------------------------------ Subject: 20. NFF - Neutral File Format NFF is a minimal scene description language used to test rendering algorithms and efficiency schemes. It supports basic geometry of objects, surface characteristics, placement of lights, color of objects, and the viewing angle of the human eye. NFF is ASCII-based and is used with the Standard Procedural Database (SPD) software package used for creating databases for testing rendering schemes. The specification for NFF is available on numerous FTP sites which archive file format documents, such as: ftp://zamenhof.cs.rice.edu/pub/graphics.formats and is available along with the SPD test programs, which produce NFF objects: ftp://ftp.princeton.edu/pub/Graphics/SPD You may also contact the author of NFF: Eric Haines 3D/Eye Inc. 1050 Craft Road Ithica, NY 14850 Email: erich@eye.com ------------------------------ Subject: 21. NFF - WorldToolKit Neutral File Format The WorldToolKit Neutral File Format is a creation of Sense8 for their WorldToolKit software product. WorldToolKit is a C language library providing the functionality needed to do virtual reality, including file parsing, sensor drivers, object management, behavior, and rendering. Sense8's NFF format was loosely adapted from the Videoscape (.geo) format, with the addition of 12-bit color, per-polygon texture application, and portals. It was later extended to support vertex normals, 24-bit color, and vertex uv coordinates. The current version of NFF is 2.1. Sense8 also supports a binary format of NFF called BFF (.bff file extension) The BFF format layout and order is identical to the ASCII version, with the exception that only 24-bit, and not 12-bit, colors are not supported. The WorldToolKit Neutral File Format was created and is maintained by: Sense8 100 Shoreline Hwy. Ste. 282 Mill Valley, CA 94941 Voice: 415.331.6318 Fax: 415.331.9148 Email: info@sense8.com Sense8's NFF specification is available via FTP at: ftp://avalon.vislab.navy.mil/pub/format_specs Questions about Sense8's NFF format should be directed to: Ben Discoe ------------------------------ Subject: 22. NITF - National Imagery Transmission Format The National Imagery Transmission Format Standard (Version 2.0) is documented as a collection of military standards documents. The actual file format is documented in the following standard: MIL-STD-2500, National Imagery Transmission Format (Version 2.0) for the National Imagery Transmission Format Standard, 18 June 1993 The remaining standards are as follows: MIL-HDBK-1300, National Imagery Transmission Format Standard (NITFS), 18 June 1993 MIL-STD-3201, Computer Graphics Metafile (CGM) Implementation Standard for the National Imagery Transmission Format Standard, 18 June 1993 MIL-STD-188-196, Bi-Level Image Compression for the National Imagery Transmission Format Standard, 18 June 1993 MIL-STD-188-197 Adaptive Recursive Interpolated Differential Pulse Code Modulation (ARIDPCM) Compression Algorithm for the National Imagery Transmission Format Standard, 18 June 1993 MIL-STD-188-198A, Joint Photographic Experts Group (JPEG) Image Compression for the National Imagery Transmission Format Standard, 15 December 1993 MIL-STD-188-199, Vector Quantization Decompression for the National Imagery Transmission Format Standard, 27 June 1994 MIL-STD-245-44500, Tactical Communications Protocol 2 (TACO2) for the National Imagery Transmission Format Standard, 18 June 1993 JIEO Circular 9008, National Imagery Transmission Format Standards (NITFS) Certification Test & Evaluation Program Plan, 30 June 1993 The NITFS standards may be obtained via FTP from the ITSI (Information Technology Standards Integrated) BBS at: ftp://jcdbs.2000.disa.mil/pub/library ITSI BSS may also be reached by modem at 703.834.6501 (14.4kbps, N-8-1). To receive hardcopies any or all of these documents, send a request via mail, fax, or email to: DISA/JIEO/CFS/TBCE c/o Logicaon Fay Mignone 1831 Wiehle Avenue Reston, VA 22090 USA Fax: 703.318.1098 Attn: Fay Mignone Email: mignone@cdbs.itsi.disa.mil or: Defense Information Systems Agency Center for Standards Carol Ciepiela Attn: TBCE, Rm 3304 10701 Parkridge Blvd Reston, VA 22091 USA Voice: 703.487.3536 Email: edi@itsi.disa.mil Questions may be directed to: NITFS Certification Test Facility Voice: 602.538.5458 x5494 ------------------------------ Subject: 23. OFF - Object File Format OFF was developed in 1986 at Digital Equipment Corporation's Workstation Systems Engineering for the interchange and archiving of 3D objects. OFF is an ASCII-based format and is independent of languages, devices, and operating systems. The specification for OFF is: Rost, Randi, OFF--A 3D Object File Format, November 6, 1986 (updated October 12, 1989). The OFF archive is available from: ftp://gatekeeper.dec.com/pub/DEC This archive contains the format specification, tools, and objects. It is not currently supported and is copyrighted. ------------------------------ Subject: 24. PBM - Portable Bitmap The Portable greymap file format is part of the Extended Portable Bitmap Utilities (PBMPLUS). PBM is used as an intermediate format for storing monochrome bitmap information generated by the PBMPLUS toolkit. PBM files may be either binary or ASCII and store data one-bit-per-pixel in size. Information and source code for PBM can be found in the distribution for PBMPLUS located at: ftp://ftp.wustl.edu/graphics/graphics/packages/pbmplus/pbmplus10dec91.tar.Z The specification for the PBM format can also be found in the manual page for pbm(5) on many Unix systems. ------------------------------ Subject: 25. PCX - ZSoft Paint PCX is one of the oldest bitmapped formats popularized by MS-DOS paint programs that first appeared in the early 1980's. PCX files may store mapped and unmapped image data from 1- to 24-bits in pixel depth, always contain RLE-compressed image data, and are recognized by almost all still-image graphics programs ever written. But because of the kludged evolution of the PCX format (caused partly by the efforts of Zsoft to continue to support the ever-changing world of graphics display adapters) it is generally advised that the MS Windows BMP format be used in place of PCX whenever possible. The PCX specification is available directly from ZSoft: ZSoft Corporation Attn: Shannon Donovan 450 Franklin Road, Suite 100 Marietta, GA 32067 Voice: 404.428.0008 Fax: 404.427.1150 BBS: 404.427.145 CompuServe: 76702,1207 ------------------------------ Subject: 26. PDS - Planetary Data Systems Format PDS was created by the Planetary Branch of the National Aeronautics and Space Administration (NASA) to store solar, lunar, and planetary data collected both on Earth and by spacecraft. And as with most U.S. Government documents, the specification is quite large and spread over several documents: Jet Propulsion Laboratory, Standard for the Preparation and Interchange of Data Sets, JPL Document D-4683, NASA, Pasadena, CA, 1988. Jet Propulsion Laboratory, Data Preparation Workbook, JPL Document D-7669, NASA, Pasadena, CA, 1990. Jet Propulsion Laboratory, Planetary Data System Standards Reference, JPL Document D-4683, NASA, Pasadena, CA, 1990. Jet Propulsion Laboratory, Specification for the Object Description Language, NASA, Pasadena, CA, 1990. These documents are available from: NASA Planetary Branch Jet Propulsion Laboratory Mail Stop 525-3610 4800 Oak Grove Drive Pasadena, CA 91109 Voice: 818.354.7587 Email: PDS_Operator@jplpds.jpl.nasa.gov ------------------------------ Subject: 27. PGM - Portable Greymap The Portable greymap file format is part of the Extended Portable Bitmap Utilities (PBMPLUS). PGM is used as an intermediate format for storing greyscale bitmap information generated by the PBMPLUS toolkit. PGM files may be either binary or ASCII and store pixel values up to 8 bits in size. Information and source code for PGM can be found in the distribution for PBMPLUS (see the section on the PBM format for information on PBMPLUS). The specification for the PGM format can also be found in the manual page for pgm(5) on many Unix systems. ------------------------------ Subject: 28. PIC - Pegasus Imaging Corporation Format Pegasus Image Corporation 4350 W. Cypress Street, Suite 908 Tampa, FL 33607 Voice: 813.875.7575 Fax: 813.875.7705 BBS: 813.874.5515 Name: guest guest, Password: demo CIS: GO PEGASUS ------------------------------ Subject: 29. PNG - Portable Network Graphics PNG (pronounced "ping") is a new bitmap format which is currently in development. Its creation is an attempt to give the graphics community an alternative to the shortcomings and misgivings found in most popular file formats. The current legal battle involving the GIF format may also have something to do with it too :-) The following paragraph, excerpted from the PNG (Portable Network Graphics) specification, eighth draft, explains the basic rationale behind the format: The PNG format is intended to provide a portable, legally unencumbered, simple, lossless, streaming-capable, well-compressed, well-specified standard for bitmapped image files which gives new features to the end user at minimal cost to the developer. The PNG specification is now in its tenth draft and is currently undergoing final editing in preparation for the 1.0 release. The PNG draft is considered finalized to the point that software may be safely written without the worry of the specification changing. A public draft of the current PNG specification may be found at: http://sunsite.unc.edu/boutell/png.html Questions about PNG may be asked on the comp.graphics newsgroup, via email at: png-info@uunet.uu.net or directed to the principle author of the PNG specification: Thomas Boutell PNG developers may join the PNG mailing list. Send email to png-info@uunet.uu.net and ask for more information. A human will be reading your request to join the list, so make it good. PNG materials can be had in great profusion by anonymous FTP from: ftp://godzilli.cs.sunysb.edu All programs on this site are in beta test and should be used carefully. In the case of questionable implementation, the specification is to be considered corrent and the code in error. Additonal PNG material may also be found at: ftp://ftp.uu.net/graphcs/png Group 42 is the author of the PNGLIB support library for developer's using the PNG file format. Their Web page contains a developer's section which includes the PNGLIB library, PNG format specification, Compression Library, and Image Test Suite. A Freeware version of theis library is currently available. Group 42 may be reached at: Group 42, Inc. Voice: 800.520.0042 Voice: 513.831.3400 Email: info@group42.com WWW: www.group42.com ------------------------------ Subject: 30. PPM - Portable Pixmap The Portable pixmap file format is part of the Extended Portable Bitmap Utilities (PBMPLUS). PPM is used as an intermediate format for storing color bitmap information generated by the PBMPLUS toolkit. PPM files may be either binary or ASCII and store pixel values up to 24 bits in size. Information and source code for PPM can be found in the distribution for PBMPLUS (see the section on the PBM format for information on PBMPLUS). The specification for the PPM format can also be found in the manual page for ppm(5) on many Unix systems. ------------------------------ Subject: 31. POL - InnovMetric Software Polygon Models Format POL is the native 3D file format for software products created by InnovMetric Software. The POL format was created to fill the need of storing data representing multi-contour, simple, planular, polygons using a binary file format. InnovMetric Software is developing a complete line of software products for building 3-D polygonal models using a 3-D imaging system. Two of these software tools are targeted at real-time 3-D graphics applications. IMCompress and IMFilter are two complementary tools for optimally reducing the number of polygons in a 3-D model. IMCompress uses a surface-based algorithm to downsize highly redundant models such as Digital Terrain Models and polygonal models generated by a CAD or a 3-D imaging system. IMFilter uses a volume-based algorithm to create ultra-compact models (20 to 500 triangles) for level of details management in applications requiring real-time 3-D graphics. The POL file format specification is primarily distributed as Appendix B of the IMCompress User's Guide published by InnovMetric Software. The specification is also available in PostScript format as the file pol.ps in a few of the graphics file format specification archived listed in part 1 of this FAQ. POL was created and is maintained by: InnovMetric Software Inc. 2065 Charest ouest, Suite 218 Sainte-Foy, Quebec Canada, G1N 2G1 Questions about POL may be directed to: Marc Soucy ------------------------------ Subject: 32. POV - Persistence of Vision Raytracing The POV-Ray format is used to store a scene description language used by the POV-Ray ray tracing software package. POV-Ray files are always ASCII to allow easy transportation between different file systems. The specification for the POV file format and scene description language is found in the file povray.doc in the POV-Ray distribution. You may obtain this file (and the entire POV-Ray package) from the official POV-Ray FTP archive site: ftp://alfred.ccs.carleton.ca/pub/pov-ray/POV-Ray2.2/ Questions about POV-Ray may also be direct to: Drew Wells POV-Team Leader 73767.1244@compuserve.com The following is an excellent book on ray tracing using the POV-Ray tracing software package for the PC: Ray Tracing Creations: Generate 3D Photo-Realistic Images on the PC, Drew Wells and Chris Young, Waite Group Press 1993. ------------------------------ Subject: 33. RAD - Radience RAD is the native file format for the public domain Unix Radience radiosity renderer. The RAD specification and Radience package are available at: http://radsite.lbl.gov/radience/HOME.html ------------------------------ Subject: 34. RAS - Sun Rasterfile Sun rasterfile is the native bitmap format of Sun Microsystem Unix systems. The rasterfile format has become more wide-spread with the growing popularity of the SunOS operating system and Sun SPARCStation family of Unix workststaions. Sun rasterfiles store images up to 32 bits in pixel depth and support a basic for of run-length data compression. The primary source of information for Sun Rasterfiles is the SunOS include file /usr/include/rasterfile.h and the rasterfile online manual page: Sun Microsystems, rasterfile (5), Sun OS 4.0 Programmer's Manual, 1990. The following jounal article is devoted to the Sun rasterfile: McGee, Format for Byte-Encoded Rasterfiles, Sun-Spots Digest, Volume 6, Issue 84. And several books on graphics file formats also feature the rasterfile format. ------------------------------ Subject: 35. RAY - Rayshade Rayshade is a ray-tracing application for the MS-DOS environment. The Rayshade format is the native scene description language used by Rayshade. And like most 3D scene-rendering formats it is ASCII-based and supports most features commonly found in these formats. The specification is available in the Rayshade distribution on many BBSs and FTP archive sites. The format is detailed in the document: Rayshade 4.0 Quick Reference The author may be contacted at: Princeton University Attn: Craig Kolb Department of Computer Science 35 Olden Street Princeton, NJ 08544 Email: cek@princeton.edu ------------------------------ Subject: 36. RIB - Renderman Interface Bytestream The RenderMAN file format specification may be found in the following document available from Pixar: The RenderMAN Interface, Version 3.1, September 1989. San Rafael, CA. Pixar 1001 West Cutting Blvd. Richmond, California 9484 USA Voice: 415.236.4000 Also of interest is the following publication: The RenderMan Companion: A Programmer's Guide to Realistic Computer Graphics, Steve Upstill, Addison-Wesley Publishing Company, ISBN 0-201-50868-0, $26.95 ------------------------------ Subject: 37. RIFF - Microsoft Resource Interchange File Format Microsoft Corporation Attn: Multimedia System Group Product Marketing One Microsoft Way Redmond, WA 98052-6399 Voice: 206.882.8080 BBS: 206.637.9009 Information on RIFF may be found in the following documents: Microsoft Windows Multimedia Programmer's Guide, Microsoft Corporation, Microsoft Press, Redmond, WA. Microsoft Windows Multimedia Programmer's Reference, Microsoft Corporation, Microsoft Press, Redmond, WA. The specification is also available in the Microsoft Multimedia Development Kit (MDK), on Disk 8 of the Microsoft Developer's Network CD distribution, and as a MS Windows help file on the FTP archive site: ftp://ftp.microsoft.com/developer/MSDN/CD8/RIFFNE.ZIP ------------------------------ Subject: 38. RIX - ColoRIX Image File ColorRIX is the native bitmap format of the ColorRIX VGA Paint application for MS-DOS. The ColorRIX format is documented in the ColorRIX VGA Paint manual distributed with the ColorRIX program available from: RIX SoftWorks Inc. Attn: Richard Brownback or Paul Harker 18023 Sky Park Circle, Suite J Irvine, CA 92714 Voice: 714.476.8266 Voice: 714.476.8486 ColorRIX is also bundled with several different VGA cards and the specification may also be found on numerous FTP archive sites. ------------------------------ Subject: 39. SDML - Spacial Data Modeling Language SDML is a spatial description language used for storing CAD and GIS data, such as found in Landscape Planning, Design, and Architectural databases. SDML currently exists in two versions: the old SDML format and the new (Version 1.0) format. The old format is derived from the ASCII-based format used in the Silicon Graphics CLRview and PolyTRIM software environments. The new format, released in 05Feb95, is a more detailed, capable, and size-optimized revision of the old SDML and supports all the features of the Silicon Graphics CLRMosaic software. The New SDML specification is available from: http://www.clr.toronto.edu:1080/CLRMOSAIC/SDML.html Questions about SDML should be directed to: Rodney Hoinkes, Head of Design Applications Centre for Landscape Research University of Toronto 230 College St. Toronto, ON, M5S 1A1 Voice: 416.978.3551 Fax: 416.971.2094 Email: rodney@clr.toronto.edu WWW: http://www.clr.toronto.edu/PEOPLE/RODNEY/rodney.html ------------------------------ Subject: 40. SHG - Segmented Hyper-Graphic SHG is a file format used by Microsoft in the WinHelp on-line help facility found in Windows 3.1. This format is used to save a Microsoft Bitmap (BMP) or Windows Metafile (WMF) graphic and store the coordinates of specific areas of the bitmap known as "hotspots". When the bitmap is displayed and the user selects a hotspot, WinHelp jumps to another part of the help documentation via a hyper-text link macro stored in the SHG file. Another file format used with SHG files is the Multiple-Resolution Bitmap (MRB) format. MRB files contain one or more SHG images, each rendered at a different resolution. Several SHG files are typically created using the SHED.EXE utility and then fed into the MRB compiler to create a single MRB file. When WinHelp reads the MRB file it chooses which bitmap most closely matches the resolution of the display. SHG is currently officially undocumented by Microsoft, but the specification may be found at: ftp://ftp.microsoft.com/developr/drg/Multimedia/SHED.ZIP Information on SHG and MRB may be found in the following journal article: .mrb and .shg File Formats, Windows/DOS Developer's Journal, Pete Davis, February 1994 (Vol 5, No 4), pp. 37-46. Questions about these formats may also be directed to Section 16 (WinHelp/Tools) of forum WINSDK on CompuServe. ------------------------------ Subject: 41. STL - Stereolithography Interface Format STL files are the native file format of the SLA CAD software created by 3D Systems of Valencia, CA, USA. STL files may be ASCII or binary in form, although binary is far more common due to the very large resulting size of the CAD data when saved to the ASCII format. [ More on this format next month ] ------------------------------ Subject: 42. TGA - Truevision (Targa) File Format Copies of the TGA specification, including a sample code disk, may be obtained from Truevision: Truevision Incorporated 7340 Shadeland Station Indianapolis, IN 46256-39925 Voice: 317.841.0332 Fax: 317.576.7700 BBS: 317.577.8783 FTP: ftp.truevision.com ------------------------------ Subject: 43. TIFF - Tag Image File Format The TIFF 6.0 specification is available in the TIFF Developer's Kit. Information on obtaining this kit and joining the Aldus Developer's Association (ADA) may be obtained from the Developer's Desk at Aldus Corporation: Aldus Corporation Attn:: Aldus Developer's Desk 4411 First Avenue South Seattle, WA 98144-2871 Voice: 206.628.6593, 800.331.2538 Fax: 206.343.4240 Email: tiff-input@aldus.com Or from the following FTP site: ftp://sgi.com/graphics/tiff/TIFF6.ps.Z The TIFF Class F specification may be obtained from ADA's FAXback service at 206.628.5753. Order document #9001 for an index of all documents available from this service. Note: Any software created or modified after 01 January 1995 that supports the capability of reading and/or writing bitmapped data stored in a TIFF file and compressed using the LZW algorithm must obtain a patent license agreement from Unisys Corporation. See Part I of the FAQ for more details on the Unisys GIF-LZW and TIFF-LZW license agreements. ------------------------------ Subject: 44. URT - Utah Raster Toolkit URT is the native raster file format of the Utah Raster Toolkit. This toolkit, which first appeared in 1983, is a rich source of bitmap manipulation tools and source code. The toolkit is copyrighted, but distributable on a GNU-like license. The specification for the URT file format is found in the following document of the Utah Raster Toolkit: Design of the Utah RLE Format, Thomas, Spencer W., University of Utah, Department of Computer Science. The Utah Raster Toolkit distribution (urt-3.0.tar.Z) may be obtained via FTP from the following sites: ftp://cs.uath.edu ftp://weedeater.math.yale.edu ftp://freebie.engin.umich.edu Questions about URT may be directed to: toolkit-request@cs.utah.edu urt-request@caen.engin.umich.edu ------------------------------ Subject: 45. VICAR2 - Planetary File Format VICAR2 is used to store planetary image data gathered from Earth and by spacecraft. VICAR2 is similar in design and use to the FITS and PDS formats. Information on VICAR2 may be obtained directly from JPL: NASA Attn: Bob Deen Image Processing Laboratory Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 Email: rgd059@mipl3.jpl.nasa.gov ------------------------------ Subject: 46. VIFF - Visualization Image File Format VIFF is the native bitmap graphics file format of the Khoros System environment implemented using the X Window System. The VIFF format specification, including other documents related to the VIFF format, may be found in the Khoros distribution. Chapter 1 of Volume II, Programmer's Manual, the files in the directory src/file_formats, and the viff.h file are the most helpful. The following FTP sites archive the Khoros distribution: ftp://ftp.eece.unm.edu/pub/khoros ftp://ftp.uu.net/pub/window-sys/khoros The Khoros Consortium may be contacted at: Khoral Research Inc. 6001 Indian School Road NE Suite 200 Albuquerque, NM 87110 Voice: 505.837.6500 Fax: 505.881.3842 Email: khoros-request@chama.eece.unm.edu Email: khorus@chama.eece.unm.edu (User's Group) Newsgroup: comp.soft-sys.khoros ------------------------------ Subject: 47. VRML - Virtual Reality Modeling Language VRML is a proposed design based on the Silicon Graphics Open Inventor ASCII file format. Originally called the Inventor VRML, this format has evolved into what is now the VRML format. VRML is also called a "Markup Language" for reasons that it is used in a fashion similar to HTML (HyperText Markup Language), but for rendering 3D graphics rather than text. VRML, however, is in no way derived from HTML. The current VRML specification may be obtained from: http://www.eit.com/vrml/vrmlspec.html Questions about VRML may be directed to: Mark Pesce, Enterprise Integration Technology, Inc. Anthony Parsi, Labyrinth Group Gavin Bell, Silicon Graphics, Inc. The original Inventor-VRML specification may be obtained from: http://www.sgi.com/Technology/Inventor/VRML/VRMLDesign.html The Labyrinth VRML specification may be obtained from: http://vrml.wired.com/proposals.labspec.html VRML Research and Sample images: http://www.sdsc.edu/vrml http://www.sgi.com/FreeStuff/Cool-Scene.vrml ------------------------------ Subject: 48. VPF - Vector Product Format VPF is a standard format, structure, and organization for large geographic databases that are based on a georelational data model. VPF is primarily used for organizing and encapsulating such digital geographic databases for transmission. More information on VPF may be found in the newsgroup and FAQ of comp.infosystems.gis. The specification for VPF may be found in the following military standard document: MIL-STD-600006, Vector Product Format, 13 April 1992 This MIL-STD may be obtained from: Naval Publications & Forms Center Code 3051 5801 Tabot Ave. Philadelphia, PA 19120 USA ------------------------------ Subject: 49. WebOOGL - Web Object Oriented Graphics Library WebOOGL is a OOGL-based format used for describing 3D graphics on the World Wide Web. This format supports the embedding of URL links within 3D objects and allows multiple WebOOGL objects found at different locations on the Web to be combined into a single scene. The WebOOGL specification may be found at: http://www.geom.umn.edu/docs/weboogl/weboogl.html Additional information om the use of OOGL as a VRML may be obtained from: http://vrml.wired.com/proposals/oogl.html ------------------------------ Subject: 50. XBM - X BitMap XBM is a native file format of The X Window System and is used for storing cursor and icon bitmaps that are used in the X GUI. XBM files are quite different in that they are actually C language source files that are created to be read by a C compiler rather than a graphical display program. XBM data is typically found in headers (.h files) and are a series of static unsigned char arrays containing the monochrome pixel data. There is one array per image stored in the header. XBM was created by the X Consortium as part of the X Window System. Refer to the /bitmaps directory of the X Window distribution for examples of XBM files. The central FTP distribution site for X version 11 is: ftp://ftp.x.org Reference works describing XBM include: Xlib-C language X Interface, Gettys, James, and Robert W. Scheiffler, Consortium Standard, X Version 11, Release 5, First Revision, August 1991. Xlib Programming Manual, Nye, Adrian, third edition, O'Reilly & Associates, Inc. Sebastopol, CA, 1992. ------------------------------ Subject: 51. WMF - Windows Meta File WMF is the native vector file format for the Microsoft Windows operating environment. WMF files are actually a collection of GDI (Graphics Device Interface) function calls also native to the Windows environment. When a WMF file is "played back" (typically using the Windows PlayMetaFile() function) the graphics is rendered. WMF files are device-independant and have no limit to their size. Most books on Microsoft Windows programming contain sections on the internals of WMF files. The Microsoft Knowledge Base (available at ftp://microsoft.com and on the Microsoft Developer Network CD) also contains the complete specification of WMF. I also highly recommend the book: Inside Windows File Formats, Tom Swan, Sams Publishing 1993. ISBN 0-672-30338-8 $24.95 softcover, 337 pages. ------------------------------ Subject: 52. WPG - WordPerfect Graphics Metafile WPG is the native graphics file format of the WordPerfect Corporation line of software products. For this reason it is common to find WPG files in MS-DOS, Microsoft Windows, Apple Macintosh, and Unix environments. WPG files may store bitmapped or vector graphics data, or Encapsulated PostScript data as well. Bitmapped data may be up to 24-bits deep and selectable from a palette of 256 colors. The WPG specification is published in the WordPerfect Corporation Developer's Toolkit for PC Products. This toolkit is available directly from WordPerfect Information Services: WordPerfect Information Services Voice: 801.225.5000 Technical questions regarding WPG may be directed to: WordPerfect Manufacturer/Developer Relations Department Voice: 801.228.7700 Fax: 801.228.7777 CompuServe: 72567,3612 And if all else fails: WordPerfect Corporation 1555 North Technology Way Orem, UT 84057 Voice: 800.526.4477 Fax: 801.222.5077 BBS: 801.225.4414 ------------------------------ Subject: 53. XPM - X PixMap XPM is a defacto standard for storing monochome, gray-scale, and color pixmap data to disk under the X Window system. XPM files, like XBM files, are C source code files, with each pixmap being defined as a static char array. The XPM format was created through the work of the KOALA Project at Groupe Bull Research. Questions about XPM may be directed to: BULL Research c/o INRIA 2004 route des Lucoiles 06565 Valbonne Cedex France Email: lehors@sophia.inria.fr You may subscribe to the XPM mailing list by sending a subscription request to: xpm-talk-request@sophia.inria.fr The XPM library (a collection of utilities that read and write XPM files) version 3.2g (April 1993) may be obtained via FTP from: ftp://avahi.inria.fr/contrib/xpm.tar.Z ftp://export.lcs.mit.edu And a collection of XPM files (mostly icons) resides at: ftp://ftp.x.org/contrib/AIcons ------------------------------ Subject: 54. XWD - X Window Dump XWD is used to store screen dumps created by the xwd client process in the X Window System. The image of any window or the background may be saved (dumped) to an XWD file. Using the following command: xwd -root > bg.xwd The background is saved to the file bg.xwd. By replacing the "root" flag with the ID of a window, only that window will be saved to the XWD file. XWD was created by the X Consortium as part of the X Window System. Refer to the /usr/include/X11 directory for header files (XWDFile.h) that define the X10 and X11 versions of the XWD format. The central FTP distribution site for X version 11 is: ftp://ftp.x.org ------------------------------ Subject: III. Kudos and Assertions ------------------------------ Subject: 0. Acknowledgments The following people have made this FAQ take just a little bit longer to read since the last time you looked at it (blame them and not me): Bjorn P. Brox John Cristy Ben Discoe James Durham Bruce Garner Eric Haines Chris Komnick Tom Lane Stanley F. Quayle Marc Soucy ------------------------------ Subject: 1. About The Author The author of this FAQ, James D. Murray, lives in the City of Orange, Orange County, California, USA. He is the co-author of the book Encyclopedia of Graphics File Formats published by O'Reilly and Associates, makes a passable living writing Microsoft Windows applications in C++, and may be reached as jdm@netcom.com, or via U.S. Snail at: P.O. Box 70, Orange, CA 92666-0070 USA. GCS d-- H++ s g- p? au+ a w+ v++ C+++(++++) US+++ p++>++++ L>++ 3 E--- N++ K- W---$ M-@ V-- po Y+ t++ 5-- j>x R+>-- G' tv-->! b+++ D++ B e- u* h- f r-->+++ n++ y*(**) ------------------------------ Subject: 2. Disclaimer While every effort has been taken to insure the accuracy of the information contained in this FAQ list compilation, the author and contributors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ------------------------------ Subject: 3. Copyright Notice This FAQ is Copyright (C) 1994-95 by James D. Murray. All Rights Reserved. This work may be reproduced, in whole or in part, using any medium, including, but not limited to, electronic transmission, CD-ROM, or published in print, under the condition that this copyright notice remains intact.