Welcome to yEd Q&A!
Here you can ask questions and receive answers from other members of the community and yEd developers. And you can tell us your most wanted feature requests.


Making sense of the data range selections on import

+1 vote
I have a data set where I want to relate people to one another through their interactions with departments.
The list looks like this - a 2 column display where I want to represent relationships of Person to each Department.

IT     John
IT     Eve
IT     Albert
IT     Susana
BZ     Gunter
BZ     Eve
BZ     Alice
BZ     Susana
AD     Joseph
AD     Eve
AD      Albert

I want to create an organic diagram using your software but not sure how to select the ranges for these two columns.
The data set I have is large so I would prefer the diagram to be generated from the Excel data.
I was successful in importing the data but I don't think I am making the data range selection properly because I get one box with many arrows pointing onto itself.

Do I need to transpose how the data is displayed.

A screenshot of the data range selection box would be helpful or description of which entries need to be filled in would be explicitly descriptive

I'm new to this type of import but understand data range selection for graphing.

in Help by

1 Answer

+1 vote

I've added headers to the data, you can also add additional information. I also made the names unique otherwise you get one person in multiple depts.

I also added a root to link the departments. But you can skip this if you want and the you'll have 3 unconnected diagrams.

You can get more advanced using the Property mapper

Results after mapping



by (450 points)
Referring to this example, I want to add that we generally propose to have two separated data ranges/tables for the list of nodes and the list of connections (edges). The shown table mixes two things, the specification of the connections in columns A and B and the specification of node types in columns B and C. This makes it difficult to add a type for department 'Root'. Apart from this, it is fine here, since the graph is a tree and every node appears only once in column B. However, for more general graphs, nodes would appear several times, requiring to duplicate the data of column C for every occurrence.

A more general solution would be to have a sheet for the list of nodes containing the data of columns B and C, but each node only once, and a sheet for the list of connections containing the data from A and B.

Kind regards,
Legal Disclosure | Privacy Policy