<?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>Jack Riesenberg, P.E.'s Activities</title><link>https://communities.bentley.com/members/a8afe246_2d00_6d07_2d00_4da3_2d00_a5fb_2d00_b7bb8838cd4a</link><description>Jack Riesenberg, P.E.'s recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>[MSCE U17] Adding filter to report returns nothing</title><link>https://communities.bentley.com/products/microstation/f/microstation-forum/237711/msce-u17-adding-filter-to-report-returns-nothing</link><pubDate>Mon, 31 Oct 2022 13:56:51 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3f0e4565-67ee-4c78-bb1a-54d256a73bd1</guid><dc:creator>Krister Surell</dc:creator><description>&lt;p&gt;I&amp;#39;m sure this worked before.&lt;/p&gt;
&lt;p&gt;As soon as I add a filter, in this case a level filter, the report returns no rows. If I remove the filter all rows are returned.&lt;/p&gt;
&lt;p&gt;Have I missed something? I&amp;#39;m I getting crazy?&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve attached a small example.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Krister&lt;/p&gt;
&lt;p&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/273/pastedimage1667224348371v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://communities.bentley.com/cfs-file/__key/communityserver-discussions-components-files/273/3750.test.dgn"&gt;communities.bentley.com/.../3750.test.dgn&lt;/a&gt;&lt;/p&gt;
&lt;div class="fskey-tooltip" style="display:none;" id="fskey-tooltip"&gt;&lt;span class="fskey-tooltiptext" id="fskey-tooltiptext"&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Automated Catchment Delineation and Inlet Dimension Settings</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/239548/automated-catchment-delineation-and-inlet-dimension-settings</link><pubDate>Wed, 14 Dec 2022 22:13:15 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4505ccbe-1a73-4ad0-a383-c16ca8042282</guid><dc:creator>Jack Riesenberg, P.E.</dc:creator><description>&lt;p&gt;&lt;span style="font-size:inherit;"&gt;Does anyone know where do change the settings related to where the catchments see the grate location and dimensions? This is in&amp;nbsp;&lt;/span&gt;&lt;span style="font-family:inherit;"&gt;OpenRoads Designer 2022 R1.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:inherit;"&gt;In the example below I have a combination intake. The magenta catchment is linked to the intake shown. You can see the &amp;quot;V&amp;quot; is more or less centered on the origin of the intake rather than the grate. The white catchment is from the downstream intake and seems to roughly match the grate width dimensions but doesn&amp;#39;t match the upstream catchment. Both catchments are also too far upstream on the grate by a few inches but that is a relatively minor issue. The major issue with this is the gaps and overlaps between the two catchments.&amp;nbsp;Overall, it looks like the amount of overlap and missing areas should come out as a nearly a wash. The problem is it raises questions about accuracy and does not look good for plans and exhibits.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:inherit;"&gt;I have messed with the catchment delineation settings and just got more of the same. Changing the catalog inlet dimensions as well as any dimensions in the Hydraulic Properties doesn&amp;#39;t seem to do anything. I also didn&amp;#39;t see anything in the node or catchment feature definitions.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="height:502px;max-height:502px;max-width:825px;" alt="Catchments" height="453" src="/resized-image/__size/1650x1004/__key/communityserver-discussions-components-files/5922/Catchments.png" width="825" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>[CONNECT] Any way to Force Ignore Loading all Nested References?</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/198034/connect-any-way-to-force-ignore-loading-all-nested-references</link><pubDate>Sat, 30 May 2020 06:30:12 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:bde23bfe-8ea4-4925-96a5-7727e6dcd786</guid><dc:creator>Mark Shamoun</dc:creator><description>&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This is a bit of a weird one - there is a bug in OpenRoads Designer where it loads Nested References, even when Nesting is disabled. The display of Nested References is honoured, but you can see them being read on file open and there are numerous &amp;quot;file not found&amp;quot; messages for these Nested references in Message Centre. This is compounded by the fact that files in ProjectWise do not copy out these Nested References (as it sees they are disabled) and we get a &amp;quot;freeze&amp;quot; of the session every time it does something to attach a reference or open a file.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;As there may be sometime till the next release where this will (hopefully) be fixed, does anyone know of any variables that can force the Microstation environment to not load Nested References?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I need all the reference files, but need to somehow force it not to look at Nesting (we don&amp;#39;t use Nesting anyway due to the overcomplexity of tracking OpenRoads dynamic element relationships). As we have dozens of large reference files, each with their own long list of reference files and models, this is really slowing us down.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Mark&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Civil Item Type Priority.json Syntax</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/216691/civil-item-type-priority-json-syntax</link><pubDate>Wed, 14 Jul 2021 16:40:53 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:38a0edbc-6394-4273-9b0e-1c0817526381</guid><dc:creator>Jack Riesenberg, P.E.</dc:creator><description>&lt;p&gt;In the Civil Item Type Priority.json file provided in the workspace, we have examples of the override set to none, first, and last. Is there an option to never pass the item type, and if so, what is the syntax?&lt;/p&gt;
&lt;p&gt;Specifically, we are looking to mimic the previous release for certain tools, like the Single Offset Entire/Partial and Taper tools, where the item type does not come through from the reference element to the new element. Any of the three options provided will pass&amp;nbsp;the item type through to the new element. This would be helpful for things like alignments, curbs, and lane lines, where we are offsetting different features that would usually have different item types.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Civil Display Browser - Why was it&amp;#39;s functionality removed and what is the new workflow?</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/178429/civil-display-browser---why-was-it-s-functionality-removed-and-what-is-the-new-workflow</link><pubDate>Thu, 18 Apr 2019 22:19:36 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:d650e602-ab07-4951-891f-f693409e4804</guid><dc:creator>Jack Riesenberg, P.E.</dc:creator><description>&lt;p&gt;We recently learned that the ability to repair relationships and remove civil rules from elements was removed from the &amp;quot;Civil Display Browser&amp;quot; key-in functionality in OpenRoads Designer. I have scrubbed the communities and have found no acceptable answer to why this was removed or what the new workflow might be to resolve issues with civil rules.&lt;/p&gt;
&lt;p&gt;First of all, the key-in command is hidden and is not something the average user will stumble upon when using the software. I do believe it should remain hidden, but the full functionality was very useful for administrators and power users to resolve problems with civil elements quickly and efficiently. We can&amp;rsquo;t be expected to send a file to Bentley for analysis every time we come across a corrupted file or element. The time this would take makes it impractical, especially when we had a tool that did exactly what we needed before. &amp;nbsp;Using the tool can absolutely mess up a file as easily as it can fix it. As they say, with great power comes great responsibility. But to think users that know about the command, understand the information it provides, and know the implications of rules and design intent can&amp;#39;t use a tool because it might break something is insulting.&lt;/p&gt;
&lt;p&gt;Here is a scenario that I was personally involved in where the repair relationships tool in Civil Display Browser (PowerGEOPAK SS4) saved countless hours of work. We had a rule on our mainline alignment that was corrupted. We had no idea why or what happened but it was causing all kinds of instability with our other files. The alignment is the most important element in any project because of all the elements that reference and rule from it. We had roadway geometry, corridors, off-site models, driveways, side roads, storm sewer, water main, and more, all referencing that one element in some way. Obviously, recreating that alignment would have caused an enormous amount of rework to get the other files to associate to a new alignment. Civil Display Browser was able to isolate the issue and repair the broken rules and the project went on without any interruption.&lt;/p&gt;
&lt;p&gt;Another issue we had was after we converted some SS4 projects to the new ORD format. The files had no issues prior to the conversion process but the files were riddled with broken relationships after the conversion. A few files would crash instantly after selecting any element. Luckily, the projects were in their infancy and to recreate them wasn&amp;#39;t a major issue but still caused about a week of headache and rework.&lt;/p&gt;
&lt;p&gt;So, why the tool was removed in the first place, can it be brought back, and what are the alternative workflows for the scenarios mentioned above?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Is there a way to add comments in the Item Type Expressions?</title><link>https://communities.bentley.com/products/microstation/f/microstation-forum/211319/is-there-a-way-to-add-comments-in-the-item-type-expressions</link><pubDate>Thu, 18 Mar 2021 15:40:27 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:26d0b5b1-daee-4406-a115-e063b5513987</guid><dc:creator>Jack Riesenberg, P.E.</dc:creator><description>&lt;p&gt;I have tried some of the most common comment designators, but I am not seeing a way to add a comment to an expression. It would be helpful for some of the longer and more complicated expressions to have the ability to add notes as with any programming.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Item Type Expression for returning the Parent Folder of a Feature Definition</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/210349/item-type-expression-for-returning-the-parent-folder-of-a-feature-definition</link><pubDate>Fri, 26 Feb 2021 17:00:49 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:941ccb90-82ec-4cff-90ba-2409944e8ca0</guid><dc:creator>Jack Riesenberg, P.E.</dc:creator><description>&lt;p&gt;Is there an expression that will return the parent folder of the feature definition being used? Or the full path which may also be useful in some situations?&lt;/p&gt;
&lt;p&gt;An example where this would be useful is having different categories of signs. You could have multiple features called &amp;quot;Stop Sign&amp;quot; but depending on which folder they are in (Single Lane or Multi-Lane) it will return a different cell size. The expression would allow us to distinguish between two features with the same name&amp;nbsp;when using things like lookup tables.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the meantime, we can use the Feature Description to help, but that could be useful for other information.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ORD 2019R1 - Profile Intersection Point Not Dynamic</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/178923/ord-2019r1---profile-intersection-point-not-dynamic</link><pubDate>Tue, 30 Apr 2019 14:52:08 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c9181f97-3bf5-4a72-9ef9-8ff2789cde90</guid><dc:creator>Steven Litzau</dc:creator><description>&lt;p&gt;Good morning. I was looking to have someone confirm what I am seeing. Namely that profile intersection points created in the latest release are not dynamic. Basic workflow is as follows.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Create two crossing features (I used lines)&lt;/li&gt;
&lt;li&gt;Develop profile for one feature and set it active.&lt;/li&gt;
&lt;li&gt;Use &amp;quot;Profile Intersection Point&amp;quot; tool to show that profile on the crossing element.&lt;/li&gt;
&lt;li&gt;Move (either vertically or horizontally) either line.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The previously created intersection point stays at it&amp;#39;s previous location and nothing is created at the new intersection location. The point does move to a &amp;quot;default&amp;quot; symbology dropping what was defined in the intersection settings in the feature definition.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Steve&lt;/p&gt;
&lt;p&gt;OpenRoads Designer CONNECT Edition - 2019 Release 1 Update 7 - Version 10.07.00.56&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question I</title><link>https://communities.bentley.com/achievements/460ac7df-7ccc-4c42-a204-9e05eef3be09</link><pubDate>Thu, 18 Apr 2019 03:24:58 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:fe3a5775-8f44-46a0-aee6-5940d0235838</guid><dc:creator /><description>Ask a question in a forum.</description></item><item><title>ORD 2018 update 4, civil display browser - we cannot delete any element now?</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/173642/ord-2018-update-4-civil-display-browser---we-cannot-delete-any-element-now</link><pubDate>Mon, 14 Jan 2019 16:03:41 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f4c67a8e-ca02-47bb-8729-d99d812d4ad9</guid><dc:creator>JeremieDL</dc:creator><description>&lt;p&gt;We use to be able to delete some corrupted elements (because that do happen with corridor element and or civil geometry) using the command key-in &amp;quot;civil display browser&amp;quot;&amp;nbsp; but now it only display bad elements.&amp;nbsp; Now what is the way to do?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>