Is there anyway to export dgn text elements to TAB text

Hi Tom

As far I know, only XFM features can be exported from Map Interoperability.

Hi Tom

As far I know, only XFM features can be exported from Map Interoperability.

Hi

All other dgn elements (almost) except text elements are aviable to export throght Map Interoperability and there is an workaround to manage the whole thing but that is to go outside dgn, that is to save the dgn as an dwg file and then import the dwg throught universal translator (built in) into MapInfo and the text elements are imported as text in MI.

Is it worth to create a CR for this issue ???. What do you think about it.

It would be great to be able to export the RAW dgn file and get all the information from it to TAB.

//Tom

Tom,

I believe a change request that could potentially expose text string values as business properties for inferred features would be worthwhile. This would allow you to simply open a MicroStation design file in Bentley Map and use the Interoperability application to export the desired MapInfo TAB or MIF/MID file, including the text string values as business properties. However there are a number of factors we must consider (such as potential performance impact) before extending the product with such a change.

Until then, conversion of your inferred text features to XFM native features with text string values converted to business properties is a simple process. Using the following VBA code you can locate text elements on a particular level (using the inferred feature class name) then simply iterate through the resulting feature instances, adding a business property based upon the text string.

The first bit of code defines the search criteria and determines whether or not you want to use fence, selection set or entire design file processing.

The second bit of code iterates through the resulting features and creates a new business property based upon the text string value of the MicroStation text element.

Please note that after running the conversion, you will need to close/reopen the design file (or simply keyin newfile) so that Bentley Map can recognize the fact that your previously inferred features are now native XFM feature instances with a feature class definition containing business properties.

I've attached an archive containing the above example.

Jeff, Jeff thank you again!!!

Can´t you come to sweden to answer some (minor and difficult) questions, hold an sessions for couple of days to sort out a LOT of our problems for the future use of BM. It would be so much easyer to implement BM if these kind of answers would be aviable to manage as you can.

There seems to be answers to almoust every problem that occure in BM, but the answers are coming from the other side of yhe ocean and the time differences and prioritys for support is dependent how you folks work, so please consider to force some of your experties to be aviable in Europe also!!!

Or Jeff, sweden is an nice pleace to live in if you wan´t :)

Best regards

Tom

BTW. I think that Bentley corp. mind is to enginneering, because of these kind of comments "However there are a number of factors we must consider ". I know is good to consider one thing to another , but in engineering (modern) in my oppinion it would be better to get some kind of "neutral" solution first and then improve it rather than skip the idea totaly because the engineer break quote " However there are a number of factors we must consider ". Take more chances in product development and sort thr bad ideas from the good by users testing and use resaults. I think that a lot of cr:s are just for this reason, Bentley, get more attitude and spine to bring forward "un considered solutions", do as me "think outside the box".

Thanks

Tom

Tom,

I had a similar question from a user somewhile ago. I made VBA based on Jeff's example from his previous replay.

With the attached VBA a property is loaded from a textstring. The text (or text node) will become an XFM feature and the property is loaded with the text string. If the property already exists it is updated.
The dialog offers:
•    A list with available features that is deferred from the XFM schema and optional from the available levels.
•    A list with existing properties from the selected feature. If needed, a new property name can be entered.
•    Optionally the rotation of the text string can be stored in a property.
•    With the Process button the whole DGN file is scanned for the selected input feature.

As a result the text strings can be exported to SHP and MapInfo.

Regards,
Kees

Hi Kees

Tested your vba today, excellent.

Thanks

Tom