Chris, as was chatting with you on ICQ about, have seen gsmloc.org and this is a different method and goal than gsmloc.
Primarily, it would be nice to have a few points in the FCC database for a cooresponding cell-id.. The reality being (and why I posted the code for distances and bearings) is that because the FCC database holds latitude and longitude positions of the towers (even with multiple cell id's) once you have 'one' position you can begin to sift through other towers near that position you have and can start making some educated guesses about which towers in the database of 122,000 towers in the DB coorespond to which cell-id's and you then have the exact location of each tower instead of a just a fixed position in an area that gets reception from that tower. You also will know the exact distances to the other nearest towers. Through just tagging every tower within a close distance of your current location the correct tower id will rise to the top of the list as it is tagged over time and people tag it from different locations. It is really trying to refine the data that is freely available vrs creating new data. A lot of interesting statistics can be gained from this, as well as the loads of maintenance and operational data that the FCC provides about each array in the database.. You could for instance create a "actual" coverage map that shows that a cell company is inflating their claims to coverage, or for consumers to see what 'real' operational coverage is. Just a few of the ideas I have had for how to use the database. Cheers
You might be interested in at least taking a look at http://gsmloc.org/ , a project geared towards collecting cellstumbling traces and making the data available via an easy to use API. -- Christopher Schmidt Web Developer --
Joel De Gan coder, linux - php, python http://blog.peoplesdns.com _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
