1.5 KiB
1.5 KiB
| 1 | # Description of deployment area topology (rooms). |
|---|---|
| 2 | # |
| 3 | # IMPORTANT: |
| 4 | # You need a precise topology description if you use algorithms that |
| 5 | # handle it. Since none of them are currently implemented, you |
| 6 | # probably can save a lot of time by skipping the topology (and |
| 7 | # waypoints) description. |
| 8 | # However, you can describe areas if you want to know when the mobile |
| 9 | # is in a particular location. In that case be sure that the algorithm |
| 10 | # you use will be able to generate positions that match each described |
| 11 | # area (in particular, with NSS, at least one reference point should |
| 12 | # be present in each area). |
| 13 | # |
| 14 | # ALSO IMPORTANT (EVEN IF YOU DON'T DESCRIBE THE TOPOLOGY): |
| 15 | # If you use the MinMax trilateration method, or the autocalibration, |
| 16 | # you must provide area-start and area-stop options that match the |
| 17 | # deployment area. That is, the cuboid formed by these two points |
| 18 | # should include the whole deployment area. |
| 19 | # |
| 20 | # |
| 21 | # Each line defines an area, using the following format: |
| 22 | # Building name;Room name;X1;Y1;Z1;X2;Y2;Z2 |
| 23 | ### First floor ### |
| 24 | # |
| 25 | #My Building;Entrance;1.00;7.28;6.05;3.70;0.00;2.99 |
| 26 | #My Building;Corridor A;6.05;30.00;8.20;3.70;0.00;2.99 |
| 27 | ### 1st/2nd floor staircase ### |
| 28 | # |
| 29 | #My Building;Staircase;2.50;2.00;0.00;5.00;0.50;6.00 |
| 30 | #My Building;Staircase landing;1.00;3.70;1.50;2.50;0.50;6.00 |
| 31 | #My Building;Staircase;2.50;3.70;1.50;5.00;2.00;6.00 |
| 32 | ### Second floor ### |
| 33 | # |
| 34 | #My Building;My desk;1.00;7.28;6.05;3.70;3.00;6.00 |