Combine all nodes of two content types as table rows / columns I have two content types: Ingredients (Butter, Flour, ...) and Units of mesure (Cup, Tablespoon, ...).

Ingredients have Density field (e.g Flour, 0.53g/ml) and Units of mesure a Capacity field (e.g. Cup, 250ml).

Using views, I am stuck trying to create a table similar to:

==================================================
|               | Nodes of "Units of measure"    |
|------------------------------------------------|
| Nodes of      | Math calculation based on      |
| "Ingredients" | "Desnsity" and "Capacity" values
|               |                                |
|               |                                |
==================================================


For example:

==================================================
|         | Grams | Cup  | Tablespoon | Teaspoon |
|------------------------------------------------|
| Butter  | 100   | 0.44 | 7.05       | 21.16    |
| Flour   | 100   | 0.80 | 12.80      | 38.43    |
| ...     |       |      |            |          |
|                                                |
==================================================


I don't know how to generate such a table with two content types titles as rows and columns respectively.

Any help would be appreciated. Thanks!

EDIT:


I read about similar questions that use references and relationships,
but this view should show all nodes of both content types. So, they don't need to be related.
Maybe Units of measure should be a Taxonomy instead of a content type? I am open to answers changing the scenario/context described. How would you create such a table with Drupal?
its very easy if contentypes are "entity reference" related, on "less important" contentype add an entityreference field and relate that node to "main contentype", in views add a relationship with your entityreference field, filter (not exposed) to display only "main contentype", and when adding fields to your view (now both contentypes fields are listed in drop menu field listings), specify if you use or not the relationship, for fields on "main contentype" do not use relationship, do it in all "less important contentype" fields. done.