DonPark and AdamShand are thinking about ways to create a SQL (or maybe LDAP or XML or something) schema which a community wireless group can use as a universal data collection point. We're trying to catalog everything we can think of that a community wireless group would want to keep track of (yes we know we're doomed to failure :-).

Databases

System for getting at the data

Implementation


[http://www.nodedb.com/ndbcom.dtd] NodeDB.com xml schema...


community database take two. March 2003 AdamShand, JerrittCollord, AaronBaer, (insert your name here)

I pulled this right out of postgresql since it doesnt appear to be documented anywhere else -- DonPark

User Table

userid

character varying(20)

firstname

character varying(50)

lastname

character varying(100)

password

character varying(8)

memberstatus

character varying(10)

phone1

character varying(15)

phone2

character varying(15)

url

character varying(200)

comments

character varying(2000)

certificationid

numeric

mailto

character varying(100)

MOIN_ID

character varying(24)

tempkey

character varying(16)

Node table

Column

Type

nodeid

numeric

name

character varying(1000)

providerid

numeric

carrierid

numeric

neighborhoodid

numeric

bandwidthid

numeric

statusid

numeric

certificationid

numeric

comments

character varying(2000)

longitude

character varying(200)

latitude

character varying(200)

essid

character varying(500)

channel

character varying(2)

address

character varying(200)

city

character varying(100)

state

character varying(100)

zip

character varying(20)

url1

character varying(300)

url2

character varying(300)

maintainer1

character varying(20)

maintainer2

character varying(20)

maintainer3

character varying(20)

maintainer4

character varying(20)

createdate

date

lastuseddate

date

node_geom

geometry

owner

numeric

height

numeric

pri_pub_ip_block

character varying(128)

Indexes: node_nodeid_key unique btree (nodeid) Check constraints: "$1" (srid(node_geom) = -1)


[CategoryDocumentation]