• 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 extended Filter?

MyPC8MyBrain

MyPC8MyBrain

Messages
596
Country
us-california
i was watching scenProc today loading my data from 21 sources simultaneously
i have to say i am very impressed with how stable and fast scenProc has become over time
the small increments eventually add up to really fast and stable platform, i love it more than ever!

back to my opening sentence (got little sidetracked there)
i realized i can speed things up by adding the RequiredAttribute filter
which is nice to have, but still doesn't really make a huge impact as i expected it to (prob works better with raw OSM import)

do you think it will be possible to extent the RequiredAttribute filter to type=something
to further speed things up and minimize memory usage for big jobs
especially if one is pulling one or two attributes from 21 sources :)

what’s your thoughts about something like this?
 
Hi,

I have to check. Adding a more complex filter might also slow things down as it could require more checking during import.

As we discussed by email already, I think I have a better way to save memory when processing big areas. Then this kind of fine tuning is probably not needed anymore.
 
You must log in or register to reply here.
Back
Top