Hover over this grip and select ‘Solve PI’. When selecting the alignment, note the IP’s are now displayed with a grey triangular grip.Lines need to be ‘Not Constrained (Fixed)’, whilst the curves need to be ‘Constrained on Both Sides (Free)’.Select ‘Geometry editor’ from the context-sensitive ribbon.Uncheck ‘Lock all parameter constraints’.Check ‘Always perform implied tangency constraint swapping’.In the ‘Constraint Editing’ tab, swap the default settings to match the image below.In the ‘Point of Intersection’ tab, select ‘By change in alignment direction’.Select the alignment and select ‘Alignment Properties’.Import alignments into Civil 3D via Genio module (or LandXML).To setup an imported MX geometry string for InfraWorks processing, the following steps are required: Parameter Constraints should be unlocked.Lines need to ‘Not Constrained (Fixed)’, whilst the curves need to be ‘Constrained on Both Sides (Free)’.Cannot have compound or reverse curves – needs a small straight between curves to allow editing in IW360.Cannot have floating curves at the start or end of the alignment string – Inserting a short length of straight at the start/end fixes this.Horizontal alignment needs to be IP method only (no floating curves).Here are just a few rules that need to be adhered to in order to achieve the desired results: The case in point involves converting MX Genio data into InfraWorks 360, whilst still providing the ability to manipulate that geometry in InfraWorks. Image below showing Imported Road Geometry warning message
InfraWorks 360 2016 now supports editing of more complex geometry from imported Civil 3D strings, however there are still some limitations and rules that need to be adhered to in order to edit the IP geometry handles, especially when importing geometry from an external package such as MX or 12D.