-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edge labels not retained on graphml export #1516
Comments
@burnssa Have you fixed the problem ?? The problem also appears in neo4j-community-3.2.2 with apoc-3.2.04…… |
No - using Neo4j for our project proved too challenging, so we ultimately
returned to relational databases and I abandoned exploration of the Gephi
export process.
…On Thu, Aug 31, 2017 at 7:17 PM, qingmu ***@***.***> wrote:
@burnssa <https://github.com/burnssa> Have you fixed the problem ?? The
problem also appears in neo4j-community-3.2.2 with apoc-3.2.04……
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1516 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACwP7vQcg3F4KJyS2SBeNrqmJTkn805gks5sd2kkgaJpZM4Iuljx>
.
--
Scott Burns, CFA
Twine <https://twine.com/>
Direct: (415) 498-0596
|
Fix commited, but edge label doesn't seem to be an standard attribute in graphml edges though: http://graphml.graphdrawing.org/specification/element_edge.xsd.htm |
eduramiba
added a commit
that referenced
this issue
Nov 18, 2017
Based on commit 6634da3 #1516 Edge labels not retained on graphml export #1788 GephiFormatException: Gephi failed saving the project. #1789 NullPointerException: The fileObject parameter cannot be null #1802 Exception with no-merge strategy in some cases. Incompatible edge should not be created #1810 GephiFormatException can cause ArrayIndexOutOfBoundsException: 0 #1811 NullPointerException on EdgeTypeFilter #1812 CSV files are no longer imported correctly when double quotes inside strings are delimited with backslashes #1815 Add support of Byte Order Mark to CSV parser #1840 Import of graphml still confuses d3 and label fields #1848 Import CSV error edges: force undirected makes edges disappear when merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi I've noticed that in exports from Gephi to graphml, edge labels and ids are not retained as an edge property. Thus when I try to import Gephi-exported graphml files into my Neo4j database, the proper edge relationship types are not being added.
As an example here is some sample output from a Gephi Graphml export:
Gephi export (loses relationship types on import)
Note that only source and target are retained on the edge property.
When I export to graphml from my database, using neo4j shell tools, I get edge descriptions like the following, which include id and label information not as a data key, but on the edge itself. When I import from graphml files like the following, the proper relationship types for each edge are set.
Neo4j Shell Tools Export (retains relationship types on import)
How can I export with Gephi so that I can retain all edge properties on Neo4j import?
Thanks
The text was updated successfully, but these errors were encountered: