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

P3D v5 Does scenProc recognize NULL values?

Messages
1,637
Country
unitedstates
I have a dataset where the field is VegType and the value in there says NULL. Not sure if is a string "NULL" or a numeric value or a null set or what? I have tried using it as a filter in many ways in the Step LineToPolygon such as:

LineToPoint|fclass="residential" AND VegType=NULL
LineToPoint|fclass="residential" AND VegType="NULL"
LineToPoint|fclass="residential" AND VegType=""
LineToPoint|fclass="residential" AND VegType=0
LineToPoint|fclass="residential" AND VegType="0"

But have been able to produce any results?
 
No, when an attribute shows as NULL in QGIS it is not present. Scenproc will simply not have the attribute on the feature in that case.

I think the filter VegType<>"*" should capture that.
 
I did try VegType<>"*" and no go. Let me dig into this a little deeper as I think something is going on here. Below is a screenshot showing a selected area from a polygonal file called Land Cover (highlighed in yellow). It's a very precise map breaking down data to the pixel it looks like.

scenProc QGIS LC highlighted.jpg


(1) Do you think the "holes" in the selection could be effecting scenProc's processing? Because if I use this step:

LineToPoint|fclass="residential"|SINGLE|100|4|50|String;TYPE|WHITELIGHT|HDG

I get lights with no issues. But the minute I add the LandCover as part of the filter like in this step:

LineToPoint|fclass="residential" AND VegType="*"|SINGLE|100|4|50|String;TYPE|WHITELIGHT|HDG

I get no lights at all... anywhere.

(2) Looking at the highlighted area there and several polys selected and some will have different VegTypes inside those polys. Do you think by having a residential road (line) running across different VegType polys (maybe even going back and forth), is overwhelming scenProc so no agn is produced?

So this may not be an issue of "NULL" values but the Land Cover file itself. I do have an older way I would make my LandCover maps so I think I may need to test between the two methods.

Your thoughts?
 
(1) Do you think the "holes" in the selection could be effecting scenProc's processing? Because if I use this step:

LineToPoint|fclass="residential"|SINGLE|100|4|50|String;TYPE|WHITELIGHT|HDG

I get lights with no issues. But the minute I add the LandCover as part of the filter like in this step:

LineToPoint|fclass="residential" AND VegType="*"|SINGLE|100|4|50|String;TYPE|WHITELIGHT|HDG

I get no lights at all... anywhere.
The LineToPoint step only takes libe features as input. So you can't have a polygon in your filter, there will not be a feature matching that filter.

What you maybe want to do is test if the line is inside a polygon that matches the right vegetation type?
 
Back
Top