<br><div class="gmail_quote">On Thu, Sep 3, 2009 at 7:18 AM, Risto H. Kurppa <span dir="ltr"><<a href="mailto:risto@kurppa.fi">risto@kurppa.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Sep 3, 2009 at 1:28 AM, Thomas<br>
<div class="im">Landspurg<<a href="mailto:t.landspurg@8motions.com">t.landspurg@8motions.com</a>> wrote:<br>
</div><div class="im">> Again , and clarifiacation:<br>
><br>
> ObenBMap have in fact less than 82963 cells (the 'trusted' cells),<br>
> the others are coming from OpenCellId! ;)<br>
<br>
</div>Yes, I knew that OBM had imported from OCI but to me the only thing<br>
that matters is how many cells a service has to be used to calculate<br>
the locations of cells, no matter where's the data from. The more data<br>
a service has, the more reliable & usable it is for a user (if there<br>
were applications capable of using any of the services to do the<br>
location). So if all three services would sync their info daily/weekly<br>
with having some of their own extra fields I'd be happy as they all<br>
would benefit from each other and they all would have the same sources<br>
to do the locationing the only difference being the algorithms. Yes of<br>
course it'd be a waste of work to maintain three databases.. but isn't<br>
that the case now anyway?<br>
<div class="im"><br>
> I would be fine also to reintegrate cells from CellsHunter into OpenCellID too<br>
<br>
</div>Is there something that stops you from doing so?<br>
<div><div></div><div class="h5"><br>
r<br><br></div></div></blockquote><div>this is how I see it, from an end-user point-of-view:<br>
<br>
openBmap has the most cells<br>
openBmap maps the most information<br>
<br>
all I want is as much cells as possible<br>
AND<br>
know that I'm logging everything that increases the quality of the data (AFAIK cellhunter logs less information)<br>
<br>
openBmap does the trick for both of them<br>
<br>
this is of course a personal opinion<br>
<br>
y <br></div></div>