ORD Automated Template Drops

We managed to create corridors and template drops from excel spreadsheets using the C# API from the SDK but with some limitations or perhaps bugs.

In the template drops the template looks like ignoring the display rules, we need to do a manual update.

There is no way as of now to attach corridor references (feature definitions as triggers and switches) programmatically, although they are a form of point control.

The key stations created programmatically ignore the start station, although created at correct location, when edited dynamically the displayed value is wrong.

Superelevation needs to be in the alignment file, that one perhaps needs some investigation on our part.

We cannot featurize the corridors, don't know why.

We have only one templatezilla that we control with parametric constraints, features (refs), point controls, etc, that we pull from excel.

We can "split" the corridor automatically into several files to cope with large jobs.

It runs in batch mode too, once configured can be run unattended, but one has to mess with the dgnws file and do some config.

There may be other ways to skin the cat, what stage of project you are at and what is the level of detail?

Can you have a single template controlled only by parameters? Parameters can be imported and exported to ASCII files.

Regards,

Val.

We managed to create corridors and template drops from excel spreadsheets using the C# API from the SDK but with some limitations or perhaps bugs.

In the template drops the template looks like ignoring the display rules, we need to do a manual update.

There is no way as of now to attach corridor references (feature definitions as triggers and switches) programmatically, although they are a form of point control.

The key stations created programmatically ignore the start station, although created at correct location, when edited dynamically the displayed value is wrong.

Superelevation needs to be in the alignment file, that one perhaps needs some investigation on our part.

We cannot featurize the corridors, don't know why.

We have only one templatezilla that we control with parametric constraints, features (refs), point controls, etc, that we pull from excel.

We can "split" the corridor automatically into several files to cope with large jobs.

It runs in batch mode too, once configured can be run unattended, but one has to mess with the dgnws file and do some config.

There may be other ways to skin the cat, what stage of project you are at and what is the level of detail?

Can you have a single template controlled only by parameters? Parameters can be imported and exported to ASCII files.

Regards,

Val.

Thanks Val for the reply.  I am still hoping there is a "simple" solution.

You may want to file a Service Ticket with Bentley Support. If there is a way to accomplish this, they should be able to tell you. It would also give you the opportunity to suggest this behavior as an Enhancement. I certainly can see the benefit of being able to import template drop limits.