There is the vosviewer json file format. Not the most universal, adding it here for completeness:

https://app.vosviewer.com/docs/file-types/json-file-type/

Added a format combo so that we can support multiple formats down the line. For now, I just implemented Graphology one but it shouldn't be too much work to add more.

Regarding position, do you avoid z when all z are irrelevant (which seems to be the case in most Gephi usecases). I am asking because I often encounter gexf files having z positions even if they are all zero. But it might be something of the past, I did not check recently.

Out of curiosity, how did you choose to handle:

1. conflicting attribute names and gexf viz namespace values?
2. dynamics?

Regarding position, do you avoid z when all z are irrelevant (which seems to be the case in most Gephi usecases). I am asking because I often encounter gexf files having z positions even if they are all zero. But it might be something of the past, I did not check recently.

Yes, I don't export Z if irrelevant. GEXF export in Gephi does the same. Maybe some other exporters are still exporting Z.

Out of curiosity, how did you choose to handle:

1. conflicting attribute names and gexf viz namespace values?

Good point. It could be a problem for the edge type column as in Gephi that column is called "kind". I guess we should ignore those columns and throw a warning. I'll change that.

2. dynamics?

If the "Dynamics" checkbox is checked we serialize to string the dynamic attributes. For instance "score": "\u003c[2002.0, 4]; [2004.0, 1]; [2006.0, 2]; [2011.0, 0]; [2012.0, 4]; [2014.0, 4]\u003e". If not checked, we use the current estimator to get a single value for that column. We do the same for CSV export.