GDI Imort creates wrong type of a parcel with an inner parcels

Re: GDI Imort creates wrong type of a parcel with an inner parcels

Tom Torell — Mon, 11 Mar 2013 15:07:45 GMT

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

communities.bentley.com/.../8508.01_5F00_CreatingTestData_2D00_Export.mp4

communities.bentley.com/.../0638.02_5F00_ImportingBack.mp4

communities.bentley.com/.../3731.03_5F00_TestGmlImport.mp4

Re: GDI Imort creates wrong type of a parcel with an inner parcels

Lillhannus — Sat, 02 Feb 2013 01:12:18 GMT

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 :)

Re: GDI Imort creates wrong type of a parcel with an inner parcels

Jeff Bielefeld — Sat, 02 Feb 2013 00:08:02 GMT

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.

Re: GDI Imort creates wrong type of a parcel with an inner parcels

Tom Torell — Fri, 01 Feb 2013 22:08:20 GMT

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

Re: GDI Imort creates wrong type of a parcel with an inner parcels

Jeff Bielefeld — Fri, 01 Feb 2013 20:31:56 GMT

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.