Definitely! Ability to import/export events, as we like to document all the event points defined on the limits of a corridor, which we can also use to rebuild a corridor if needed.
Also would like to be able to define a list of station/ 0' offset points in a text file to define events to create XS named boundaries, then import. Maybe tie this to the left/right offset values for XS named boundaries, to also tie in with another idea here for adjusting XS named boundaries...
Plus be able to select an existing range of XS named boundaries and export the event list to be able to recreate XS later if needed, or to use the list as documentation.
It would be great if this functionality also provided ruled point names, so if a user exported out a point list, edited it and then reimported, it would move the event points (without recreating them). This would make this functionality much more useful and aid in users developing a design to delivery.
It would be good to also have them ruled to the imported point name, so if the user exported them, edited and then reimported they would move (as the same entity).
In many parts of design cross sections are required at specific locations along a corridor. Adding event points one at a time is cumbersome and time consuming with product lag after every data point. It would streamline the process if event points...
0
Future consideration
Add angle and station value.
Definitely! Ability to import/export events, as we like to document all the event points defined on the limits of a corridor, which we can also use to rebuild a corridor if needed.
Also would like to be able to define a list of station/ 0' offset points in a text file to define events to create XS named boundaries, then import. Maybe tie this to the left/right offset values for XS named boundaries, to also tie in with another idea here for adjusting XS named boundaries...
Plus be able to select an existing range of XS named boundaries and export the event list to be able to recreate XS later if needed, or to use the list as documentation.
It would be great if this functionality also provided ruled point names, so if a user exported out a point list, edited it and then reimported, it would move the event points (without recreating them). This would make this functionality much more useful and aid in users developing a design to delivery.
It would be good to also have them ruled to the imported point name, so if the user exported them, edited and then reimported they would move (as the same entity).