<?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>Itwin Ad Hoc Review - Openroads Terrain not visible</title><link>https://communities.bentley.com/products/digital-twin-cloud-services/itwin-services/f/itwin-services-forum/220040/itwin-ad-hoc-review---openroads-terrain-not-visible</link><description>Hi, I have followed the steps described here: https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/50786/best-practices-for-creating-a-civil-imodel 
 My terrain model is one with 400k triangles/points so I should not</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Itwin Ad Hoc Review - Openroads Terrain not visible</title><link>https://communities.bentley.com/thread/674921?ContentTypeID=1</link><pubDate>Fri, 01 Oct 2021 14:47:40 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:eaf24fba-c2eb-422e-9202-d752346b7089</guid><dc:creator>Simon Normand</dc:creator><description>&lt;p&gt;Hi Jeremie,&lt;br /&gt;We are actively working on properly saving the Terrain elements in a such way that the Civil tools could easily identify and process them for the profile and cross-section views.&lt;br /&gt;&lt;br /&gt;For now, the workaround has been to assign a Feature-Definition name that starts with&amp;nbsp; &amp;nbsp; &amp;nbsp; Terrain&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; to your terrain elements.&lt;/p&gt;
&lt;p&gt;I hope this helps,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>