SBuilder BLN import question

[Holger 0]

Howdy,I'm trying to import a Surfer BLN file into SBuilder (2.01) but keep getting "Run Time Error '5' - Invalid procedure call or argument" and SBuilder shuts down.The ASCII data are in lat/long, WGS84 and look like this:8-151.55179995 59.64184423 15-151.55167444 59.64182533 15-151.55148025 59.64179567 15-151.55127618 59.64176397 15-151.55106171 59.64173192 15-151.55083815 59.64169958 15-151.55061144 59.64166663 15-151.55044406 59.64164326 153-151.54462313 59.64546563 16-151.54662145 59.64483623 16-151.54903627 59.64407370 1629-151.70190746 59.71022267 17-151.70182361 59.70997531 17-151.70174502 59.70974423 17Any ideas? Perhaps a different separator?Cheers, Holger

[Guest Horst]

Hello Holger,Look to the ini file of SBuilder.When the separator is tabulator of your file, use

[Holger 0]

Hi Horst,Besten Dank - thank you very much! The change to 'tab' did the trick.Cheers, Holger

[Holger 0]

Howdy,um... well, not so successful after all. Every time I try to zoom in on the data or pan around I get an "Run time error 480 - Can't create AutoRedraw image" crash. Seems like the same error that G2K4 gives when it runs out of memory. So I subset my road data to a mere 650kb section and still get the error. In contrast, I can load a 60MB background image into SBuilder without a problem. Is the memory use determined by the size of the project area or the size of the BLN data? If the former, how would I deal with sparse data (i.e., a few roads) that occupy a large area (the subset is 2 x 5 degrees)?Cheers, Holger

[Guest luissa]

Hello Holger,I have no clue as to what causes that crash. If you want to send me the file I will possibly discover the reason.On my tests I use a map which spans 5 x 3 degree. I divided it, manually, in 15 maps of 1 x 1 degree. Each 1 x 1 degree is composed of:one 2000 x 2000 pixels for summerone 32 x 32 pixels dummy map (not) used for fall, winter, hard winter, spring, night, alpha and landone 3601 x 3601 pixels for meshAll maps have degree borders so the calibration is just to enter the lat/lon for the borders. The 3601 x 3601 is a bitmap related to a "1 arc second mesh" of 1 degree span. I create the bitmap by using the DEM tool "BSQ > BMP". If you have a decompiler for a mesh that creates BSQ (DEM) files it could be the case that you need to add 8 extra bytes at the end of the DEM file for SBuilder to recognize it as a BSQ file and produce the Bitmap. For example a BSQ file of 3601 x 3601 data points should have:3601 x 3601 x 2 + 8 bytes for SB to accept itThis mesh map is useful because when I switch the View to mesh I can check how good are LWM lakes adjusted to the mesh. I am finishing an addition to SB wich allows me to change the color for a given altitude. I could change the color for altitudes "less than a value" but that forces me to read the original bitmap pixel by pixel which is very slow. The partition of the maps is useful because the display becomes faster when a map is not visible. The 15 referred to maps could be in any place. There should be no reason for scattered maps to cause problems. Also note that in the described example only 15 bitmaps are loaded at a given time (each map is composed of 8 "seasonal" bitmaps but only one season is active). Therefore the idea of creating a dummy small map for non used seasons is not really a good idea with respect to memory saving.Finally the maximum number of polygons or lines is 32767. Also the maximum number of points in each polygon or line is 32767. But SB will freeze if your system memory is low. I loaded with success a project with 32XXX lines, but I work on smaller ones. I do not know if version 2.01 already has the tool "Invert Selection". I have this on the present version. So when I import a so big project, I select a box, followed by "Invert Selection" followed by "Delete Everything Selected" and Save As a smaller project.Please excuse me for this long email as I am taking the opportunity to refer to some things that could be useful to other users. One more thing related to the Mesh Map is the fact that I can read the altitudes of the mesh. I could combine this with the Photo Tool. You can have, say, a 1 pixel per meter bitmap placed as the Summer bitmap. Every LOD13 square with an underlying summer bitmap can be declared as a photo tile with the Photo Tool. Then SB can generate a photo BGL and produce the bitmap phototile (256 x 256 pixels with a resolution of about 4,8 meter per pixel). But I could also generate textured triangles in SCASM format. The resolution of the textured triangles would be the resolution of the bitmap. I could place in the begining of the BGL a "distance test". If the viewer is far no display (better saying : the normal photo tile display). If the viewer is close display the triangles). I have not tested this idea as I am not completly sure how the triangles are made. I have 257 by 257 (X Y Z) points but I do not know how to make the triangles (anyone knows?). Also there should be the problem of changing the "TERRAIN MAX VERTEX LEVEL" and the 4.8 meter/pixel skin to show over 1 meter/pixel skin.Kind Regards, Luis

[Guest Horst]

Hello,Holger, I did a lot of experiments with SB, but never get this error on my machine here!?!Maybe, try different data sets, to make sure it is not the bln file.650 kb bln should never give you a memory problem!Luis,-Finally the maximum number of polygons or lines is 32767Thanks for pointing this out