Arnt Karlsen writes: > Curtis L. Olson writes: > > Alex Romosan writes: > > > "Frederic Bouvier" <[EMAIL PROTECTED]> writes: > > > > > > > I am playing with SRTM-1 too. I started terrafit with --error=2 > > > > and --maxnodes=2000 ( after the patch to terrafit.py ) and I must > > > > say it is very impressive to see in action. > > > > > > > > But I found glitches that are quite obvious, and that do not > > > > appear in the scenery made by Alex Romosan ( certainly with > > > > default options, before the patch ) : it seems that the buildings > > > > are buried in the terrain, with small pikes. > > > > > > i never ran terrafit. i just followed the instructions at > > > http://www.terragear.org/docs/scenery-tutorial/fg-scenery-tutorial.html > > > what does terrafit do? do i need to run it before generating the > > > scenery? > > > > Look at Prep/TerraFit/terrafit.py > > > > It will take the specified tree of .arr files and generate a .fit file > > for each of them. > > > > It uses an algorithm that is at least a couple orders of magnitude > > more intelligent than what I came up with years ago when I first > > started the terragear tools. Essentially this means significantly > > better terrain approximations, with significantly fewer points which > > is a win-win-win-uhhh-win. > > ..this means the resulting terrain points are _calculated_ and not > the original _observations_ collected by instruments, fotos etc? > (I ask to try help document future scenery generation decisions, > calculated scenery details mistaken for observed terrain features, > or vice versa, will introduce errors in future sceneries.)
No it means that It 'selectively' uses some of the original points See "Fast Polygonal Approximation of Terrains and Height Fields" linked from http://graphics.cs.uiuc.edu/~garland/CMU/scape/ HTH Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
