...
Spreadsheet here shows a comparison of error (in km) between CBG with multi-lateration and CBG with tri-lateration. The technique I've followed:
- Sorting target lists in ascending order on the basis of distance between the target location and landmark location.
- Re-running the CBG code for new results.
- Populated the spreadsheet with results.
What I didn't do so far and why:
- Avoiding duplicate landmarks.
- Reason: If you look at the spreadsheet you will notice that there are duplicate entries for multi-lateration as well. You can infer this from matching Estimated Lat/Longs to Actual Lat/Longs and by observing the distance to the nearest landmark values. Also a few targets don't have more than two landmarks and
...
- in all such cases those are duplicates (in terms of Lat/Longs), so in such a case I don't have an option but to use the duplicate ones. However I do require comments on this on whether I should remove duplicates or not. The reason
...
- of my
...
- concern is that multi-lateration uses duplicate
...
- landmark values.
- Avoiding landmarks present within a target's vicinity. This requires taking note of the location.
- Reason: Closely related to the point mentioned above.
What I've tried and didn't work:
...