Hi,
We are designing (re-designing) a map production system. Previosly it was build on plain MicroStation but now we are using Bentley Map. In the end we need to export the finished map to a single dgn file (see image).
The active model contains the frame. The base map and cables are in two, clipped, reference models.
Since the information in the references are features I can't merge, Save As (merged refs). File fence with fence mode clip almost works but asks if I wants to post the changes. If I say No, everything is cleared from the ff-file.
I tried the same operation from plain MicroStation but this resulted in skipped shapes, no merge during Save As etc.
So, what work-flow should I use to create a single file with the same look as the original map? I also want to be able to use that work-flow from VBA.
I'm using SS3 and SS2. Problem in both versions.
Regards,
Krister
I just saw the discussion about Native Features. This is exactly what my problem is all about so we are quite a bunch that think this is a major problem.
/Krister
Owner consultant at Surell Consulting AB
Before you do your save as, place a fence around the graphics to be exported, and on its tool settings, set the fence mode to clip.
Then, when the dialog box opens, there will be an options button near the save and cancel buttons. Press it and on one of its tabs, you can set a filter and specify fence contents. You may also need to tell it to merge reference files - but I would test it a few times with different settings.
Before they had the filter options - V7 and earlier, we used to use the FF= or FENCE FILE command the same way:
This worked in V7 and probably still works in V8.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Sorry, this is exactly what I do. In plain Microstation this works fine, but when you have native features in your file (or references) the graphics will not be clipped. No matter if you use plain MicroStation or Bentley Map.
This is a major problem. There has to be a way to remove the feature information or to ignore it.
Have you seen the tread about using the tool to export the file to MicroStation elements ? I believe, from your description of the process you have been using, that you could proceed from there.
Well, it kind of works. There are, however, a couple of problems:
What would be preferrable is a way to query Oracle "read-only". The result should be formatted and attributed as usual but it should be possible to process the result freely as a normal dgn-file. This includes normal behaviour of Fence File and the ability to do fence clip.
There has been a TR filed today by Carlos Martin on behalf of Tom Lillhannus on the same subject.