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

Wildcards in filter

A

apollon01

Messages
163
Country
luxembourg
Hi Arno,

Thank you for a wonderful tool. I gave up clicking the autogen manually already a long time ago... and now I discovered scenProc.

I am experimenting... and I have a question related to use of wildcards.

I have noted that * wildcard works when used on its own (like: building=*). Does it work also when looking for a specific string in a filter field?

Example: One of my attributes is other_tags which contains more values. I want to filter only those features that contain "mixed" with whatever before and after that string. I tried
ADDATTRIBUTE|other_tags=*mixed*|les|jehlici but it does not work.

The reason why I want to do it that the attribute other_tags contains (among other things) also information about the type of forest (coniferous, mixed, or broadleaf).

Thank you.

Regards,

Milan
 
Hi,

That's an interesting approach. At the moment you can't do it indeed, but I'll add it to the wishlist.
 
wild card works already; not just as a global delimiter
in many of my scripts i already use something like this type=*_bridge
 
Are you sure? I can't remember I programmed that :)
 
maybe its inherited from another function; it works/ed here (now im unsure too; maybe it broke through the revisions)
im looking at the script right now; i will have to go into the attributes table again to re validate
im pretty sure its working and was validated initially when put in place
 
When I look at the current code I think only a wildcard at the end might work.

But adding the feature as requested should not be too hard. So I'll have a go at it later.
 
Hi,

I had a go at implementing support for wildcards now. It was nice to do some programming again after all the moving work :)

I'll make a new development release available soon that will add better support for the wildcard. Four use cases are supported:

category=* selects the feature when category has any value
category=*ding selects the feature when the value ends with ding
category=buil* selects the feature when the value ends with buil
category=*ildi* selects the feature when the value contains ildi

The wildcards also work for the ! operator, but of course the logic is reversed in that case :)
 
well... that's what I'd call a support!

I will look more closely at the 'support us' section :-)

thanks Arno

Milan
 
No that won't work. The attributes with null values are ignored on import. So the features don't have these attributes at all.
 
Arno,

While tinkering with and trying to improve my configuration file I have noted that most probably the filter including ! stopped working.

I am using your suggestion for dividing the building footprints into 5 categories. While I think it worked OK before I installed the last update, now adding the attribute BUILDING with values 3, 4, and 5 returns 0 results (all of them contain ! in the filter).

Once you have a minute, will you please look into this issue?

Thank you.

Milan
 
Let me check later today. I thought I tested it.
 
I think I know what the difference is. The not equal operator probably works different now when a feature doesn't have the attribute being tested.
 
OK, thanks for looking into this

as for what to do now... is there any workaround that might work in the same way as the not equal ! operator?

Milan
 
I didn't have the time yesterday evening, but I'll try to make a bugfix soon that restores the old behavior. Should only be one line of code to change :)
 
Hi,

I have made the fix now and a new version is online.
 
You must log in or register to reply here.
Back
Top