On Tue, 18 Jan 2011 09:00:28 +0200, clipka <ano### [at] anonymousorg> wrote:

> Am 17.01.2011 20:45, schrieb Carlo C.:
>> clipka<ano### [at] anonymousorg>  wrote:
>>> Am 17.01.2011 15:59, schrieb Nekar Xenos:
>>>> It would be wonderful if we could use .dem and .hgt formats for
>>>> heightfields as these are the native file formats for terrain data.
>>>
>>> Do you have a source for file format documentation? A (not necessarily
>>> complete) list of software that generates files in this format might be
>>> interesting, too.
>>
>> This, about USGS DEM:
>>
>> http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/dem/
>
> As far as I understand, the format stores data in a non-rectangular  
> format, which will make it pretty difficult for use in height fields.

So I guess we need to ad a request for spherical heightfields as well :)

-- 
-Nekar Xenos-

Post a reply to this message

Am 18.01.2011 14:52, schrieb Nekar Xenos:

>>> This, about USGS DEM:
>>>
>>> http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/dem/
>>
>> As far as I understand, the format stores data in a non-rectangular
>> format, which will make it pretty difficult for use in height fields.
>
> So I guess we need to ad a request for spherical heightfields as well :)

Given the various possible ways of mapping sample points to lat/long 
coordinates, the least common denominator would probably be a triangle 
mesh, so what you'd actually ask for seems to boil down to another 
syntax for describing mesh/mesh2 objects. Somethng like

mesh_file {
   FILE_TYPE FILE_NAME
   [...]
}

(The same syntax could also be used for .obj files.)

Post a reply to this message

On Tue, 18 Jan 2011 20:57:21 +0200, clipka <ano### [at] anonymousorg> wrote:

> Am 18.01.2011 14:52, schrieb Nekar Xenos:
>
>>>> This, about USGS DEM:
>>>>
>>>> http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/dem/
>>>
>>> As far as I understand, the format stores data in a non-rectangular
>>> format, which will make it pretty difficult for use in height fields.
>>
>> So I guess we need to ad a request for spherical heightfields as well :)
>
> Given the various possible ways of mapping sample points to lat/long  
> coordinates, the least common denominator would probably be a triangle  
> mesh, so what you'd actually ask for seems to boil down to another  
> syntax for describing mesh/mesh2 objects. Somethng like
>
> mesh_file {
>    FILE_TYPE FILE_NAME
>    [...]
> }
>
> (The same syntax could also be used for .obj files.)

Sounds good to me :)

-- 
-Nekar Xenos-

Post a reply to this message

Nekar Xenos <nek### [at] gmailcom> wrote:
> > mesh_file {
> >    FILE_TYPE FILE_NAME
> >    [...]
> > }
> >
> > (The same syntax could also be used for .obj files.)

> Sounds good to me :)

  Sounds, once again, something which should be implemented via scripting
(in the hypothetical new scripting language of POV-Ray 4.0) rather than as
a core feature.

  Adding more and more new core features is *not* going to help with the
transition to POV-Ray 4.0 (if that ever comes into fruition).

-- 
                                                          - Warp

Post a reply to this message