<?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>ORD Annotating XS Crossing Feature Points</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/213335/ord-annotating-xs-crossing-feature-points</link><description>I am using 2020 U3 trying to figure out the best way to handle feature crossing points (ie. right of way, fence, wetlands, etc.) in a Cross Section Annotation group. I am well aware of the right of way example Cross Section Point Annotation - Troubleshooting</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: ORD Annotating XS Crossing Feature Points</title><link>https://communities.bentley.com/thread/647645?ContentTypeID=1</link><pubDate>Mon, 03 May 2021 13:42:06 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:2cd57c83-a806-4464-8632-79505eb69c30</guid><dc:creator>rclerk</dc:creator><description>&lt;p&gt;Thanks Mark. I noticed your posts on this from years ago, but I was hopeful this was the direction Cross Section Annotation Groups would be headed in by now. Without filter wildcards or more interaction with element information (like item types), all the information from style or&amp;nbsp;symbology manager from InRoads SS2 related to cross sections would need to be explicitly stated line by line as unique Annotation Definitions in ORD.&amp;nbsp;Why not allow&amp;nbsp;more predictive or rule based&amp;nbsp;cross section annotation definitions to cut maintenance down and simplify&amp;nbsp;cross section annotations?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ORD Annotating XS Crossing Feature Points</title><link>https://communities.bentley.com/thread/647498?ContentTypeID=1</link><pubDate>Sat, 01 May 2021 01:45:06 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c4734939-1a65-49f2-ac25-613275225bb4</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately there are no wildcards in the Cross Section element filters and this has made it a constant maintenance task for each project (I have requested this since it was first added to the software).&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regarding integration with named expressions/item types there is nothing like that as far as I know. One recent enhancement is the ability to annotate by Feature Definition Description so you can have a more universal label in place of Feature Name, however there are still some limitations, eg. This only works for Corridor features and not linear geometry (hopefully fixed in the next release).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>