• 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.

ImportOGR hanging

MatthiasKNU

Resource contributor
Messages
962
Country
germany
Hi Arno, hi everybody!

As I have already written, I have another little problem.

Shortly to the prehistory (even if you declare me crazy):
I am in the process of creating a completely photorealistic Africa for my flight simulator. The most of the work is allready done, all of North Africa is already finished, most of it from the south.

Now I have started to create the autogen for it.
I use globcover data for the vegetation - because the OSM data are unfortunately too inaccurate for this purpose.
My "test area" is Namibia.

After processing, vectorizing, etc. the Globcover data, I wrote the following script (for testing) in ScenProc:

Code:
ImportOGR|C:\Users\mknue\Desktop\Namibia\Data\NamibiaVeg_3.shp|*|*|AUTODETECT
#
SplitGrid|AGN|*
#
PlacePointsInPolygon|gridcode=130 OR gridcode=140|0.001;0.001|1;1
AddAttribute|gridcode=130 OR gridcode=140|Integer;HDG|RND(360)
PointToPolygon|gridcode=130 OR gridcode=140|16;16|HDG|String;Tree|true
CreateAGNRectVeg|Tree="true"|{A40B9F9D-72A1-4DFA-83C4-885D8AF9C629}
#
CreateAGNPolyVeg|gridcode=40 OR gridcode=50 OR gridcode=60 OR gridcode=100 OR gridcode=180|{57fb3c8e-db8b-47b0-a012-8305fbf082c2};{7ad672f7-e0d4-455b-85f9-6032d39c0855}
#
ExportAGN|P3D v2|C:\Users\mknue\Desktop\Namibia\texture
The first part is creating the savannah, the PolyVeg-Part is the tropical forest.

The vegetation shapefile is about 40 MB in size.

However, ScenProc hangs just before the end of the ImportOGR process (screenshot)
Even after 5 hours waiting I am seeing no difference.
zwischenablage01cpq97.jpg


I have to admit that in the vegetation-shapefile more than 100 000 polygons are included with one polygone with nearly 400 000 sq km.
The Shapefile:
https://drive.google.com/open?id=1ufp0_SnglQ3UeP9CbqR4RbrYnG0AdXsV

What goes wrong, or does something go wrong at all, or does ScenProc really just take so long to load this shapefile?
And if so, do you have an idea what I could do to accelerate this process?

Thank you again!
Kind regards!
Matthias
 
Last edited:
Hi,

I would have to check the shp file. Just loading data should not take so long, but if there are many holes to process it could take longer.
 
You could test the option to ignore holes and see if that goes faster.
 
Tried it out now, with the DONTPROCESSHOLES-Option it runs through in about 10 seconds...
So it just takes time without this option, but everything else works?
 
I suspect the holes are the problem then. I'll do some testing later today when I'm behind my PC.
 
Hi,

I can confirm it's loading slow indeed, although I did not wait for hours of course ;)

It doesn't help you much, but I have a new feature with improved support for holes in development. I tested the file in there and with all holes it loads in less than 10 seconds. But unfortunately that feature is not yet complete enough for release.
 
Oh, that sounds great!

Don't worry, I'm not in a hurry, I'd rather wait for the new feature!
Thank you for developing! :D
 
Back
Top