Community
Participate
Working Groups
I created both a plate carree graph and a square lattice graph in a project. Then I created a migration graph. The migration graph generate edges for both the plate carree graph and square lattice graph. As a consequencer when I use say the plate carree and migration graph in a model I get lots of warnings that it's unable to resolve edge URI's. Here's one proposition to solve this: 1. Create a single node, say an 1x1 square lattice node 2. Create a plate carree graph (or square lattice graph) and add the ability to specify the single node as a parent. So relative physical containment edges would be created between the parent and all other nodes. Since those nodes now become admin level 1, we would add a '-' in their names. 3. Create the migration graph but specify the single parent node for location
Discussed this with Jamie. Another solution is to create a new graph generator that tessellates the parent node. However, we might still want to create a parent node for all the graphs we generate so we can generate migration edges for a single graph only.
assigned to jk
(In reply to comment #2) > assigned to jk I'm not sure whether it is reasonable. but this bug sounds somehow related to the extension of the Pajek2STEM-import that Jan is currently working on, where we want to give the user the option to include a pajek graph into an existing node of a graph within the workspace. Matthias
New idea... can we have an option on the graph generator to select multiple nodes and a button "create parent node" which would add a node along with the required containment edges? Let's discuss on a future call...
