|
|
Hi(gh)!
On 14.04.20 11:57, jr wrote:
> o you could "mix" tiles. using the 30m where detail matters, using 90m for
> other areas.
>
> o you could pre-process each ocean etc tile, averaging out N neighbouring
> pixels.
>
> o you could reduce the #vertices per mesh. for instance, if the mesh data is
> stored in GTS format, there's a tool ('gtstricutter' (have not used it (yet)))
> which can remove triangles according to some constraints you supply on the
> command-line.
>
> there will any number of other ways too, I guess.
Most likely, I will provide the data as heightfields rather than mesh2
objects...
See you in Khyberspace!
Yadgar
Post a reply to this message
|
|