Hi Scott, that's right, the tutorial is part of the AutoAsm documentation. These are the links:http://www.kline.demon.co.uk/AutoAsmV05.zip (the original release last December)http://www.kline.demon.co.uk/AutoAsm_Update_2.zip(update from the end of January)http://www.kline.demon.co.uk/autoasm_temp_update.zip (the latest temporary update) AutoAsm always reads in data from a bitmap. TerraScene can generate bitmaps in the right format, so the two programs work together very well. Best regards, Chris

Hello Luis,Did not see your post!I hope you had a nice vacation and a recreative time!An interestingly approach.What I thought some weeks ago is for imported polygons:I hope the attachment works (very small size and kb, (last time I had no luck with this) and has this address:http://forums.avsim.net/user_files/89274.jpgAs you can see on my screenshot the lakes fit nice to the mesh (or vice versa).The mesh do not have big steps there, because there is a lake.The variation of the elevation around the lake is always around +/- 0-20m (requirement: a good mesh)What I am doing currently for my imported lake polygons (hundreds in one step):I am going around the polygon with the mouse, and the status bar tells me the altitude.(here -1, because I am on the polygon point).With this lake between 605-617 m.So I assign manual the high for the polygon to 610m.Very rare there are big, unwanted cliffs.I thought, there is maybe a possibility to save the time and have an automatic feature:a)to look for the elevation of every single point of these 226 points of the polygonb)take the average from the point elevations as the polygon high?The same I do manually.I took this lake, because it is done with 2 polygons (but they are rare!). The end points of the black line in the lake are identical and used from both polygons.This situation is probably a problem (maybe a nice waterfall, along the black line). But maybe a possibility to use identical points to assign the same high to both polygons.I do not know, if this can be done, and how much time it takes, but I always forget some lakes.Doing 500

Hi Horst,I've been using this "painful" manual approach for quite awhile editing the default or new (created with Slartibartfast) LWM elevations directly in the LWM code, based on a shoreline overlay of the base mesh. The released version of Slarti actually does what you propose: it reads the mesh points beneath the poly boundary and assigns the median as the lake's elevation. Works like a charm except that Slarti's procedure works at the LWM level. That is, the poly is already broken into its LOD13 subpolys (if it crosses LOD boundaries) and thus larger lakes sometimes have small elevation steps, depending on the "cleanness" of the mesh. Usually, those steps can't be seen from the air but they can be a nasty surprise when touching down with a floatplane ;-) For now I compile larger lakes in a separate file and do the hand-editing, where necessary. Hopefully, future versions of AutoAsm or Slarti will find a "perfect" solution (though I have my doubts, given the issues with mesh detail, particularly of SRTM data).Cheers, HolgerP.S.: I'm really curious what you're working on there - European lakes???