graphml `edgedefault` not handled to spec

Bug #676272 reported by Sébastien Heymann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gephi
Confirmed
Medium
Mathieu Bastian

Bug Description

from http://graphml.graphdrawing.org/primer/graphml-primer.html#GraphGraph

 Graphs in GraphML are mixed, in other words, they can contain directed
 and undirected edges at the same time. If no direction is specified
 when an edge is declared, the default direction is applied to the edge.
 The default direction is declared as the XML Attribute edgedefault of
 the graph element. The two possible value for this XML Attribute are
 directed and undirected. Note that the default direction must be
 specified.

However, when specifying an edgedefault Gephi complains "Edge type doesn't
fit with default".

More importantly having a graph with `edgedefault="undirected"` but all edges
but one with `directed="true"` makes the unspecified edge directed as well. My
work around for now is to just not specify edgedefault for the graph, and manually
specifying `directed` as `true` or `false` for each edge - even though this doesn't
strictly follow the GraphML spec.

Tags: import
Changed in gephi:
importance: Undecided → Medium
milestone: none → 0.7beta
tags: added: import
Changed in gephi:
status: New → Confirmed
Revision history for this message
Sébastien Heymann (sebastien.heymann) wrote :

The issue doesn't seem to come from the importer itself but the ImportContainerImpl.addEdge().

I don't understand the code from lines 208 to 224, which raise this exception when an edge has a different type than the default type.

Changed in gephi:
assignee: nobody → Mathieu Bastian (mathieu.bastian)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.