Roadway Designer Profile Elevation not matching what was stored in the GPK File

RE: Roadway Designer Profile Elevation not matching what was stored in the GPK File

Josh M — Thu, 18 May 2017 15:07:47 GMT

[GPK SS2] I just experienced this same problem. I have a Roadway Designer model with a point control to control the DIT_L elevation. However this elevation doesn't match my gpk profile. I've imported it several times, rebuilt the point control, checked the xml file of imported geometry. Everything checks out, but the modeler doesn't match. My point control doesn't introduce any additional vertical offset to the gpk profile. The model profile is consistently higher than the gpk profile by 0.231'. This template has been successfully used many other times.

I am at a loss. Was a solution found to this problem back in 2013?

Re: Roadway Designer Profile Elevation not matching what was stored in the GPK File

Beebe Ray — Tue, 15 Oct 2013 19:15:07 GMT

Please send along your \rddbs folder too. It has the XIN, ALG, XML, TXT files in it.

Re: Roadway Designer Profile Elevation not matching what was stored in the GPK File

TBrugger — Tue, 15 Oct 2013 09:04:27 GMT

Chain: MED02 (Median Centerline of the Divided Interstate)

Profile: WB02NMPR (Raised Profile of the Westbound Lanes)

Median Station: 1113+75.00, LT (Median Station & Corridor Modeler Station) = 1113+49.64 (Westbound Station)

I could not post the zipped file to this page (too big?), so I'll try to put it on the "Be Communities Secure File Upload" area listed as "Brugger.zip".

I've attached a screen capture of the corridor model at Median Sta. 1113+75 & Sta. 1113+95.

Thanks,

Tim

Re: Roadway Designer Profile Elevation not matching what was stored in the GPK File

Beebe Ray — Fri, 11 Oct 2013 17:36:11 GMT

Please attach the dataset so we can review. Please pass along the name of the alignment and profile and the station point that is in question