There are some cases that a corridor can not be exported correctly or at all through RXL templates.
Correct surface
One of this is when a template has a Side Slope with a varying slope through eg a table with no surface to catch assigned.
It simply fails showing an error message. Complete failure. No file at all.
 |
| Error message |
At a similar case where a surface is not assigned but the SideSlope is constant then the exported RXL is a complete mess. Added lines from nowhere and wrong SideSlopes . A now warning at all RXL file full of serious mistakes !!!
 |
| No comment |
Another case is when a template ends either with a varied SideSlope or with an element such as Offset/Elevation that is based on a target or a
table to set its exact width, height or slope.
In this case the exported
templates do not reflect the desired form.
The exported template is broken into templates adjusted at each horizontal and vertical point of intersection of the hinge point. The slope that the original template had at this stationing is kept and applied constantly throughout until the next template.
Finally you get an RXL file full of errors, no warning at all !!!
 |
| Red for wrong daylights. Green for correct. Yellow for POIs. |
So it is impossible to export through RXL templates a variable Side Slope either in the form of a SideSlope/CutFill or just in the form of line.
Such a frustrating limitation!
The only semi workaround i have found is to do the export through "RXL road export from surface".
No comments:
Post a Comment