<?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/"><channel><title>Megan Mcdonald's Activities</title><link>https://communities.bentley.com/members/a06a5432_2d00_7fe0_2d00_499e_2d00_b23c_2d00_d2668aa914a9</link><description>Megan Mcdonald's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Stored graphics alignment not matching actual stationing</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/113495/stored-graphics-alignment-not-matching-actual-stationing</link><pubDate>Tue, 17 Nov 2015 23:52:46 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:d1f74bb4-e968-435c-bf22-25d30d6e1b5f</guid><dc:creator>Megan Mcdonald</dc:creator><description>&lt;p&gt;I am creating an alignment within geopak using &amp;quot;store graphics&amp;quot;. &amp;nbsp;However I&amp;#39;ve noticed that while the length of my alignment should be approx 6028&amp;#39;, it&amp;#39;s only coming out to 5980&amp;#39;. &amp;nbsp;It appears that my curves are being stored shorter than what they actually are. &amp;nbsp;For instance, my first curve is 60.53&amp;#39;, but only storing as 57.80&amp;#39;. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;To add to my frustration, plan view labeling is measuring my stationing correctly - i.e. my first curve station is showing at 200+57.80 (57.80&amp;#39; long curve) per the Design and Computation Manager stationing, but in plan view labeler it&amp;#39;s showing the correct stationing (based on the length of my first curve - 60.53&amp;#39;) as 200+60.53.&lt;/p&gt;
&lt;p&gt;Any ideas? &amp;nbsp;I&amp;#39;ve never seen it happen before. &amp;nbsp;I&amp;#39;m thinking it could be a setting in the design file perhaps? &amp;nbsp;I didn&amp;#39;t set up the original file, so not sure if that has anything to do with it.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Geopak - creating a TIN with csv file</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/110573/geopak---creating-a-tin-with-csv-file</link><pubDate>Thu, 03 Sep 2015 20:31:42 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:53081ece-31b7-4868-ae8d-1e7d303bf5e5</guid><dc:creator>Megan Mcdonald</dc:creator><description>&lt;p&gt;For some reason I&amp;#39;m having trouble getting my csv file to translate into a DTM model/TIN file. &amp;nbsp;Yesterday it seemed to be working just fine, but no matter which avenue I&amp;#39;m taking it never seems to load correctly and I&amp;#39;m stuck without a TIN. &amp;nbsp;What steps should I be following in order to get that set up correctly? &amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>