Where do the settings come for display of horizontal annotation like stationing in SS3? I know that within each style you can turn on auto-annotate which defines if you want annotation on or not, but where do the settings come from? In SS2 users could define a preference which had to be named the same as the style of the geomtery and then similar auto-annotation would occur. Is this the same in SS3?
Also, if I define an element template and assign it to the plan text of this particular style the annotation disappears altogether. Does this imply that the element template settings are ignored when annotating stationing for alignments?
Marc
Inroads SS3
mbachand said: That is incorrect. Within the style of a linear element there is a setting for auto-annotate. When set to 'True" elements with this style are annotated with stationing and cardinal points. I am wondering where the settings for this annotation come from. Marc
That is incorrect. Within the style of a linear element there is a setting for auto-annotate. When set to 'True" elements with this style are annotated with stationing and cardinal points. I am wondering where the settings for this annotation come from.
Marc, it's correct - could you auto annotate without auto export? Quote from bentley Civil Guide best practice: "If you want to use Auto Annotation in order to station your centerlines and baselines when they are created, then you have no choice but to use Auto Export for these particular feature definitions."regards, krzysztof
Marc: As to the problem where line annotation is not removed when adding a curve. This sounds like an oddity of the workflow. I'm speculating some since I haven't seen this demonstrated, but I suspect what is happening is: The line is created and annotated. you add a curve which updates the complex but does not update the status of the original line in GPK file. Thus, although you have a single complex in dgn, the GPK has a line and also a complex, oth of which are annotated.
The obvious fix of course, is simply clean up the extra annotation. For additional guidance about possible better workflows or to investigate possible bugs, I'd suggest placing a support call.
Robert GarrettSenior Product EngineerBentley Systems Inc.
As to whether export is required in order to auto annotate: In GEOPAK, if you want to auto annotate, then you must also set the auto export to true. This is due to the way that the older GEOPAK code works. In InRoads, you can auto annotate without exporting. MX? Not certain but think you must export.
Note that both the auto annotate and auto export are part of the feature defintion, so the exporting is pretty much invisible to the user.
Annotation features need to be defined in the native app such as InRoads XIN or GEOPAK DDB.
Once defined that are set up in the Feature tree in SS3 where Auto Annotate is set to true on those features in the library (DGNLIB) or the active design once used.
Michael Barkasi
Application Engineer
Reality Modeling
I noticed playing with the auto-annotate options that if you modify a chain/alignment and the auto-annotated stationing does not update, simply re-apply the feature definition (choose another and then back to the previous that was set). This forces the export back out to the gpk file and back in to the view to update the annotation. The issue I am seeing is when an alignment is copied to another file or model by another user that this can corrupt the gpk file cause it seems as it is trying to overwrite the chain/alignment. If I left all the resources in place and just used InRoads with all the same tools, does this issue go away?
The comment above about InRoads does not export to do the auto-annotate as GeoPAK does, will this be cleaned up later down the road for GeoPAK when the removal of the gpk goes away and everything is native to the dgn file? creating FeatureDefs to accommodate a ddb file and sync to the gpk makes the auto-annotate feature a void option due to the issues that can arise in the gpk. I would think the majority of users would like to take advantage of the auto-annotate features while designing or they have to stop what they are doing, run the ddb file, station, and if the chain/alignment changes, then I have to delete the old annotation, re-run the ddb again to achieve the result, SS2 workflow using SS3 Civil Horizontal tools....thoughts?