Taylor Brownlow's Activities

Function to create points automatically at parcel vertices?

Taylor Brownlow — Mon, 14 Aug 2023 20:18:02 GMT

Hello,

I was wondering if this is a function in OpenRoads?

We have hundreds of parcel chains, some overlapping sides, and were wondering if it is possible in ORD to avoid having to create a point for each parcel vertex and then snap to that point for Right of Way table purposes. Previously in InRoads we would use the "Assign Names" and "Horizontal Event" utilities to create the parcel chains and assign cogo points to each vertex (removing coincident points.

Thank you!

Plotting parcel shape overlaps with solid lines

Taylor Brownlow — Mon, 13 Feb 2023 15:54:38 GMT

Question: Is there a best practice for keeping close parcel shapes and ensuring they print correctly, i.e. not as a solid line?

Explanation: When we receive property data from our survey department, the property lines are closed shapes complex elements with ruled geometry. When we print these shapes often there are overlaps and the dash-dot linestyle appears as a solid line. Usually we would just break the parcel shapes and delete any duplicate or overlapping elements. Since these are ruled geometry and essentially Inroads chains we don't want to drop them. Our workaround now is to create another model in our property file and in that model have the dropped geometry, referencing that model and it's "dumb" lines into our drawings to ensure no overlaps.

Thank you for the information!

Ask A Question I

Mon, 13 Feb 2023 04:39:02 GMT

Ask a question in a forum.

Dynamic Cross Sections & End Conditions

Norman Brown — Wed, 14 Dec 2022 19:09:36 GMT

Does editing a dynamic cross section remove the functionality of the end condition (i.e. the ability to seek the existing terrain)?

[ORD] Brainstorming Cross Section Ideas?

MaryB — Thu, 15 Dec 2022 17:18:58 GMT

I know that I need to adapt to the ORD way of doing everything, but I am not thrilled with Plans production.

The addition of the extra step of drawing models is an annoyance, but I can probably train everyone to use those eventually. We don't use them in our current process so that's just something new to deal with.

The fact that we cannot alter named boundaries AND the associated saved views AND attachments is going to be more of a problem. Often, we need to adjust the limits of what is shown on the sheets for one reason or another over the course of the design project. We have several staged submittals which all require plan sets, and the idea that we would have to create brand new plan sheets because we need to adjust the limits is...costly and unappealing. With sheets created the "old" way, we could retain the actual sheet, with all of the annotations intact, and simply adjust the limits (by hand) as needed. I'm not even sure we COULD adjust the limits by hand with Named Boundaries and saved views.

Is that possible? Would it be as simple as changing the reference clip boundary, or is it more complex than that?

Cross sections are another issue. It's VERY common for the initial submittal to not include drainage structures, or for those included to be nominal placeholders. This means that any cross sections cut at the early stages would be too shallow to be useful for the next submittal, without creating artificial limits (I posted about that earlier). I had thought that we could create HUGE artificial limits to make sure that we had "enough" cross section, but then I realized that the annotated grid would draw to that entire section. Which leads me to creating our own grid and annotating by hand the way we always have. We would also have to create sheets by hand because the "supersized section" wouldn't fit onto our sheets in any automated way. The benefit of the referenced saved view means that the cross section will update with any design changes, but it saves us nothing beyond that.

For anyone who is not using the default cross section sheet creation method in production, what ARE you doing?

OpenRoads - Feature Definition Not showing up in the Finished Surface

Mohammad Osman — Wed, 14 Dec 2022 22:59:15 GMT

Feature Definition Not showing up in the Finished Surface

My WorkSpace, version of OpenRoads, Client settings etc. look correct.

However, in the finished surface I only get one default layer (white color) and the model ignores all the other feature definitions I have set up in the template.

Anyone else has a similar issue and have any insight?