Problem promoting multiple features

Hi Rob,

For now, only non-collection feature can be promote to a multiple single feature in the same time. As you reported, for a collection feature, it will promote all selected/fenced elements to a single collection feature with multiple sub-features.

For now, what I can suggest to you, if it is a possibility in your project to make that change, is to change feature type from collection-polygon feature to polygon feature. Then, we will be able to promote all these in one click.

Sorry for that weak option, I will try to find you a better solution by consulting colleagues.

I hope that will help you.

Sébastien Lefrançois
Associate Software Quality Analyst - Geospatial Products
Bentley Systems Inc.

 

Thanks Sébastien,

Is there a way to do that by updating the features in the GSA or do I need to create new features? I tried changing the type for my collection feature to polygon- so now I have a polygon feature with a polygon subfeaure. I updated the placement commands and the command manager after the change. I can now promote multiple features correctly and view/edit their individual attributes, but I can't post them to Oracle- no errors, just 'Post Complete (0 features)'. Also, the polygons don't get the feature symbology.

These are Oracle Spatial features, so the polygon-collection with a subfeature is automatic when I register features from the database.

I guess there are three possible paths forward:

- register polygon features from Oracle without creating collections (I don't see an option to allow this)
- change the collection features to normal polygons after registration (unless I've got something wrong this doesn't seem to work, as above)
- manually create polygon features without subfeatures and register them as Oracle Spatial features (not aware of a way to do this)

If you have any thoughts or advice, I'd definitely appreciate it.

-Rob

Rob,

To convert the shapes you've created into individual structure_existing_area_collection feature instances, you should be able to use the following workflow:

1. Use your originally defined schema that contains the structure_existing_area_collection feature class definition, including the structure_existing_area subfeature.
2. Process your linework and create your shape elements on the structure_existing_area level which matches the level defined for your structure_existing_area subfeature. This allows the Bentley Map DFS (Dynamic Feature Scoring) functionality to infer the feature class of your shapes based upon their level.
3. Using the fence option, perform a "Tools > Geospatial > Utilities > Reset Feature" command to convert the inferred feature instances to native feature instances with any defined business properties. In your case, the result should be individual structure_existing_area_collection feature instances.

After performing the FEATURE RESET command, you should be able to edit and post your structure_existing_area_collection feature instances into Oracle Spatial as desired. If this process does not produce the desired result, please let me know.

Regards,

Jeff Bielefeld [Bentley]

That works, thanks Jeff!

Followup to this: We've been able to promote and post some elements but are seeing some converted into shapes and associative regions, which won't post and can't be attributed.

I've been trying to create a consistent reproduction of the problem but haven't had much luck. I can fence some buildings, use Reset Feature, use ctrl-z if they aren't converted to real shape features, then Reset Features again without re-placing the fence, and it will work properly (sometimes).

 Any thoughts? I'm guessing that something I do is affecting the scoring mechanism, but I'm at a loss to explain it.

 See attached screenshots.

Followup to this: We've been able to promote and post some elements but are seeing some converted into shapes and associative regions, which won't post and can't be attributed.

I've been trying to create a consistent reproduction of the problem but haven't had much luck. I can fence some buildings, use Reset Feature, use ctrl-z if they aren't converted to real shape features, then Reset Features again without re-placing the fence, and it will work properly (sometimes).

 Any thoughts? I'm guessing that something I do is affecting the scoring mechanism, but I'm at a loss to explain it.

 See attached screenshots.

followup #2: For lines/linestrings it appears the XFM promote methods for each line feature are the way to go. I haven't had any luck using Reset Feature to turn lines into features. Is that correct?

Rob,

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.

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.

Rob,

Using the provided schema, I was able to perform the following:

1. Open schema.xml in the Bentley Geospatial Administrator, modifying a few paths to accomodate my local Bentley Map installation.
2. Exported workspace.
3. Created new work.dgn design file using 2dEnglish.dgn file from delivered sample files.
4. Open work.dgn, created new Road_Centerline level, made Road_Centerline my active level.
5. Used MicroStation PLACE LINE command and digitized a few lines on the Road_Centerline active level.
6. Used RESET FEATURE command in fence mode to create new "Road Centerline" feature instances.
7. Perfomed "Edit Feature" and was presented with "Edit Road Centerline" form with all applicable business properties.

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]

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.