Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site turtlevax.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!think!mit-eddie!genrad!decvax!decwrl!turtlevax!ken
From: ken@turtlevax.UUCP (Ken Turkowski)
Newsgroups: net.graphics,net.ai
Subject: Re: Re: Computer Vision, Pattern Recognition --> Generalized Image Files
Message-ID: <839@turtlevax.UUCP>
Date: Mon, 29-Jul-85 13:44:49 EDT
Article-I.D.: turtleva.839
Posted: Mon Jul 29 13:44:49 1985
Date-Received: Wed, 31-Jul-85 23:57:50 EDT
References: <10571@rochester.UUCP> <833@turtlevax.UUCP> <374@utastro.UUCP> <89@rochester.UUCP> <195@steinmetz.UUCP>
Reply-To: ken@turtlevax.UUCP (Ken Turkowski)
Organization: CADLINC, Inc. @ Menlo Park, CA
Lines: 18
Xref: linus net.graphics:932 net.ai:2688

In article <195@steinmetz.UUCP> connolly@steinmetz.UUCP writes:
>We've been switching over from an internal format to SRI's (?) IU-workbench
>format.  This is the default format for Image-Calc and seems to be adequate
>for the time being.  When we store scene structures with line segments
>thrown in, we use an adaptation of the format used by Image-Calc for color
>images (i.e., a master file which contains paths for each component image,
>and then all the definitions for the lines & their properties).

Could you post the formal description of these image formats?  I'd like
to see what the advantages and disadvantages are, and whether they are
machine independent and are flexible enough to be used for my
application.

-- 

Ken Turkowski @ CADLINC, Menlo Park, CA
UUCP: {amd,decwrl,hplabs,nsc,seismo,spar}!turtlevax!ken
ARPA: turtlevax!ken@DECWRL.ARPA