gephi / gephi/gephi

Problem with export/reimport .graphm after editing with third-party tool

Open
#708 1 comment 0 reactions 0 assignees View on GitHub
Import
Dominant language
Java
Stars
6.6k
Forks
1.6k
Avg merge
9h 38m
Merged PRs (30d)
75

Description

Version from "About" Dialog:
Product Version: Gephi 0.8.1 beta 201202141941
Java: 1.7.0_09; Java HotSpot(TM) 64-Bit Server VM 23.5-b02
System: Linux version 3.6.9-2.fc17.x86_64 running on amd64; UTF-8; en_US (gephi)

Situation:
- I create and edit a graph n Gephi
- I export it as a .graphml file
- I edit the exported .graphml file using yED (http://www.yworks.com/en/products_yed_about.html)
- I reimport the .graphml file into Gephi

Problem(s):
- Nodes and edges created in yED only have the Node ID, not the label and other data
- The attributes created by the external tool are NOT in the "Data Laboratory" view
- Gephi does NOT allow me to select which field/attribute to use as label for display purposes
- At import time, Gephi tell me that a) it could not find the attribute type and class of several attributes, that b) it is assuming type String" for these attributes and c) that it is "ignoring" these attributes.
- The graph in question was edited as UNDIRECTED in both Gephi and yED, yet Gephi assumes (wrongly) for some reason that the graph is DIRECTED when reimporting it.

In this special case, yED creates attributes of its own in the .graphml file, which Gephi IS NOT importing when it should import them.

Expected Behavior:
- Gephi SHOULD import ALL attributes in a .graphml, including attributes created by any external tool
- Gephi SHOULD allow me to SELECT ANY ATTRIBUTE to display on a node as "Label", on a per graph and per node/edge basis
- If Gephi is able to infer a type for an attribute, it SHOULD import it instead of discarding it :-(
- Gephi should determine correctly if a graph/edge is directed or undirected, perhaps ask me which attribute to use when determining this.

Contributor guide

Open the contributing guide

Research direction

Reproduce the import using a Gephi-exported .graphml file edited in yED, then inspect the import warnings and the resulting Data Laboratory attributes, labels, and graph direction. Done would require resolving the reported attribute import, label selection, type inference, and directedness problems for externally edited GraphML.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
data-visualization
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.