Placements

What it is

A placement is one physical device: a type put at a centre point x, y, z and turned by an azimuth, a tilt and a roll.

Typical values and how to get it

Convert the device centres from the layout drawing and take the heights from the survey or a terrain model. The id is optional and defaults to the position in the list (p1, p2 and so on); given ids are unique. The type must exist. Up to 40,000 placements. Neighbours are not declared: the engine finds, for each device, the devices that can shade it from the geometry, and the pitch is the spacing between placements across the row or the tracker axis. A tracker's neighbours are the devices of any kind and orientation whose centres lie within ten collector widths across its axis and that overlap it along its length, up to eight on each side (trackers in line along the axis are not neighbours). A rack's neighbours are every device toward its facing whose centre lies within ten collector widths of the rack, counted beyond the two half lengths along the row, and, when a device lies toward its facing, the nearest device on each side of its own row. Two placements whose footprints overlap in plan are warned, not rejected, naming the pairs: a rack's footprint is its length along the row by its width times the cosine of its tilt, a tracker's its length times the cosine of the axis tilt by its width (the footprint at 0° rotation), an east-west ridge's its length by the gap plus twice its width times the cosine of its tilt; touching edges do not count. An overlap is still run as given and shades twice. A roll on a tracker or an east-west ridge is accepted and ignored with a warning from POST /api/scene/validate.

API

scene.placements