<br><font size=2 face="sans-serif">Let's not forget that you need some
fixed reference points.</font>
<br><font size=2 face="sans-serif">In commercial systems, the locations
of the access points are well known.</font>
<br><font size=2 face="sans-serif">In ad-hoc networks the best that you
can hope for is a topological map.</font>
<br>
<br><font size=2 face="sans-serif">M.</font>
<br>
<br><font size=2 face="sans-serif"> </font>
<br>
<br><tt><font size=2>server-devel-bounces@lists.laptop.org wrote on 04/02/2008
01:45:14 AM:<br>
<br>
> Ryan,<br>
> <br>
> Like Ben said, inducing the physical layout of the network from metrics
<br>
> such as RSSI will give you poor results for various reasons. What
<br>
> "Space" did was to average arrival rates from direct neighbors
over a <br>
> "long" period of time (anywhere between 1 and 10 seconds)
to avoid <br>
> highly temporal effects like multipath and noise. Even so, the result
is <br>
> only a rough layout of the network. If you'd like to achieve better
<br>
> accuracy I thing you should combine other ideas like sound measurements,
<br>
> as Ben suggested.<br>
> <br>
> Pol<br>
> <br>
> <br>
<br>
</font></tt>