[Interop-dev] netjson for meshviewer

Moritz Warning (spam-protected)
Fri Dec 8 23:13:44 CET 2017


Hi Ufo,

thank you for your response. We use a fork of https://github.com/ffrgb/meshviewer, because some features were not accepted. But their data format is changing. :/
Using NetJson was discussed but dimissed/postponed, not sure: https://github.com/ffrgb/meshviewer/issues/87

Maybe someone has an example of how the meshviewer data look as netjson. 

On 12/08/2017 03:35 PM, Ufo wrote:
> please have a look at https://github.com/hopglass/hopglass-server/issues/61

> 
> On 07.12.2017 13:06, Moritz Warning wrote:
>> I like to evaluate netjson for a meshviewer implementation.
> which meshviewer do you mean? there are many versions (forks and branches).
> the "hopglass" is sometimes newer and also have many forks.  we like https://github.com/ffrgb/meshviewer.
> 
>> It would be helpful if somebody could tell me how the attached graph.json and nodes.json would look like in netjson.
> 
> your attached files are looking like one of the "freifunk-gluon"-standards, which still has no names. (or is it the "gluon-meshviewer-standard" or "hopglass-json-v1"?)
It's https://github.com/ffrgb/meshviewer, from a few month ago.

> 
> we tried visualization for our olsr-freifunk network with netjson. but realizing, there is no location-field (lat, lon, height)!?
Hard to believe that there is not lat/lon data in netjson.

> 
> 
> p.s. our meshnethwork with netjson (but no colors!): http://vpnf.leipzig.freifunk.net/netjson/
There is only topology information in http://vpnf.leipzig.freifunk.net/netjson/netjson.json, but no node information.

> 
> 
>>
>> thanks,
>> mwarning
>>




More information about the Interop-dev mailing list