Hi,
I thought it should be simple, but it seems it's not:
How to select only inferred (or only native) specific feature? E.g. when I have DGN where there are both native (newly created) and inferred (created in the past) features and DGN consists from more levels with different features, how to select only one type of feature and only inferred?
I found it's possible to search by element type, where the split between native and inferred is available, but element type is not equal to a feature.
Regards,
Jan
Hi Jan,
After using Element Selection by Element Type, you can load selection in Data Browser to see selected feature. It will display a tab by feature, and you will be able to manipulate your selection feature by feature. what do you think?
Sebastien
Hi Sebastien,
unfortunately, your approach does not help,because it does not allow to differ between native and inherrited versions of the same feature.
I need to select all features recognized as "inferred" (because of bug I reported in this post). When Data Browser is used, both inferred and native are displayed together. I also did not find any search criteria that can be used for such selection.
With regards,
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan,
both inferred and native are displayed ? It should only display selected element. Ok. Let me suggest a workflow to you.
Regards,Sebastien
Answer Verified By: Jan Šlegr
Ok, now I understand what do you mean.
I will adapt the procedure to project conditions, it has to start with switching all levels off, so when Line: Inferred features in Element selection tool is used, only one feature is selected.
Frankly, why it's so complicated? My customer, when saw it right now, simply do not understand why it's required to work with levels, element types and at the end, features, when XFM features are searched? Especially when there is knowledge how QGIS and ESRI work.
Greetings Jan,
If desired, you could also craft a few lines of VBA code with XFT using a LocateOp to easily locate feature instances by class, then determine if they are native or inferred, adding whatever is needed to a selection set.
When comparing OpenCities Map to QGIS or ESRI, please keep in mind that OCM is designed to preserve the power and flexibility of CAD (e.g. MicroStation) and add the concept of features for GIS interoperability.
Jeff Bielefeld [Bentley]