On Jun 2, 5:16 am, Premnath <[email protected]> wrote: > > We are not using this for commercial purposes. Using this just for > testing
That doesn't exempt you from the Terms of Service. > Yes, The above mentioned google API can be used for development > purposes. I don't believe that, I'm afraid, but if you're certain, then you should be able to find its documentation (I can't). > It returns the Latitude & Longitude for the cell IDs retreieved from > the Sierra Modem (As it returns a 4 byte Hexadecimal cell ID). > > Whereas the Novatel Modem returns a 2 byte Hexadecimal CELL ID. > In both the cases we convert the CELL ID to decimal & pass it to the > google API mentioned. > > Our query is whether google support the 2 byte CELL ID, as this is the > format all legacy devices (Modems) support. I don't suppose it does, since it's not returning any data. What does the documentation say? > If so what conversion need to be made at our end. I found this: http://s95417013.onlinehome.us/ktekx/gps%20cell%20tracker/atcommands/dg_at_2005_r6a.pdf which says "Four bytes are required for UMTS, whereas only two bytes are applicable for GSM, and the two first bytes are then zeros, for example, 00001A02." That indicates that a four-byte representation with leading zeros would be the same number as the two-byte value (that is, there's no conversion); but they indicate different things. Perhaps the Google database doesn't recognise two-byte GSM (2G) cell ids, only four-byte UTMS (3G) ones. This isn't really a Maps question anyway, although this group does seem to soak up queries about other APIs. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
