ORD U6 - Annotate Template Corridor Feature Definition Geometry

Hi,

I am yet to look into this fully but is it possible to annotate 3D geometry created by a template drop?

I have assigned a feature definition to my road channel template point but currently, based on my understanding, element annotation is limited to civil geometry.

My EOP is defined with civil geometry in 2D space, the Z coordinate is unknown until an EOP point control is set on the template corridor. Once I set my point controls I can see the feature definition line in 3D space but how can I get those Z levels to assign themselves to the 2D EOP civil geometry? I guess it would be like using point controls to create profile lines???

If what I'm asking isn't clear I'll try again to explain.

Josh

Parents
  • Josh

    It sounds like you want to annotate (say) the Z value along the EOP. Is that right?



  • Yes but the catch is the Z is not defined by a civil profile line.

  • I have done a simple experiment and have my EOP annotated every 10m using an annotation group I called EOP_Anno. The EOP was created in a corridor with a template, so that is how it got its elevation.

    I set the Annotation Group in the Feature Symbology properties for the EOP. Note that the 10m is measured along the EOP, so annotating the other side of the road will not have the annotation in the same place i.e. the text will not be lined up.

    I have attached the Annotation Group definition if you want to see what I did. Create a new Plan\Linear annotation group, and then import the file.

    <?xml version="1.0" encoding="UTF-8"?>
    <AnnotationDefinitions>
      <AnnotationDefinition name="EOPZ">
        <AlignmentPointAlongAnnotation xmlns="GeometryModel.00.00">
          <Where>
            <AlignmentWhere>0</AlignmentWhere>
            <IncrementOption>0</IncrementOption>
            <IncrementValue>10</IncrementValue>
            <IncrementSkipValue>0</IncrementSkipValue>
            <StationOption>0</StationOption>
            <StationValue>10</StationValue>
            <StationSkipValue>0</StationSkipValue>
            <HorizontalPointMask>0</HorizontalPointMask>
            <VerticalPointMask>0</VerticalPointMask>
            <HorizontalComponentMask>0</HorizontalComponentMask>
            <HorizontalComponentOption>0</HorizontalComponentOption>
            <HorizontalComponentIncrementOption>0</HorizontalComponentIncrementOption>
            <HorizontalComponentIncrementValue>1</HorizontalComponentIncrementValue>
          </Where>
          <With>2</With>
          <PlaceLeader>True</PlaceLeader>
          <BegLeaderOffset>0</BegLeaderOffset>
          <EndLeaderOffset>0</EndLeaderOffset>
          <ArrowSize>0</ArrowSize>
          <ArrowWidth>0</ArrowWidth>
          <CircleSize>0.0001</CircleSize>
          <SquareSize>0</SquareSize>
          <TriangleSize>0</TriangleSize>
          <ExtensionSize>0</ExtensionSize>
          <RotationOption>3</RotationOption>
          <Rotation>0</Rotation>
          <PerpendicularOffsetOption>0</PerpendicularOffsetOption>
          <PerpendicularOffset>-0.001</PerpendicularOffset>
          <TangentialOffsetOption>0</TangentialOffsetOption>
          <TangentialOffset>0</TangentialOffset>
          <Length>0</Length>
          <XScale>1</XScale>
          <YScale>1</YScale>
          <ZScale>1</ZScale>
          <ApplyActiveCellScale>False</ApplyActiveCellScale>
          <ViewIndependent>False</ViewIndependent>
          <ViewReadable>False</ViewReadable>
          <Template />
          <LeaderTemplate />
          <Name />
          <Prefix />
          <Suffix />
          <Style>Arial 1.8 mm Rt Ctr</Style>
          <Favorite>Text Favorites_Text Styles_Dimension Styles UK.dgnlib/Point Elevation</Favorite>
        </AlignmentPointAlongAnnotation>
      </AnnotationDefinition>
    </AnnotationDefinitions>



  • Thanks Mark, I am checking this myself now.

    Given that this is strictly a 3D line does the annotation group need to go in Linear or Linear3d?

Reply Children