<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Cross Section Width Annotation</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/242844/cross-section-width-annotation</link><description>Hello, 
 Typically, we use the points from the template for slope, so i was thinking to use the points for the width annotation. However, our workspace does not have an existing &amp;quot;width&amp;quot; annotation group so I am unsure how to add the expression to annotate</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Cross Section Width Annotation</title><link>https://communities.bentley.com/thread/757389?ContentTypeID=1</link><pubDate>Tue, 14 Mar 2023 09:32:27 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:28b11f07-2e17-4c40-b3cc-3bbc3856bdb5</guid><dc:creator>Adam Wieczorek</dc:creator><description>&lt;p&gt;Mark,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;In legcy InRoads&lt;/p&gt;
&lt;p&gt;Multiple surfaces annotated on XS - run&amp;nbsp;annotations few times for the same XS set with the different surfaces to be annotated, with changed frame offset. This actually works with ORD as well, but instead of changing the surface to be annotated on the list,&amp;nbsp; you need to change active terrain after annotating in first run.&lt;/p&gt;
&lt;p&gt;Points to be annotated - same as in ORD by Style (Feature Definition now) but also by names, Wild Cards were honored. So for some scenarios, that we had a special points to be annotated we added prefixes in the name to support the workflow.&lt;/p&gt;
&lt;p&gt;Segments - as simple as choosing pairs of points to be annotated. no need to be physically on a template segment&lt;/p&gt;
&lt;p&gt;and frankly, XS annotation engine is one of the very few&amp;nbsp;things I miss from InRoads compared to ORD. Next to reporting and persistent graphic of Thematic Display ;), I guess my wish list is endless :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cross Section Width Annotation</title><link>https://communities.bentley.com/thread/757379?ContentTypeID=1</link><pubDate>Tue, 14 Mar 2023 08:53:53 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:04538614-1299-4a30-94ee-aee840762374</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;Hi Adam, as a non-Inroads user how did you define this in Inroads? In MX, we used wildcards of the string names to annotate, was this similar in Inroads?&lt;/p&gt;
&lt;p&gt;What looks to be missing here is linear feature based slope annotation instead of component segments.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cross Section Width Annotation</title><link>https://communities.bentley.com/thread/757377?ContentTypeID=1</link><pubDate>Tue, 14 Mar 2023 08:48:34 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a2a378ae-8bdc-468e-a3c2-004eabbdee8b</guid><dc:creator>Adam Wieczorek</dc:creator><description>&lt;p&gt;I think we sent at least a few change requests for annotating the distance between points not on a segment. Eg existing traffic lanes widths, the distance between the end of the slope and ROW and fence, etc. Same with slope annotation, annotating existing slope, slope on the bottom layers of the subgrade. Also being able to annotate additional existing surfaces on XS (eg. rock substrata), annotating vertical distance between surfaces (eg. depth of rock excavation) - multiple surfaces with aliasing, the same way as for ORD profiles ....&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;modeling corridors just to be able to annotate slopes or widths between points... no way we will get money for doing this in the project budget. and what with surface templates for junction areas, these are not honored as segment annotation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Waiting for 202R2 with hope XS are improved. too many workarounds to accomplish what was granted in Inroads  &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cross Section Width Annotation</title><link>https://communities.bentley.com/thread/757322?ContentTypeID=1</link><pubDate>Mon, 13 Mar 2023 22:06:17 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a8abd153-10af-42d9-96f3-4930d9049ac3</guid><dc:creator>Derek Schmidt</dc:creator><description>[quote userid="771775" url="~/products/road___site_design/f/geopak-inroads-mx-openroads-forum/242844/cross-section-width-annotation/757288"]Why not use a separate corridor/template to model the existing widths and annotate that way?[/quote]
&lt;p&gt;Probably because the thought never crossed her mind. This question is nearly identical to the question I came to finally this evening, the answer to which is that this is pretty much the only way you can do it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The &amp;quot;segments&amp;quot; annotation type is what you&amp;#39;re looking for but to my knowledge, this requires both points to be non-null and in the same corridor, and possibly even as part of the same component.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cross Section Width Annotation</title><link>https://communities.bentley.com/thread/757288?ContentTypeID=1</link><pubDate>Mon, 13 Mar 2023 18:02:12 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:01104bcc-786a-4539-8506-f9259232afad</guid><dc:creator>Kyle Chism</dc:creator><description>&lt;p&gt;Why not use a separate corridor/template to model the existing widths and annotate that way?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>