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

AdAttributeIfInside step

Vogel

Vogel

Messages
211
Country
france
I have experimented the ADDATTRIBUTEIFINSIDE step in my script, and I feel that this function is much slower than old Scenproc revision (2015-2016) ... It's me or the algorithm and/or processing library has been changed since then?

Otherwise maybe someone knows a batch or a command line (ogr2ogr or equivalent) that would have the same function ... as the "selectbylocation" function of QGIS ?

In summary, I have a shp file that contains points and a shp file that contains polygons ... I want to create a new shp file that contains only the points that are contained / included in the polygons.
And most importantly, I would like to automate this function for a large number of files ...

Scenproc in "batch" mode was perfect for this but today it seems to be more difficult to keep great performance... Any idea?

thank for your help :)
 
Last edited:
Temporary Resolved: So it wasn't just a feeling... I've just reload an old Scenproc revision (v1.0.0.0 r2810 02/06/2014) convert and launch my new script... the process take 90 sec with old one vs more than 15-20 min with new one...
 
Last edited:
That's a huge difference. The algorithm had some improvements to fix bugs, but no fundamental changes. Would you have a sample file for me to test with?

Also which step takes most time? Importing data or the inside testing?

If the features cover a big area splitting it in a grid first might help, since you can parallel process then.
 
You must log in or register to reply here.
Back
Top