CaseySpain has developed a very cool mapping application using Macromedia's Flash. It uses a database for node data and presents node data over a raster map.
- Decide on a license to release it under (GPL?)
- Use a plain text file as well as a database for node data (the data is fairly simple and it would make it more easily portable).
- It would be nice if the nodes could be numbered or identified somehow. Right now if I try and find out where Nate's node is I have to put the mouse over every blue dot and see what it says. Maybe it could take some kind of parameter and color that dot a different color so if you clicked from a table to the map it would show up centered on that node?
- It would be cool if we could have a couple different icons to represent different types of nodes. Possible worthwhile distinctions would be:
- Non-active node (eg. i'm here, i'm interested but i haven't done anything yet)
- Hub node (i have an omni-directional hub up and running)
- Client node (i have no antenna or a directional antenna connected to a hub node)
- Point to point connection
- Connections between nodes (eg. node 16 is the hub for 12,18 and 23)
- Make the map bigger to cover outlying suburbs (Beaverton, Tigard, Vancouver etc)
No matter how we end up implementing mapping, we need to be consistent in how we collect, report, and display data. There are many different sets of data that people may be using. Common datum are NAD 27 and WGS 84. The same lat/long pair in one datum can be hundreds of meters away from the same lat/long pair in another datum. This could obviously be problematic for our application. See conversion utility for more info. --BillHolmstrom
Note: Casey's mapping sight has been down for over a year and the source was never released so this is a well and truely dead project. -- AdamShand (2003-05-30)
Well, crap. I just did a Google search to see if I could find where Casey was haning out these days and sure enough the map is back up at a new home. Sweet. -- Adam.