Hi,we have a serious problem with the GDI Export and Import. We use the Import tool, to fill in the DGN from an Oracle Database. It seems that parcels with holes are imported not in the right way. Unfortunately these cases appear frequently in our cadastre project. I can reproduce this behaviour interactively with Bentley Map:When I create a parcel with an inner parcel interactively, I get a grouped hole. When the import process creates exactly the same parcel, I get a parcel of type Polygon Collection.This happens in a cadastre wizard created project, all options answered by default.Here is the description, what I'm doing in the video. If it is too small use strg + scroll the mouse:- I'm using the latest version of Microstation and Bentley Map actually available from Bentley download.- I've created a parcel with an inner parcel interactively.- I turn on labelling in the map manager for the parcel (Area).- The area label is shown in the right way for the outer and the inner parcels.- The parcel I created is of type grouped hole.- I export the parcels in a GML file.- For the following import process, I delete the Parcels. I delete them, deleting the three boundaries. While I delete them, the parcels are deleted by the syncronizer.- Now I import the deleted Parcels back from the GML file, expecting to get the same data set as before.- Unfortunately labelling is not ok. anymore: The holes now show two labels, their own area and additionally the area of the outer parcel on top of it.- Looking at the element type: It now has changed from a grouped hole to a Polygon Collection.- When I try to delete the data set, it is possible to delete the three boundaries, but the syncronizer can't delete the associated parcels. They still stay in the DGN.Looking at the created GML file attached to this post, I can't see a problem. The outer parcel has three boundaries, one exterior and two interior linear rings. (I had to attach .txt extension to the file because *.gml is not allowed for upload)Please help!Regards,Tom
Jeff, I made some more tests this morning and now I hope I got closer to the core of our problem! Video 1: - I'm creating two sets of test data. The first is working fine with our workflow, the second (with holes) leads to errors. - I'm showing, the structure of the parcel with the two holes created with BM Cadastre: Polygon Collection 1 -> Shape Polygon Collection 2 -> Shape Polygon Collection 3 -> Grouped Hole - I export this to GML and delete the test data Video 2: - I import back the test data - I run the command "cadastre topology from existing" - The first test case without holes works perfectly! - Then I look at the data structure of the second case: Polygon Collection 1 -> Shape Polygon Collection 2 -> Shape Polygon Collection 3 -> Shape, Shape, Shape (all solid, no hole, no grouped hole!) - When I move a vertex, BM Cadastre creates a group hole element. Now the structure is: Polygon Collection 1 -> Shape Polygon Collection 2 -> Shape Polygon Collection 3 -> Shape, Shape, Grouped Hole (I think the two shapes here are not right here) - When I do something more, e.g. cutting off an edge, the test case gets ok: Polygon Collection 1 -> Shape Polygon Collection 2 -> Shape Polygon Collection 3 -> Shape Polygon Collection 4 -> Grouped Hole This is exactly what is going wrong with our workflow. After we ran the "cadastre topology from existing" command against the Parcel with a hole, it is a Polygon Collection without an associated Grouped Hole, but BM Cadastre always works with this structure: Polygon Collection x -> Grouped Hole
Video 3:
- Perhaps I have a little bit more information that may be helpful- Testing DWG-Import, I found, that "cadastre topology from existing" works fine with simple Shapes without any Type 106.
- My point of view is, that the first part, the GDI-Import fails. It creates a flat structure
Polygon Collection 3 -> Shape, Shape, Shape (all solid, no hole, no grouped hole!)
and the following "cadastre topology from existing" is not able to create valid parcels from these faulty data.
- If you simply put in three shapes, the result is as expected.
Regards, Tom
Hi Tom and Jeff
Jeff, when you was in Stockholm you showed us the new survey functionality in BM SS3 rel2 "that what isn´t aviable through dialogbox as I understood..but anyway", in survey application there should be an import function for LandXML but if that function handles features like containing holes to create polygon Collections thats a different question .
Regards The other Tom :)
Tom,
The only import tool that I'm aware of is the "Cadastre > Topology > Import LandXML" one. As mentioned, you may find that development of a custom importer may be required. Maybe you can contact me offline and we can further discuss your specific data modeling and workflow requirements.
Regards,
Jeff Bielefeld [Bentley]
Jeff,as I understand you, the Interoperability application is a Bentley Map Application and not an App of the cadastre configuration. So probably we are using the wrong import tool to create cadastre features from our Oracle DB.Is there a better import tool we can use for our GML? Perhaps the cadastre import / export?Regards,Tom
The Interoperability application when importing area features containing holes is designed to create polygon collections and not grouped holes. This due to the fact that grouped holes are not easily edited using standard MicroStation primitive tools. When using the cadastre configuration of Bentley Map it seems that parcel data when exported to GML and then imported back is changing from the cadastre persistence format (which uses the synchronizer and persistent topology) to the standard Bentley Map format which uses polygon collections. Therefore as currently designed I'm not certain this particular import workflow would be possible without developing some custom import code that would write the imported feature instances using the expected cadastre configuration format.