• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Processing time for huge shape files

As you see there has not been a lot of discussion since then. In general I get quite good loading performance in scenproc, but of course if you load a very big area it takes longer and uses a lot of memory.

Are you encountering issues yourself and if so what kind of?
 
arno said:
As you see there has not been a lot of discussion since then. In general I get quite good loading performance in scenproc, but of course if you load a very big area it takes longer and uses a lot of memory.

Are you encountering issues yourself and if so what kind of?
Click to expand...
Hi Arno,
I have the same issues with Thorsten. I used the detect feature in Scenproc to detect vegetation in a 300 km2 area, but I ended up crashing my PC. I was using the detect feature because there was no data for vegetation in my working project.
 
That sounds like a different issue, as Thorsten was having issues importing data from SHP.

Does it get stuck while detecting the features? A roughly 20 x 20 km area is something that should be possible to process at once, although it's probably a big image to load. Did you try to process the area in smaller sections?
 
Horst18519 said:
I now have a similar problem with using the Feature Detection. scenproc is running for more than 24 hours now trying to detect features.
I use this code:
Code: 
ImportGDAL|Input_GeoTiff.tif|NOREPROJ

#
SplitGrid|AGN|*
#
DetectFeatures|FTYPE="RASTER"|Detect_Veg_v2.tfc|String;veg|tree|NONE
#
MergeGrid
#
ExportSHP|FTYPE="POLYGON"|veg_trees|C:\Export\veg
It's almost identical with the code from the (very nice!) scenproc manual. (I think you should add "|NOREPROJ" and "|NONE" though in the manual as I get errors using the exact code you used there)

The input file is 1.5GB big, the detection file worked very nice on a small test image in the texture tool. Does the detection time depend mainly on the size of the input image or the values in the tfc file? Would it improve the workflow if I used an image that only includes vegetation areas (like a 1 bit file) instead of using the original geotiff?
Click to expand...
@arno In this post, he was using a Geotiff file. For detection in an image filter, I am using a low-LOD.tif file from SbuilderX for performance in texture filtering, and it works, but when I use Scenproc for detectfeature, it just takes so long. I've waited for 12 hours, and my PC is so low in memory that I can't move my mouse LOL, so I end the process.
Thanks for the reply, Arno.
Screenshot 2024-06-11 150038.png
 
For my vegetation detection, it takes about 8minutes to run a size equal to LOD10 (about 15 square kilometers). But I run 25 scripts total (5 scenProc scripts simultaneously), for around 50 square kilometers and that takes around 1.5 hours. It also takes a good hour to select sample points as I have discovered, if I do not include certain image samples they seem to skip those areas on the results? Not sure why. I use DONTPROCESSHOLES which speeds up processing time. In my TFE script, looking at yours above, I do not use Multi Res Segments. I found using K-Means Clustering works better and faster.

This method works pretty good for me based on my computer specs and how much detail I wish to work on for that area size. Just my 2-cents.

Redding, CA - Day.jpg
 
Wow, that's amazing,i'll try that K-means clustering, this is my scenproc script, im just using script from manual scenproc, and it takes all of my RAM till freeze, i dont know much about scripting
Thanks for the reply anyway
 

Attachments

  • Screenshot 2024-06-13 091731.png
    Screenshot 2024-06-13 091731.png
    20.2 KB · Views: 65
Hi,

The KMeans clustering is quicker than the Multi Resolution Segmentation indeed, but usually the quality is slightly less as well.

How much RAM do you have in your system? And what is the size in GB of the TIF that you are loading? Using all RAM should not happen that quickly normally.
 
Hi arno,
Thanks for the answer.
I have i5-9400f, 16GB RAM, and a 20MB TIF file, and it just takes all of my RAM in around 2–5 minutes.
And also, it gives me this warning. I don't know what is wrong with that. I exported a TIF file from SBX, but it gives me this warning too. Is that the problem with that?
 

Attachments

  • Screenshot 2024-06-13 121912.png
    Screenshot 2024-06-13 121912.png
    10.5 KB · Views: 58
  • Screenshot 2024-06-13 121658.png
    Screenshot 2024-06-13 121658.png
    2.3 MB · Views: 58
That warning explains it, the image you are using is not georeferenced correctly. That means scenproc does not know where it is and then it will take the pixels as degrees. E.g. a 1000x1000 pixel images becomes 1000x1000 degrees in size, which means multiple times the world. In that case splitgrid will indeed take a lot of memory. You need to make sure it's a geotiff with wgs84 coordinates in there.
 
Oh, I see. What do I do?I have to recalibrate that image into QGIS or something so it fits the WGS84 coordinates in there?.
 
Last edited:
Does SBuilder give any other output with the image? Maybe a txt or inf file?
 
Yeah, there are.txt files. I can generate the inf file by compiling the image. By default, the.TIF file is not georeferenced?.
 
I'm not sure if SBuilder does reference them, I think not. Can you send me a sample image and a txt file that comes with it? Then I can let scenproc read them correctly.
 
I have added a new step now ImportSBuilder which can be used to import the SBuilder saved images. This step will use the TXT file to get the right geo-referencing for the image. It will be part of the next development release.
 
You must log in or register to reply here.
Back
Top