Hi
I have just upgraded my PowerMap to the new SelectSeries 1, and I have now some problems with some of my VBA application that uses the Xft-object.
I seem that nonXFM element (= simpel microstation elements) are treated in a new way by the Xft object. Some times, but not allways it seems, microstation-elements are treated as a subfeature to a collection feature.
Exampel:
old V8i version would treat an element on level "Skel" as a feature "Skel", now SS1 version will treat a element on level "Skel" as a subfeature to a feature "Skel_colletion" but only until I have created the first "Skel" feature from my VBA application, then it seem that it works like the old version and treats simpel element on level "Skel" as feature "Skel".
I am more than a bit confused; so. could some one please point on some documentation that explain how this works (and maybe why) or may be give me some enlightment here on the forum :o)
Erik Wirring
LE34, Denmark
The DFS ( Dynamic Feature Scoring) interface has changed from previous versions. This is to accomidate the issues raised by users when importing data from external sources ( Acad, non-Map DGN files, etc.) and posting external data into a spatial database. In the past if you placed graphics on a level that had the same name as the feature, and the geometry type matched the feature, then the XFM engine 'assumed' this was a instance of the feature. Though this worked fine for dgn based features, this did not work so well for spatial database features. Thus the DFS was updated and there was a 'promote' functionality added to the standard feature library, to assist.
How this affects your VBA, and what you need to do to fix your application, I do not know, at this time.
There should be documentation, in the product, discussing this change.
HTH
Jerry
I am a little desorientated.
What documentaion are you refering to ?
The documentaion for the Xft object is still very sparse and poor, and there is as far as I can see nothing new in that and nothing about the DFS or the change in that.
Erik
The change was not made to the XFT api itself, that api continues to work on features. This change was done internally in the DFS engine that featurizes standard geometries to support collections.
Martin
Hello Erik,
When XFM / DFS recognizes an element in a feature class that is new to the session (either not defined in the XFM schema or previously inferred from some element), then if the element is a closed element, a polygon collection feature definition is created.
This behavior may be disabled by setting the following configuration variable:
MS_GEOXFM_NO_CLOSEDELEMENTCOLLECTIONS - If this variable is set to any value then the XFM / Dynamic Feature Scoring (DFS) engine will not create polygon collection feature definitions for closed elements whose feature names are new to the session. The default behavior is that a polygon collection feature definition is created for a closed element whose feature name is new to the session.
When you read an instance of this feature into a XfmFeature object, then the polygon geometry is loaded into the sub-feature object(s). If the polygon geometry is a grouped hole, then each closed element within the grouped hole is loaded into a separate sub-feature.
Regards,
Chris
Hello Chris
Thanks for the answer, it helped me understanding the procress going on when working without a XFM-Schema.
Could you tell me the reason for handling 'Grouped hole' as a feature collection instead of a *grouped-hole' cell. Are there some benefits within the XFM when handling this as a feature collection ??
Best Regards,