Update: Google GIS Tidbits - 6/17/11

A source close to Google says that Google has changed how it processes location requests, thus limited the sharing of locations of mobile devices. CNET reported on such sharing earlier in June. Exactly what has changed is not clear, but CNET reports it's seen a change.

Out of approximately 3,000 MAC addresses that CNET tested over the last few days, not one delivered a location from Google's database. Before June 15, Google's database showed them as appearing in locations as varied as [the U.S., China].

- CNET

Continue reading...

Update: iOS 4 Hardware Uses Apple’s Own Wifi Database for Location

GigaOm suggests that yesterday’s press release from Skyhook noting its latest four patents is intended to start a legal battle with Apple and perhaps Google.

- GigaOm

—- original post 7/30/10——

That’s what what the letter Apple sent back to Congress regarding its privacy issues states. The older Apple devices still use Google and Skyhook but from iOS 4 forward it’s all Apple data. Here’s the key bit:

To provide the high quality products and services that its customers demand, Apple must have access to comprehensive location-based information. For devices running iPhone OS versions 1.1.3 to 3.1, Apple relied on (and still relies on) databases maintained by Google and Skyhook Wireless (“Skyhook”) to provide location-based services. Beginning with the iPhone OS version 3.2 released in April 2010, Apple relies on its own databases to provide location-based services and for diagnostic purposes. These databases must be updated continuously to account for, among other things, the ever-changing physical landscape, more innovative uses of mobile technology, and the increasing number of Apple’s customers. Apple has always taken great care to protect the privacy of its customers.

Good digging there MG Siegler!
- TechCrunch

How Google Maps uses the W3C Geolocation API and Google Location Services

There’s a lot of excitement (sample) about browsers (notably Firefox and Chrome, but actually any implementation that include Google Gears) implementing the W3C Geolocation API. Why? In the past few days Google announced that Google Maps (desktop) can now take advantage of it. All good. My concern: all this discussion may be “fuzzing up” what the API does and does not do.

Continue reading...

Skyhook’s Morgan: Screen Size Challenges GPS Signals, Turn by Turn too Expensive

Rafe Needleman interviewed Skyhook’s CEO Ted Morgan on the current state of things location, including FireFox going with Google’s toolkit and not Skyhook’s (not unexpected), the price of turn by turn directions in phones (too high), the need for location brokers like Fire Eagle (too early to know) and how the larger the screen in a device, the poorer the reception.

Furthermore, the bigger the screen of a device, the worse the GPS reception gets. Morgan says, “The bigger screens drown out the GPS signals.” Although when I pressed him as to why, and he claimed to not be technical enough to fully understand it.

Wired’s Honan on LBS Overload

Recall the fim Super Size Me? The fellow ate exclusively at McDonald’s for a month to see what would happen. It was not pretty. Wired’s Matthew Honan did the same thing - but with an iPhone (and later an Android G1) and LBS services. The results? Also not pretty. His report (including fear, adult situations, awkward meals) is well worth reading, as much for the tech review as the social commentary. I’ll just share his conclusion - which was forced after a near car-accident when loading an app:

I had gained better location awareness but was losing my sense of place. Sure, with the proper social filters, location awareness needn’t be invasive or creepy. But it can be isolating. Even as we gradually digitize our environment, we should remember to look around the old-fashioned way.