NodeTable

The following is a draft NodeTable, as described in the NodeMap page. Note that the spec is still in development, so don't spend too much effort populating the table just yet. At this point, I'm especially interested in comments regarding which data elements should be included in the table. For example, a NodeAdmin field is probably not very relevant for the purposes of this table, but anyone could find the NodeAdmin by clicking on any NodeName link. A NodeStatus field, on the other hand, could be useful to those who would like to find currently active nodes (i.e., 'SELECT node WHERE NodeType=="Active"'). The intent of this NodeTable is that anyone may import it into any database or mapping system and run queries on it, so data consistancy is a high priority. (If anyone knows of an easy online tool for maintaining a table of this sort that can enforce data consistency, let me know...otherwise, it'll have to be maintained manually.)

Also, I'd say that I'm quite hesitant to create yet another node table, as there are admittedly a couple others available, each geared to a specific purpose:

• ServicesOffered

• IpAllocation

• (I thought I'd seen a "channel allocation" table somewhere, but haven't found it since."
• [add links to other existing node tables here]

(...what we probably eventually need is a simple relational database to keep all this straight, but hey, one thing at a time, right? )

NodeTable Definition

NodeTable Experimentation Area

Here's a relatively easy project... write a couple data converters, such as one for exporting data from http://www.nodedb.com to a table here on SeattleWireless and back. It's vital that we maintain a separate copy of any data hosted on third party sites so that we still have our data in the remote chance that the service halts.