Project overview

Short introduction

Cell information is a way of finding a position based on a mobile phones connection to a GSM antenna. This method is somewhat inaccurate with deviations of 50-400 metres. What I look into in this project is to add additional information into the equation to
better the position. Until today, using a mobile phone for
positioning, gives a position with a deviation of 50-400 meters.
This is by far too inaccurate when you compare it to a GPS which gives you 3-15 metres at the most. Using information we already know, in my case geographical road
information, it is possible to decrease the deviation.

The way I want to improve position is by adding a server with “knowledge” about a certain area. This server then correct information from the cell information service according to what the server knows.

Hence my problem definition is:

Can cell information accuracy, by the use of additional geographical information, be increased to an extent where it is usable as a GPS road tracking substitute?

Where do I stand:

So far I have stumbled Halden to Aremark and in this same process experimented with cell information and different programs available for this. As I have chosen Python as the programming language to use I have written code to test out a client and information transfer between the phone and an internet connected server. This is very straightforward when using the correct Python libraries. Furthermore I have structured a rouge final solution and decided where to go and how. For more information take a look in my living project report linked on the botoom of this post. Until Monday 20.03.06 this project had two participants. Today, the following day I am down to one. This changes my plans but it should be quite possible to give a conclusion when the project finishes.

New work plan:

By the end of week 12 finish the queues in my project report and have a meeting with Misund on server algorithm for positioning.

Week 13: Look into server algorithm and decide upon client functionality.

Week 14: Start server implementation and test it out against test data. SVG usage in the client and the algorithm for this, both server and clientside.

Week 15: Easter vacation. Work with report.

Week 16: Build client and start testing against server. Work more with the server as this is where most of the work needs to be done. Also training the server database.

Week 17: Continue server development while adding client functionality. The server need a client for decent testing. The client need graphics and added functionality for better usage. This will also demand more from the server.

Week 18: Finish the project report and evaluation.

Link to the current project report: http://www.ia-stud.hiof.no/~johnesim/rss/main.pdf