Pipes

Straight runs of pipe, priced by length. Material and, where it matters, pressure rating and jointing method.

LoopbuildPipes.txt: 3 parameters, plain text. Load it once and reuse it in every project.

The shared parameters

The names matter exactly as written: these are the column headers Loopbuild looks for. They are all text fields on purpose: length and angle parameters export in whatever unit the project is set to, which changes the number we read.

Parameter	Revit categories	Type or Instance	Example	What it does
`LB_Material`Required	Pipes, Pipe Fittings, Pipe Accessories	Type	`PVC-U`	The material family: PVC-U, CPVC, ABS, PE100, PP, copper, steel or cast iron. Without it, nothing on that row can be priced.
`LB_Pressure_Rating`	Pipes, Pipe Fittings	Type	`PN16`	PN16, PN10, or a value in bar. Breaks ties between otherwise identical products.
`LB_Connection_Type`	Pipes, Pipe Fittings	Type	`solvent weld`	Solvent weld, threaded, push-fit, compression or flanged. Breaks ties between otherwise identical products.

Built-in columns to include

Nothing to create for these: Revit already has them, they simply have to be columns in the schedule you export. Revit won't let you create a shared parameter with one of these names, which is why they aren't in the file.

Column	What it does
`Family and Type`	Identifies the product. If your schedule only carries Type, that works too.
`Size`	The diameter. Millimetres, inches and DN are all read correctly.
`System Classification`	Tells us whether the run is pressure or drainage: a pressure pipe and a soil pipe of the same size are different products. System Name works as well.
`Length`	How much pipe to price. Without it, elements can only be counted.
`Count`	Only needed when your schedule lists one row per type rather than one row per element.