Hi all,
I'm trying to bring in data from an AutoCad file. I set up my project in the GSA and now I've cleaned up some of the linework and created shapes. If I promote a shape, I can post it and all is well.
Since there are a lot of elements to promote, post, and attribute, I'd like to select all of my buildings and promote them at once. When I do this I get a message like Converted 213 element(s) into 1 feature(s) and then when I post I get an error that the geometry is invalid. It appears that all of these elements are really being promoted to a single, multipolygon feature.
About my feature setup: I have a structure_existing_area_collection, and I'm trying to promote the to the structure_existing_area subfeature. I have "Created associative regions" disabled under Symbology -> Fill Type.
Any idea what I might be doing wrong here? I thought I'd tested promoted multiple elements before without issue. FWIW, I just upgraded to the latest Map.
thanks, -Rob
Thanks, Jeff. It may be that something about the elements coming in from reference files are confusing DFS.
When I first registered with the GSA there was no data. I assume that element type was taken from the spatial index.
Rob,
Using the provided schema, I was able to perform the following:
Please try the same workflow using first an empty design file (e.g. create file, create level, digitize then RESET FEATURE). What may be occurring is that the design file you are in contains other elements on the Road_Centerline level that is causing the Dynamic Feature Scoring functionality to infer an incorrect feature class.
If your Oracle Spatial tables contain SDO_GEOMETRY with SDO_GTYPE values of 2007 or 3007 then, performing "Register Feature" will result in a polygon collection feature class. If the SDO_GTYPE values are 2003 or 3003 then a simple polygon feature class (e.g. non-collection) should be registered.
Regards,
Jeff Bielefeld [Bentley]
We do have "Use Associative Regions" turned off for all poly features. We might like to allow for complex features eventually, but the associative regions were creating other problems for us.
For linestring features, I did have linework on an appropriately named level, but they were never promoted to editable XFM features. Although the tooltip on hover did say they were "Linestring: Linestring Feature" elements, trying to use the XFM edit tool would report "No edit method for road_centerline". The elements did not post.
We're currently using polygon collections with polygon subfeatures because that's the way they're set up by the GSA when registering Oracle features- if there is a way to use non-collection polygon features instead that would be great. I haven't had any luck with it.
A schema is attached.
You should be able to use the described RESET FEATURE technique with linear features (e.g. lines, linestrings, curvestrings etc...) as well, just as long as the line/linestring elements are created on the level which match that defined in the Symbology section of your linear feature class in the Bentley Geospatial Administrator.
For your polygons, does your feature class enable the "Use Associative Regions" option under the "FillType" setting? If so, you could disable that setting and export your workspace again. If your polygon feature instances are to support holes, then you would want to enable the "Use Associative Regions" setting. Are you using a polygon collection feature class or a non-collection class? Unless you have disjointed polygons that represent a single feature instance, using a non-collection polygon feature class would be recommended.
If you could send me a sample schema (e.g. .xml) which I could load in the Bentley Geospatial Administrator I will review and attempt to duplicate the behavior you are describing with the RESET FEATURE command.