[Commotion-dev] Mesh visualization/mapping options

[Dan Staples]

Also moving this discussion to the dev list. We've been talking about 
re-writing or replacing the clunky OLSR-Viz that we currently use to 
visualize a Commotion mesh on the OpenWRT firmware. Below we mention a 
couple options:

1) Freifunks super jazzy uber-visualizer: 
http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html
2) AlterMundi's altermap: http://mapa.mesh.altermundi.net/

I personally like the decentralized, replicated nature of Altermap, 
which synchronizes data between hub nodes (using CouchDB), so that each 
has a full picture of the entire network. To build off this idea, we 
could have nodes pushing their link-state data to nearby hubs, and then 
the nodes could periodically pull summarized snapshots of the network 
map that they could present to clients. If the clients want more 
detailed info, there could be a link to a nearby hub node, which would 
present a visualization of the full data set. The hub node could be 
running a much more in-depth visualization, perhaps using something like 
Freifunk's map.

Here's a quick sketch of how this could be architected: 
http://www.asciiflow.com/#Draw6659252420885764096.


-------- Original Message --------
Subject: 	Re: [OTI-Tech] Freifunks new node map
Date: 	Wed, 17 Apr 2013 11:29:39 +0200
From: 	Dan Staples <danstaples at opentechinstitute.org>
To: 	oti-tech at lists.opentechinstitute.org



On 04/17/2013 12:54 AM, Will Hawkins wrote:
> I've seen some pretty cool network layout "stuff" that is done with d3
> and I think that it would be very worthwhile to investigate how to use
> it for the layout engine for olsr-viz!
>
> Will
>
> On 04/16/2013 06:28 PM, Georgia Bullen wrote:
>> using d3 & leaflet!
>>
>> nice.
>>
>> that's what i've been suggesting to jrb and preston as a way of
>> combining geographic info and network info.
>>
>> -GA
>>
>> On Mon, Apr 15, 2013 at 9:02 AM, Seamus Tuohy <s2e at opentechinstitute.org
>> <mailto:s2e at opentechinstitute.org>> wrote:
>>
>>      It is just so pretty... btw, #battlemesh is the official channel of
>>      battlemesh and it is starting to become active.
>>
>>      http://freifunk-gw01.hamburg.ccc.de/ffhhmap/nodes.html
>>
>>      s2e
>>      _______________________________________________
>>      OTI-Tech mailing list
>>      OTI-Tech at lists.opentechinstitute.org
>>      <mailto:OTI-Tech at lists.opentechinstitute.org>
>>      https://lists.opentechinstitute.org/mailman/listinfo/oti-tech
>>
>>
>>
>>
>> --
>> Georgia Bullen
>> Field Operations Technologist, Open Technology Institute
>> <http://oti.newamerica.net/>
>> New America Foundation
>>
>>
>> _______________________________________________
>> OTI-Tech mailing list
>> OTI-Tech at lists.opentechinstitute.org
>> https://lists.opentechinstitute.org/mailman/listinfo/oti-tech
>>
> _______________________________________________
> OTI-Tech mailing list
> OTI-Tech at lists.opentechinstitute.org
> https://lists.opentechinstitute.org/mailman/listinfo/oti-tech
I'd also like to point to AlterMundi's mapping software:
http://mapa.mesh.altermundi.net/

The front-end view isn't super sophisticated, but I like their back-end
model for collecting the nodes' data. Basically groups of nodes report
their link-state info (via JSON) to nearby nodes/servers running
CouchDB. Each of these DBs are federated and synchronize their data to a
central internet-routable web server that provides the front-end
display. It's decentralized, and could fit well with our
BigBoard/LittleBoard idea.

AlterMundi's altermap code is here:
https://colectivo.altermundi.net/projects


_______________________________________________
OTI-Tech mailing list
OTI-Tech at lists.opentechinstitute.org
https://lists.opentechinstitute.org/mailman/listinfo/oti-tech



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130417/dd2f345e/attachment.html>