In SS4 I could Save As using the option Convert XFM 09 -> 07. After that it was possible to clip the information using fence clip.
In SS10 this does not work (for me).
I've attached two files, one having 09 linkages and one with 07 links. Neither is possible to clip.
Also, if I save the 09 file using Remove XFM Bentley Map specific data some shape turns into Polygon Collection that cannot be clipped either. Trying to drop these elements (Application turned on) will crash MicroStation.
I'm using BM for MicroStation.
Regards,
Krister
bas_SS10_xfm_07.dgnbas_SS10_xfm_09.dgn
Krister,In Ss10, you have the correct workflow to me.
I do not reproduce the crash on my side. Both files results to plain MicroStation elements then.Regards,Sebastien
I will continue to investigate.
I have also noticed that MicroStation (both MS and BM) will crash if a use Save As together with a csv-file when the file contains Polygon Collections.
In my case a can drop the Polygon Collections with plain MS but not with BM
/Krister
Owner consultant at Surell Consulting AB
ok. If you talked about Save As option of csv-file used for remapping, I will say this is not supported with Polygon Collection. I will suggest to save by removing XFM first, Drop by application secondly and remapping plain MicroStation element then.For the drop tool, after Save As by Removing XFM, it gave the exact same results in both MS and Map.
Is Map resulting to "nothing to drop"? You probably need to remove XFM before.
This process have been improved in OpenCities Map CONNECT edition.
In my case I have made a Save As with remove XFM-features as a first stage..
This occurs when I try to save the seconds time.
ok. my bad. I miss a step. Removing XFM will not remove Polygon Collection causing the issue. I should say, removing XFM, drop by application then save as by csv-file to remapping. As I said, Remapping is not supporting Polygon Collection from map. Only MicroStation elements.
Sorry.
Sebastien
Not supported is ok. Crash is not. Elements that are not supported should just be ignored.
Totally agree. I have already reported the behavior to the Product Management. Sorry for the inconvenient. And thank you for reporting.