Civil 3D Toolkit Feedback thread

[Paolo_Emilio_Serra1]

It converts the Polyline 3D into a Polyline 2D

[craigp]

If I use this node and create profile view, alignment will show as flat (Z as 0) or will it show as 3d polyline Z value?

[Paolo_Emilio_Serra1]

The alignment is flat

[Paolo_Emilio_Serra1]

[Eden]

Thanks Paolo for amazing work. Could you please create an examples of how these nodes can be useful?

[bertrand.savarit]

Thanks a lot @Paolo_Emilio_Serra1!!!

Would it be possible to add a node to delete one alignment element? And one to import an alignment by a landxml?

[Paolo_Emilio_Serra1]

Civil 3D Toolkit 1.1.0 is out.
This time there are a lot of nodes added but also some nodes reshuffling, which means that some of the graphs will throw an error (e.g. Unresolved Nodes or conflicts). The only thing to do is to search by name and replace the affected nodes. As the structure of the Toolkit is growing it made sense to have these adjustments now that we are 6 months in after the first release. Apologies for any inconvenience that this might cause but I’m sure you can realise that the benefits outweigh the graph review effort. Every once in a while it might happen again, I’ve created a backlog of functionalities that the community has been asking for, this should in part mitigate this kind of disruption in the future.

Requested Feedback
I’ve introduced some new approaches for inspecting API properties connected to AutoCAD and Civil 3D objects under the Object Extensions. In particular it returns a dictionary of parameter: value pairs. The dictionary keys are not sorted alphabetically for now. I would like to receive some feedback on this functionality.
Also I’ve been working on enabling the creation of Alignments and Profiles. This takes us closer to being able to create Corridors and start to seriously think about Generative Design workflows for transportation in Civil 3D.

Changes

• ProfileView and Section View are now under Civil 3D
• ProfileView.Alignment is now a property
• Profileview.Extent() is now ProfileView.Extents()
• SectionView.Extent() is now SectionView.Extents()
• AlignmentSubEntities are now under AlignmentExtensions
• ProfileEntity are now under ProfileExtensions
• StationFormatting has been removed from the MText and is now under AlignmentExtensions and groups the digits differently between Imperial and Metric systems

Known Issues
There is an “Autodesk” shelf among AutoCAD and Civil 3D that contains some COM objects enumerator that refer to Parcel User Defined Properties. They are not necessary in anyway, they don’t do anything at all. Until I find a way to hide this shelf please just disregard it. An alternative option is to implement Custom nodes via user interface (dyf) to leverage Python and COM to achieve the same results, still under evaluation but not impacting the usage of the new Parcel nodes.

[durasovartyom]

Thank you for this wonderful job!
Thank you!

[keith.sowinski]

@Paolo_Emilio_Serra1
What method are you using for your XYToLatLong and LatLongToXY conversion? I was comparing with my own nodes and the ToolKit nodes don’t appear to be as true.

Here is the approach that I took:

coordSysFactory = MgCoordinateSystemFactory()
csCatalog = coordSysFactory.GetCatalog()
csDict = csCatalog.GetCoordinateSystemDictionary()
cs = csDict.GetCoordinateSystem(csCode)
csLL = csDict.GetCoordinateSystem("LL84")
trans = coordSysFactory.GetTransform(cs, csLL)

for i, j in zip(x, y):
	toLongLat = trans.Transform(i, j)
	output.append({"Latitude": toLongLat.Y, "Longitude": toLongLat.X})

[Paolo_Emilio_Serra1]

I’m using MgCoordinateSystem.ConvertToLanLat(x, y). If the CoordinateSystem for the document is set it will select it from the dictionary otherwise it will default onto LL84.

But good catch I maybe have swapped target and source coordinate system in the XYToLatLong, thanks!

EDIT: Actually I tested it again and it seems pretty accurate the way it is in the Toolkit. Which CoordinateSystem are you using? (in my tests I used UTM84-32N)

[keith.sowinski]

Try “WISCRS2011-BrownF”. I wonder if this is a Metric to Foot conversion thing. This is a USSurveyFoot system.

[Paolo_Emilio_Serra1]

With this code I see the same differences but it is not clear why, I’ll try to reach out to product and see if they can shed a light

[bertrand.savarit]

Hello,

I was trying the new nodes you add and i think there is a problem with the two nodes AlignmentSubEntity.Before and AlignmentSubEntity.After.
I was hoping to get for AlignmentSubEntity.Before :Null;Line;Spiral;Arc;Spiral etc…
See my screenshot below :

[Paolo_Emilio_Serra1]

@bertrand.savarit thanks for the feedback could you please share the DWG so I can replicate the same?

[craigp]

Thanks @Paolo_Emilio_Serra1 for amazing work. Do you have examples of these newly created graphs? How it can be useful to us.

[bertrand.savarit]

Of course, you’ll find attached one dwg and .dyn.

AlignmentSubEntity.After.dwg (906.5 KB) AlignmentSubEntity.After.dyn (12.1 KB)

[Paolo_Emilio_Serra1]

@bertrand.savarit thank you so much, I’ve fixed the issue in 1.1.1

[Paolo_Emilio_Serra1]

@craigp I don’t have a lot of bandwidth right now for creating the samples, maybe someone else feels confident enough to get these samples started?

[marolek]

Hi everybody,
is it possible to get a perpendicular distance from one alignment to another (like target distance in corridor) using Civil3d Toolkit?

[bertrand.savarit]

You can try this method (not using any node of the civil 3D Toolkit)?