Arrays are returned when x/y/z translation/scaling/rotation clash in generated graphs

[bherr2]

Routes like https://apps.humanatlas.io/api/v1/ds-graph and https://apps.humanatlas.io/api/#get-/v1/extraction-site can have arrays instead of numbers if the placement (this can happen else where) occurs multiple times, but has different values. Some of this is different rui locations have the same ID (ie clashes) and some are from different rounding methods (which should be mostly ironed out at this point).

Investigate the issue and find a solution. This might be just choosing the first element to make sure the data is valid on output, but could introduce issues in itself (if the entities are actually different). Or it might mean tracking down the original data and fixing the issue.