<?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 CE 2021 R2 - Cross Sections - Grid Annotation &amp;amp; Annotation Units Trouble Shooting &amp;amp; Feature Requests</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/239842/ord-ce-2021-r2---cross-sections---grid-annotation-annotation-units-trouble-shooting-feature-requests</link><description>Hello, 
 
 I am looking for some specific help with a cross section grid annotation issue that my coworker and I are experiencing. We have both recently transitioned from V8i to ORD CE 2021 R2 and have been scouring the forum (and google) for specific</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: ORD CE 2021 R2 - Cross Sections - Grid Annotation &amp; Annotation Units Trouble Shooting &amp; Feature Requests</title><link>https://communities.bentley.com/thread/747118?ContentTypeID=1</link><pubDate>Thu, 22 Dec 2022 23:13:00 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:fd4b82af-0aef-4862-bda6-0cf4e77fb9d7</guid><dc:creator>KYLE TITUS</dc:creator><description>&lt;p&gt;Thank you for your reply, I believe that would be a suitable replacement as there is now the ability to show other 3d objects in the model onto the profile sheets&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ORD CE 2021 R2 - Cross Sections - Grid Annotation &amp; Annotation Units Trouble Shooting &amp; Feature Requests</title><link>https://communities.bentley.com/thread/747098?ContentTypeID=1</link><pubDate>Thu, 22 Dec 2022 20:15:21 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:d2b1c2d2-4842-4e60-9df5-4e0ac3e8ef42</guid><dc:creator>MaryB</dc:creator><description>&lt;p&gt;This doesn&amp;#39;t address your main issue, which is very obviously Unit related (I believe Mike is on the right track)...You can cut a profile along any feature you like - it&amp;#39;s not restricted to just &amp;quot;alignments&amp;quot;. If you had a flow/control line feature or such that ran through your drainage network, you would be able to use that to generate a profile/&amp;quot;long&amp;quot; section.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ORD CE 2021 R2 - Cross Sections - Grid Annotation &amp; Annotation Units Trouble Shooting &amp; Feature Requests</title><link>https://communities.bentley.com/thread/747097?ContentTypeID=1</link><pubDate>Thu, 22 Dec 2022 20:10:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:081e1ad6-bce0-4ca7-94d9-e8db85b6a44b</guid><dc:creator>KYLE TITUS</dc:creator><description>&lt;p&gt;Thanks for the quick explanation, Yep, changing the &amp;quot;resolution&amp;quot; to match the dgn lib file has fixed issue (1) where the grid was offset from the actual section so thank you very much for helping with that!&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-discussions-components-files/5922/pastedimage1671738656425v1.png" /&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-discussions-components-files/5922/pastedimage1671739120197v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/176976/openroads-designer-connect-edition---annotation-and-resolution-units"&gt;OpenRoads Designer Connect Edition - Annotation and Resolution Units&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am still experiencing the incorrect vertical grid labels (scaled by 3.048) and the width of the named boundary is still scaling incorrectly. Aside from the design file settings of the problem file, are there other variables I should be looking at?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Edit:&lt;/p&gt;
&lt;p&gt;The issue is resolved now, it was primarily a problem with the units of resolution as Mike suggested. Steps to resolve, recreate the file from a blank seed. When referencing the original dgns the unit issue needed to be addressed. Initially re-creating the sections still had the units wrong (scaled by 10 instead of 3.048) but after a dgn crash i was able to recreate the sections and have everything annotate correctly&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ORD CE 2021 R2 - Cross Sections - Grid Annotation &amp; Annotation Units Trouble Shooting &amp; Feature Requests</title><link>https://communities.bentley.com/thread/747091?ContentTypeID=1</link><pubDate>Thu, 22 Dec 2022 19:07:39 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:b5dfcebc-803c-4598-993d-230a5cc27739</guid><dc:creator>Mike Longstreet</dc:creator><description>&lt;p&gt;Are all your seed files and DGNLIB files using the same units of resolution?&amp;nbsp; They need to, the DGNLIB that contain the Cross Section Sheet definitions&amp;nbsp;needs to match the file you are cutting cross sections in.&amp;nbsp; Just in general all your ORD files need to have the same Units of Resolution within the workspace for annotations and sheeting to scale appropriately.&amp;nbsp; This is also true for cell libraries used with ORD annotations, all cells used should have the same unit of resolution or the scale will be off by the difference factor(s).&lt;/p&gt;
&lt;p&gt;With MicroStation alone this is not an issue typically the &amp;quot;True Scale&amp;quot; functionality within MicroStation mathematically resolves background resolution differences when placing cell or attaching references.&amp;nbsp; ORD does not do that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>