This page can be used to manually upload your data to a WiGi interface. We are working on an API to allow programmatic data uploads. These uploads will either direct a user to the visualization in a browser window, or embed the interactive visualization in a users own web page. Until this functionality is developed, please use this page to manually upload your data. Follow the schema below and upload a CSV file, or any one of the accepted formats below. You will then be redirected to a n interactive WiGi visualization of your data.
Note 1: If you don't know CSV, don't worry! ... it's just the simple text file as shown in the example below. CSV (comma separated value) files can be exported from Microsoft Excel. To export, click File >> Save As and select .csv from the list of file types.
Note 2: You MUST name your file with the appropriate extension. The system uses the extension to recognize the format
Upload Your Data
Accepted Schema 1 .csv files (Download a sample file in csv format)
A graph of nodes and edges can be intuitively represented in N tables. Where N is the number of different node types, plus one table to associate them all together.
For example, suppose we have a 10 node graph with 2 different node types. (say, authors and publications). This can be represented in one CSV file with a delimiter between each table, as in the following example:
Notes: This simple technique allows for addition of multiple node types. Be sure to keep the ID of each node unique. All uploads in this format must be have a .csv file extension.
| @NODES | @COLOR[1.0,1.0,0] @SIZE[2.0] |
| id, | name |
| 1, | Linked |
| 2, | Sync |
| 3, | Global Illumination for Fun and Profit |
| 4, | Many Authored Paper for Profit and Fun |
| @NODES | @COLOR[1.0,0,1.0] @SIZE[1.0] |
| id, | name |
| 101, | Albert Lazlo Barabasi |
| 102, | Stephen Strogratz |
| 103, | Malcolm Gladwell |
| 104, | Joe Bloggs |
| 105, | Mary Bloggs |
| 106, | Susie Bloggs |
| @EDGES | |
| id | id |
| 1, | 101 |
| 1, | 104 |
| 2, | 102 |
| 2, | 104 |
| 3, | 101 |
| 3, | 105 |
| 3, | 104 |
| 4, | 104 |
| 104, | 103 |
| 105, | 104 |
Accepted Schema 2 .tup files
The second schema we accept is as simple as it gets: a two column data file in which each line contains a tuple representing an edge between the two node ids on that line. This format was chosen because it was used to visualize data from UCSB's CURRENT: Secure and Reliable Networking Lab. specifically, a visualization of their work on modeliing the complex social networks on Facebook.
In the example below, each line contains two 32 bit hex strings, which represent two nodes. Ids can be either HEXIDECIMAL or INT values Co-occurence of nodes on a line represents a bidirectional edge between both nodes. A space (or a comma) should be used to separate two values on each line, as in the following examples:
5e76c5fd4130f10bd0daf8b80af071fc a99f766badac95b4a5f527a60b82c112
51dcc4c01420b59c757db03fbd3d0ee7 6d16247101ffd7d54515bc757347c676
1100022bc4194d16cd784ff10528fb41 4fcbfa105d29abe5d167589ad10b256b
1100022bc4194d16cd784ff10528fb43 c7548003b219a44a0cf9a55e20abbe7e
or
1,2
2,5
3,1
Accepted Schema 3 .es3 files
The third schema we accept is currenty "under construction". THis is a specialized form of XML used by the ES3 project at UCSB's Bren School.
In this format, nodes are represented with unique identifiers (UUIDs), nestings and oter rich data is also supported. This is a highly specialized format, not for general use.
Accepted Schema 4 .dnv files (download a sample file in DNV format)
We have defined our own simple XML-like schema for graph uploads, used internally in the Four Eyes Lab at UCSB. This is a simple schema that specifies nodes and edges in xml with unique ids, and a set of semantic data that can be associated wiht each element. DNV or Dynamic Network Viewer files are currently our preferred data input type, but we are moving towards other formats.
