Hi,
I have a working Bentley Map project created from GSA. In my workflow I would like to acess most of the layers read-only for plotting purposes. This means that I also want to do a fence void clip to remove everything outside the plot frame. I cannot do that on data read through gdi query. I then tried to use gdi import instead but then I get the error message:
Failed to insert the provided instance with id = 0 and class name = LED_TEXT into the XFM storage.
LED_TEXT is the first layer it tries to read.
What is the prefered workflow if I want to get read-only layers from Oracle and also want to be able to delete the data in the file?
Regards,
Krister
Query the data as you usually would. Create a Map model and attach the data in the queried model as a reference. Use a fence to apply the clip boundary for the reference file.
HTH
Jerry
Krister,
In the Bentley Geospatial Administrator, when registering your Oracle Spatial layers, if you do not assign a sequence generator to the layer you have effectively defined a "read only" layer (e.g. users can query geometries but cannot post changes back). So as Jerry correctly states, you could query the feature instances into a design model and use the suggested reference/clip approach or you could leverage the existing Print Preparation functionality of Bentley Map to perform your clipping etc...
Jeff Bielefeld [Bentley]
Yes, the layers are read-only since they don't have a sequence. Since they are read-only, I cannot figure out why I can't modify them as I please? Putting them in a separate model means that I could clip the information, but that require some major workflow changes (this is an old project that is converted to Bentley Map). Isn't there a way to "drop" read-only data read through "gdi query" to plain MicroStation elements that can be modified as I please?
Owner consultant at Surell Consulting AB
Hi. the Oracle node, query operations etc are for 2-tier connections where the instances you see in the dgn are really just proxies for the information in the database. By design you cannot modify them unless you hold a lock to the instances and you intend to post that change back to the database.
Import on the other hand is the means by which you transfer information into the dgn where the end goal is to have a copy of the imformation. You could use the fence to limit the instances you import, and you could afterwards clip as you wish. However there are some limitations on the clipping operations of Microstation that Bentley Map supports simply because not all operations would result in valid XFM instances. For example, a polygon instance sitting on the border of your clip could become a line, and that is not valid.
That is why it is easier and safer to reference the data into another model and use the clipping service of the reference mechanism to ensure you only display what you want, without necessarily trying to change the instances.
Martin
Ok, I'll try to do some redesign for the plotting workflow.
My original question, however, has not been answered. Why can't I do a sdo import on the same information I can do sdo query on (see error message in the original post)?
Also, it would be great if I could use Bentley Map for all task, not only the map related ones. This includes standard MicroStation stuff like clipping, element selection also behaves strange in Bentley Map. For now, you have to run plain MicroStation for certain task.