]]>
I import spreadsheet with edges (source;taget;type) and then Gephi create nodes. I want to update label to this nodes with another spreadsheet (id;label) and I want to update only nodes witch are created ealier I don't want new ones. In second spreadsheet I have more nodes than I need, so is it possibility to update only existing nodes?
Statistics:Posted by kamila88 — 14 Jan 2013 13:10
]]>
Label column is mandatory (and id), and they will always appear first. You should be able to name your short name column 'Label' and import the values there.
Eduardo
Statistics:Posted by eduramiba — 12 Nov 2012 22:35
]]>
Nodes / ID/ CityState / Latitude/ Longitude / Network / Color / Organization / Short Name
When I import this into Gephi, these are preserved, but Gephi has added columns to the left and right:
Nodes / ID / Label
wherein the content of this Nodes column is the same as the ID column.
(I used to have the column "Short Name" named "Label" but this caused the import to use the contents of those cells as the "Nodes")
Is there something I need to do to keep my own column names intact so that I can get proper results from the edges data?
thanks \
patti
Statistics:Posted by panklam — 12 Nov 2012 21:23
]]>
Eduardo
Statistics:Posted by eduramiba — 15 Dec 2011 00:45
]]>
So yes, this is a bug. The importer should consider it the same edge, since there is no direction specified and sum the weights.
Thanks for reporting this bug, I will fix it.
Eduardo
Statistics:Posted by eduramiba — 15 Dec 2011 00:20
]]>
---------------------------------------------------------
I create an excel sheet like this and import it.
source target type
a b undirected
a c undirected
a c undirected
b c undirected
c b undirected
gephi correctly identifies the a-c relationship as being entered twice, and includes it only once with a weight of 2.
I have no quarrel with this behavior.
However, gephi fails to do the same thing for the b-c relationship.
It removes c-b entirely (recognizing that the pair is repeated), BUT, it does not change the weighting of b-c to 2.
I could understand doing nothing (leaving b-c and c-b as separate relationships with weights of 1), OR
removing c-b, but weighting b-c 2.....
but I don't understand why you would remove c-b but fail to change the weight of b-c.
-------------------------------
Here is what gephi imports from the above example:
source target weight type
a b 1.0 Undirected
a c 2.0 Undirected
b c1.0 Undirected
It seems to me (naively) that if a-c is weighted as 2, then b-c should be weighted as 2, ELSE b-c and c-b should be left in place.
So, is this a bug, or is it mean to be this way?
Thanks,
Dianne
Statistics:Posted by diannepat — 15 Dec 2011 00:14
]]>
FYI: Gephi 0.8 alpha, System: Linux version 2.6.32-33-generic running on i386; UTF-8; en_US (gephi)
Statistics:Posted by rbelew — 12 Sep 2011 19:20
]]>
Also gdf is not working for me. I carefully followed the instructions, but the file wont load (Java reports errors on import).
A proper xls import of seperate edge and node tables with attributes would be very nice. Also should be considered if edge relations of source and target could be a attribute signing the direction of the relation (like the cytoscape sif or nnf format). This would reduce data amount and would give other opportunities for attributes relating to both of the edges.
Olivier
Statistics:Posted by Gogolo — 09 Nov 2010 22:09
]]>
I made the CSV import of data laboratory as a simple rows and columns importer from a spreadsheet (CSV only for now).
Since these rows are nodes or edges, the wizard offers some node or edge specific options like assigning ids or creating nodes...
For your files, you would need a id column in nodes file with the same values as the label so edges can be imported sucessfully.
Statistics:Posted by eduramiba — 08 Oct 2010 20:52
]]>
CODE:
nodedef> name VARCHAR,label VARCHAR, ppavm VARCHARRick,Rick,PersonJeff,Jeff,PersonLiam,Liam,PersonFarm,Farm,PlaceCity,City,PlaceCow,Cow,AnimalDog,Dog,AnimalCarrot,Carrot,VegetableBrocolli,Brocolli,VegetableSalt,Salt,Mineraledgedef>node1 VARCHAR,node2 VARCHAR,relationship VARCHARRick,Carrot,EatsDog,Brocolli,EatsCow,Farm,LivesBrocolli,Farm,GrowsDog,City,LivesJeff,Cow,EatsLiam,City,LivesStatistics:Posted by rotten — 08 Oct 2010 15:37
]]>
However you can create a GDF file, which is comma-separated, to have list of nodes and and a list of edges.
Statistics:Posted by admin — 08 Oct 2010 09:28
]]>
]]>
Currently we have a naming problem: CSV is a format one can use for various cases, e.g. encoding an adjacency matrix, or saving and Excel-like data sheet.
The first one is only usable to import a graph topology (nodes and edges without additional information).
The second is to generate a network from a spreadsheet.
Statistics:Posted by admin — 07 Oct 2010 21:37
]]>
The first one I found:
http://gephi.org/users/supported-graph- ... sv-format/
is really confusing because it starts off with semicolons in it, and then switches to commas.
Then I found this one:
http://wiki.gephi.org/index.php/Import_CSV_Data
which is more helpful.
I'm still a little confused. Here is what I think I understand so far:
If I want to build a graph in Gephi from a csv, I actually need two csv files if I want to have extra properties (columns) on both the nodes and edges. [ So I can use Partitioning and extra Filters. ]
One will define the nodes and the node properties. Each line in the csv represents a single node.
The other defines the edges, with each line representing an edge. Edges can have properties too.
Both imports expect the first line of the CSV to contain headers identifying the columns. If the header names match standard Gephi column names, that is where the data will be populated.
If an edge occurs more than once in the file, the weight value will not automatically be incremented unless you read it in via "File/Open" instead of 'Import CSV'. (However, you can count up the duplicate edges and add a 'Weight' column before trying to read it in.)
After selecting "New Project", and navigating to the Data Laboratory, I should import the nodes CSV first. Once the nodes table is populated, I can import the edges.
The problem is that the edge import doesn't recognize any of the nodes I already added. My theory was that this is because when I imported the nodes, they had extra columns.
If I import the edges first, and let it seed the nodes table, the same thing happens when I go to import the nodes. The nodes that get pulled in don't map to the ones already loaded.
If I remove the extra columns, they still don't seem to map to each other. So maybe the extra-column theory is wrong. Should Source and Target in the Edge CSV be Ids, Labels, or some other value in the node table?
If I load in just the edges (with properties) it will create the nodes and build me a graph with properties and I can use the Partitioning tool on the edges.
** I've also noticed that if I close the project, (don't save) and then select "New Project" and import the nodes again, the 'Id' column numbering starts up where it left off from the last project. This is a minor bug. I don't really mind exiting and restarting Gephi after each experiment with CSV imports. But I thought I should mention it.
[ I'm working in 0.7Beta. ]
Here are some a couple of sample CSV's of the sorts I've been experimenting with:
test-nodes.csv
CODE:
Label,PPAVMRick,PersonJeff,PersonLiam,PersonFarm,PlaceCity,PlaceCow,AnimalDog,AnimalCarrot,VegetableBrocolli,VegetableSalt,MineralCODE:
Source,Target,RelationshipRick,Carrot,EatsDog,Brocolli,EatsCow,Farm,LivesBrocolli,Farm,GrowsDog,City,LivesJeff,Cow,EatsLiam,City,LivesStatistics:Posted by rotten — 07 Oct 2010 20:38
]]>