Slime wrote:
> Cool, this seems like the sort of thing you'd see forwarded around and
> linked to a lot.
> 
> You're missing a period at the end of the second paragraph on the Technical
> Information page. I would make the "About" link more prominent because I
> found that information interesting. 

Yes, i first didn't find a name short enough to put into the main menu 
but it is there now.

> I was also left with a few questions
> after reading it:
> 
>  - You claim that isosurfaces "only need the plain height data and not
> require large mesh structures to be generated." Of course, you must keep the
> elevation data in memory *somehow* to be able to render the images. How do
> you store it more efficiently than, say, a height field does?

A smooth heightfield needs additional 3x16bit per vertex for storing the 
normal vectors.  And you are bound to using a plain rectangular grid or 
fiddle with multiple heightfields.

>  - How are you feeding your data into the isosurfaces? I know POV-Ray can't
> read efficiently from arrays from within function{}s. Are they greyscale
> images?

Yes, of course.

>  - Where do you get your data from (maybe I missed this)?

http://earth.imagico.de/credits.html

> Nice job.

Thanks.

Christoph

-- 
POV-Ray tutorials, include files, Landscape of the week:
http://www.imagico.de/ (Last updated 14 Mar. 2006)
MegaPOV with mechanics simulation: http://megapov.inetart.net/

Post a reply to this message