Trouble with Dynamic Feature Scoring (DFS)

Hello all,

I try to use DFS in a really simple structured project with only a few features. Here's an example: a linear element (line, line string) on Level 2 which is blue (color 3) should be designated as "my.feature". I tried the following syntax in my dfs.xml file:

<FeatureScoringRules minScore="3">

<Feature useCriteria="" name="my.feature">
<Rule type="CExpr" score="1">XFMCompareElementLevelName("Level 2")</Rule>
<Rule type="CExpr" score="1">XFMCompareElementColor(3)</Rule>
<Rule type="Element" score="1" ElementType="3-4" checkZeroLengthLineElementType="false"/>
</Feature>

</FeatureScoringRules>

MS_GEOXFM_NO_LEVELFEATURES and MS_GEOXFM_NO_CELLNAMEFEATURES are turned off, because I'd like to control what happens in my dfs file. I don't like any features to be assigned by just by level or just by cellname.

In addition, I renamed the file FEATURESCORING.XML which is automatically created by the GSA system during the export process. My goal is to make it inactive this way, so I renamed it to .xml_. What I don't really understand is: if there are two dfs control files and both are recognized by the system, there is a chance that they have contradictory contents. Which one is evaluated by Bentley Map in that case?


Now, when I open a dgn file using my above dfs I expected the existing elements that reach the minScore of 3 as well as new elements to turn into native "my.feature". Instead, I find two things: first, none of my existing blue line strings on Level 2 turn into features. Second, if I digitize new lines on Level 2 in blue, they become "Inferred feature: my.feature". But, the system doesn't care what element type they are!! That is, a blue circle or a blue text on Level 2 also becomes "my.feature", which makes no sense. The syntax I used is exactly like it is explained in the "Bentley Map-DFS Notes.docx" document.

It seems to me that the dfs is working in principle, being the problem that the rule type "Element" is always considered true. If I set the minScore to 4, then no new elements become features any more.

Any ideas? Thanks in advance, Uwe

Parents
  •  
    Featues recognized via DFS are inferred features if  they are not tagged as a native feature and thus are ‘inferred’ by their level and geometry type. To test this, place a simple line (place line tool) on one of the levels where a typical linear feature would be stored. This will then be a ‘inferred’ feature, because you did not place a GIS feature, you placed a line, but youplaced it ont eh level and with the geometry of the linear feature.
     
     
    Jerry Walter
    Geospatial Advisor
    Mapping - US and Canada
    +1 937 205 3674 (office)
    +1 937 205 3674 (mobile)
    Skype : jerry.walter.troy
     
     

     

Reply
  •  
    Featues recognized via DFS are inferred features if  they are not tagged as a native feature and thus are ‘inferred’ by their level and geometry type. To test this, place a simple line (place line tool) on one of the levels where a typical linear feature would be stored. This will then be a ‘inferred’ feature, because you did not place a GIS feature, you placed a line, but youplaced it ont eh level and with the geometry of the linear feature.
     
     
    Jerry Walter
    Geospatial Advisor
    Mapping - US and Canada
    +1 937 205 3674 (office)
    +1 937 205 3674 (mobile)
    Skype : jerry.walter.troy
     
     

     

Children
No Data