Jonathon Nichols's Activities

Components/points merge with undisplayed components when adding a new component

Jonathon Nichols — Tue, 14 Apr 2020 14:14:04 GMT

I'm having an issue with my templates. I have a null point to create an auxilary lane where there are the corresponding corridor references. None of the components in the Aux lane null point are used in the regular mainline and I have display rules to show one vs the other where appropriate.

My issue is this: when building out my aux lane template, I add a new component and it merges with all the undisplayed components unprompted and I am unsure why or how to remedy. The first photo is of the new Aux lane template before adding the safety edge component, and the second is after adding the safety edge component. Suddenly the same point is a part of several other components that it previously was not a part of.

Photo 1:

Photo 2:

Corridor not displaying in profile view properly

Jonathon Nichols — Thu, 19 Mar 2020 15:56:15 GMT

Hello, I'm running Power Geopak V8i SS4 and I'm having an issue.

I have an alignment file. In a separate file, I referenced in the alignment and created an offset alignment and created a corridor off the offset alignment. Now I have referenced the corridor back into the alignment file and want to display the corridor in the profile view to design my proposed profile off of.

I'm using the vertical geometry tool Quick Profile From Surface. When I display it only displays part of the corridor profile and it's quite frustrating. Yesterday, without doing anything, it displayed a seemless profile, however I got in this morning and updated some superelevation information and reprocessed the corridor and it reverted back to the same issue. I've tried different design stages, even creating a terrain and displaying that instead of the corridor and it still displays the same. Below is a photo of what it looks like. The dots are the corridor profile.

Has anyone had an issue with this that can give me any insights? Thanks!

Horizontal Feature Constraint stops part way along the feature

Jonathon Nichols — Fri, 07 Feb 2020 17:00:01 GMT

I have a null point that displays a curb in my template with a horizontal feature constraint to that searches for the selected feature definition. I created a horizontal feature from a series of regular microstation lines chained together using microstation tools and assigned the referenced feature definition to it. I then referenced this drawing into my corridor drawings and added the feature to the corridor as a reference. The problem is my template only seems to recognize the horizontal feature for a portion of it rather than the entire thing and I'm stumped to find out the problem. Any thoughts?

SSD on Vertical Curves is incorrect

Jonathon Nichols — Tue, 14 Jan 2020 20:45:28 GMT

There was an issue with older versions of Geopak where the stopping sight distance displayed for vertical curves was incorrect and there was a system configuration variable you could change to fix it. I'm still finding this issue with the current version of geopak but can't find any solutions or explanations to the issue. Does anyone have any information on this?

Thanks

COGO Database Utilities - Clean and Compress issues

Jonathon Nichols — Fri, 03 Jan 2020 14:15:39 GMT

Has anyone else ever had this issue? I use the clean and compress function in database utilities in COGO and everything seems fine but then an unknown chain shows up in COGO “uy.” When I go to delete it I’m not able to and it says it’s not found. It doesn’t seem to be causing any issues but I’m worried it could in the future.

Profile geometry not present in COGO SS10

Jonathon Nichols — Thu, 17 Oct 2019 20:04:39 GMT

I created and chained my horizontal alignment using horizontal geometry tools, created and chained a profile for that alignment using vertical geometry tools. I then change the name of my horizontal geometry and my profile no longer appears in COGO. I delete the vertical geometry and recreate it, then export to native and there it still does not appear in COGO. Why is this? Is there another step I'm missing or are you never allowed to change your horizontal geometry name after creating it the first time?

Alignment Elements change names when exported to land XML

Jonathon Nichols — Mon, 23 Sep 2019 20:44:10 GMT

The naming convention of the linear elements of my Alignment changes when I export to XML. Normally this wouldn't matter nor would I have even noticed, but I'm importing the data to an excel file for design purposes and the macros do not like the renaming of the elements. I'm exporting to LandXML 1.2 Geometry through COGO. Any insights would be appreciated.

Let me Help You

Wed, 11 Sep 2019 10:10:54 GMT

Answer a question that is verified as helpful or correct.

Auto Annotate not displaying stationing after horizontal Alignment chained

Jonathon Nichols — Tue, 10 Sep 2019 14:31:49 GMT

I'm having an issue with my alignment auto annotating in certain circumstances. If I create my horizontal geometry with simple lines and arcs or Complex by PI and then chain it, the stationing appears. However, if I create an alignment with Simple Lines and Simple Arcs from Elements, and then chain it, no stationing appears although the alignment does have stationing in the .gpk. I've tried creating the alignment other ways but I have 3 back to back curves with this alignment and this is the easiest way to create it.

My Civil Formatting Design File Settings are By Index for Equations.

My Feature Definition properties are set to True for Auto Annotate and Auto Export.

I haven't been able to find any other threads with this issue.

Ask A Question I

Tue, 10 Sep 2019 01:00:22 GMT

Ask a question in a forum.