topic Re: Cannot get rebar centerline curve using GetCenterlineCurves() in Revit API Forum

Cannot get rebar centerline curve using GetCenterlineCurves()

longt61 — Tue, 16 Jul 2019 03:33:54 GMT

I am using Revit 2019 API and I want to get the center line curve of the first and the last rebar in a rebar set. When I used the following method:

Rebar.GetCenterlineCurves(bool adjustForSelfIntersection,

bool suppressHooks,

bool suppressBendRadius,

MultiplanarOption multiplanarOption,

int barPositionIndex);

it seems that the parameter "barPositionIndex" has no effect at all. No matter what valid position index of the rebar set I inputted, the curve list I received is the curves of the first bar - the same result of :

RebarShapeDriveAccessor.ComputeDrivingCurve();

How is this possible? Is there anything I missed in the document?

P/s: I found an other way to achieve what I want by translating the first rebar curves along the direction of rebar set though.

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

jeremytammik — Mon, 22 Jul 2019 10:00:24 GMT

Take a look at the new external command CmdRebarCurves in The Building Coder samples:

https://github.com/jeremytammik/the_building_coder_samples/blob/master/BuildingCoder/BuildingCoder/CmdRebarCurves.cs

Does it achieve what you need?

If not, please supply a minimal reproducible case demonstrating your problem:

https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

Thank you!

Best regards,

Jeremy

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

jeremytammik — Wed, 24 Jul 2019 16:03:02 GMT

Congratulations on solving the problem as described in your post scriptum.

In fact, that seems to be the same approach used by CmdRebarCurves.

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

manuel.solis.lopez — Wed, 24 Jul 2019 22:25:32 GMT

Rebar.GetCenterlineCurves(… , i ) will return the curves of the Rebar at the i-th position.

However, You must distinguish among 3 different cases:

Rebar.DistributionType == DistributionType.Uniform. The rebar curves will be equal at all valid positions.
Rebar.DistributionType == DistributionType.VaryingLength. According to the rebar constraints, the rebar curves may vary along the distribution path. For example, a set of straight rebar in a triangular slab.
Rebar.IsRebarFreeForm() == true. The Rebar curves of FreeFormRebar at each position will be defined by the given constraints but also by the specific RebarUpdateServer to which the Rebar is subscribed, for instance using SurfaceDistribution or AlignedDistribution.

The Rebar curves at each i-th position could vary or not, but in case of non-FreeFormRebar (Rebar.IsRebarFreeForm() == false), you would have to apply the corresponding Transformation in order to obtain the actual location in 3D Space: Rebar.GetShapeDrivenAccessor().GetBarPositionTransform(i);

Regards.

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

longt61 — Thu, 25 Jul 2019 02:18:24 GMT

Thank you for the explanation. For more information, I was using Rebar driven by shape and uniform distribution, thus, the shape of rebar is the same for every bar.

However, I just find it strange and quite confusing that the GetCenterlineCurves() does not return the actual position of the bar but we have to explicitly transform it ourselves without mentioning it in the api documentation. It seems to me if the method return the actual position of the center line, then the barPositionIndex parameter would make more sense.

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

jeremytammik — Thu, 25 Jul 2019 06:30:53 GMT

Thank you very much, Manuel, for the helpful explanation.

I preserved this solution for posterity on the blog and added your explanation there as well:

https://thebuildingcoder.typepad.com/blog/2019/07/roadmap-rebar-curves-wizard-zip-and-more.html#4

Best regards,

Jeremy

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

Anonymous — Wed, 11 Aug 2021 11:30:39 GMT

Hello,

Could you please give an example of usage Rebar.GetShapeDrivenAccessor().GetBarPositionTransform(i) ? With GetBarPositionTransform I can get a Transform of each bar in group, but I don't know how to use it to create bars.

I would like to recreate each rebar from given rebar group as a single rebar.

As said in this topic GetCenterlineCurves with index doesn't do anything, all what I get is a list with the same shape of first rebar.

mp = MultiplanarOption.IncludeOnlyPlanarCurves rebar = UnwrapElement(IN[0]) n = rebar.NumberOfBarPositions curves = [] curvesDynamo = [] i = 0 for x in range(n): curves.append(rebar.GetCenterlineCurves(False, False, True,mp,i)) i+=1 for curve in curves: for c in curve: curvesDynamo.append(c)

Re: Cannot get rebar centerline curve using GetCenterlineCurves()

Mr.Borges — Mon, 22 Apr 2024 00:20:33 GMT

Last year I spent a lot of time trying to get a little Add-in to work. What I wanted is exactly what "Rebar Bending Detail" (introduced at 2024 Revit Release) does. I could extract the centerline curves using:

rebarCurves = (List<Curve>)rebar.GetCenterlineCurves(false, false, false, MultiplanarOption.IncludeOnlyPlanarCurves, 0);

from Rebar and project it to the view as detail lines using:

Document.ConvertModelToDetailCurves(view, modelCurves);

mentioned here and Typepad awesome examples. But I never was able to do the same with the most special type of Rebar: Spiral.

Always get a exception: "Curve must be on the plane". I've researched a lot about it until I realize that even draw a Helix using default Revit tools is hard. Seems Revit lack's a lot of usefully "basic" geometric operations. Then I gave up.

Now trying the Revit 2024 tool for Bending Details I remembered this work of mine, and I was excited to see how Revit's Team worked in Spiral Rebars bend detail. The answer proved my point: Revit lack's a lot of basic geometric operations. They simple draw a simplified detail using basic lines instead of a projection of the Spiral (as I tried before). For other Rebar seems to be a projection. Simple solution. Works. But exposes the lack of basic operations from API.