home 
wiki
wiki
Spelling: ThinkingOutsideTheBox
* Introduction [1]
* In simple terms [2]
* What is the number one feature you wish to see implemented on the
Melbourne Wireless website right now? [3]
* Do you know any accomplished application programmers with PHP )"
title=";)" />
I've had a number of suggestions made to me for improvements to the
Melbourne Wireless website over the past few months, and I've come to
the conclusion that there are too many things distracting me from
being truly productive in the short to mid term. So, I've decided to
prioritise, recruit and discuss options to ensure my own workload and
that of other Melbourne Wireless coders is not too burdensome, and to
ensure that Melbourne Wireless moves forward in a cohesive and
productive manner.
IN SIMPLE TERMS
WHAT IS THE NUMBER ONE FEATURE YOU WISH TO SEE IMPLEMENTED ON THE
MELBOURNE WIRELESS WEBSITE RIGHT NOW?
DO YOU KNOW ANY ACCOMPLISHED APPLICATION PROGRAMMERS WITH PHP )"
title=";)" /> -- TysonClugg [9]
NodeDB [10] is famous for it's elevation diagrams that come with it's
nodemaps. I believe we can go one (or two) better. How about being
able to produce "Line-Of-Sight Overlays" on our maps? I've seen a
rough version done on the San Francisco WLAN website. It will produce
an overlay on a map that shows in a different colour the areas that
have "Good" Line-Of-Sight to a given point on the map - eg the area
around a node.
If you were going to implement Elevation Diagrams you could also get
Locfinder to produce a list of nodes that have "Good" Line-Of-Sight to
any given node. This feature would be useful as for many nodes it may
show Lines-Of-Sight that the node owner may not have realised. The
Line-Of-Sight between NodeGUR [11] in Moorabbin and NodeGDW [12] in
Taylors Lakes is an example of this - it was found by a fluke of
antenna orientation. An algorithm that produces a list of all possible
Lines-Of-Sight from a node would find more of these "flukes".
As for what constitutes "Good" LoS [13] - we could create and refine
formulas that attempt to take into account buildings and trees - it's
reasonable to assume a "blanket" of houses across the landscape that
is about 7 metres tall blocks LoS [14] more or less completely.
Another "Layer" above the houses from 7 metres up to about 15 metres
above the ground level is trees, which strongly attenuate 2.4GHz
signals but do not completely block them. A LoS [15] between two nodes
could be classified as "Non-existant","Bad","Good" or "Excellent"
depending on the distance it travels through buildings, trees and open
air.
These calculations are probably pretty hard on the Locfinder server.
It would be ideal to be able to calculate the LoS [16] from every node
to every other node in the database. I don't think we'd need to do the
calculations anytime anyone requests them. They should be done
everytime a new node is created or moved - or maybe 30 minutes
afterwards in case someone starts having fun moving their node to
different coordinates all over the place. You could then build up a
"matrix" of Node-to-Node LoS [17] calculations that is stored on the
server and referenced when requested by a node. When requested by a
node, the resulting list could have various sorting options
Another more simple feature would be "Shaded contours" - that show a
colour gradation for lower or higher elevations.
I guess these ideas would take a lot of hard work in coding to
implement. But I guess you have to start with an idea first.
Please discuss... - DanFlett [18] 26/03/04
-------------------------
Links:
------
[1] http://melbournewireless.org.au/#introduction
[2] http://melbournewireless.org.au/#in_simple_terms
[3]
http://melbournewireless.org.au/#what_is_the_number_one_feature_you_wish_to_see_implemented_on_the_melbourne_wireless_website_right_now_
[4]
http://melbournewireless.org.au/#do_you_know_any_accomplished_application_programmers_with_php_sql_experiencewho_are_willing_to_donate_at_least_2_hours_per_week_of_their_time_to_melbourne_wireless_
[5]
http://melbournewireless.org.au/#which_services_should_melbourne_wireless_be_offering_via_the_website_to_help_grow_the_network_in_the_long_term_
[6] http://melbournewireless.org.au/#suggested_features
[7] http://melbournewireless.org.au/#discussion
[8] http://melbournewireless.org.au/?TysonClugg
[9] http://melbournewireless.org.au/?TysonClugg
[10] http://melbournewireless.org.au/?NodeDB
[11] http://melbournewireless.org.au/?NodeGUR
[12] http://melbournewireless.org.au/?NodeGDW
[13] http://melbournewireless.org.au/?LoS
[14] http://melbournewireless.org.au/?LoS
[15] http://melbournewireless.org.au/?LoS
[16] http://melbournewireless.org.au/?LoS
[17] http://melbournewireless.org.au/?LoS
[18] http://melbournewireless.org.au/?DanFlett
[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]