Is there value to be added to location data?

Last night I was involved in a brief Twitter conversation with the inimitable Tony Fish, author of “My Digital Footprint” about mobile operators adding value to location data.  Personally I don’t see any (intrinsic) value in location data, that horse bolted years back (totally disrupting Alcatel et al’s monopoly at the switch level for location data).  The value in location data come from what you do with the data.  Anyway…

Tony’s thinking raised the question over placing delay on location data as a privacy guard.  His blog post on the subject is over here.  I have taken the liberty of posting my response here and on his blog.

Hey Tony

I can totally see where you are coming from but a couple of points if I may;

The notion of applying a “false” location to things is of course technically feasible but to be caught deliberately falsifying one’s location would probably do one’s reputation more harm than any good it might achieve.  Far better to merely omit the location data in the first place than try to put people of the scent as it were.

I don’t want the operator to take control of my location.  Firstly if one lives in a low signal area or indeed a highly built up and populated (read cell overloaded) area then the operator’s true understanding of one’s location is actually pretty coarse.  Sure they could get all clever and pull timing data from each cell and trilaterate back at a central point BUT as you have already stated the API is silly expensive – it’s already been disrupted by the handset itself.

Secondly, and you’ve eluded to the privacy enhancing nature of such a service, even with a user-pays service provided by an operator I would have little faith that my location data would not be aggregated and mined for their own purposes.  Far better to leave the collection, aggregation and control with the user methinks.

So how would I approach this? Well…

Certainly the handset is the right place to gather the location information. Assisted GPS (aGPS) utilising any number of beacons from cell towers to wi-fi nodes to locate the phone is easily the most reliable method of getting an accurate location.  It’s what you do with it next that counts.

If one looks at the Fire Eagle service from Yahoo! (one of the first true identity information brokerage services IMO)  it allows one to post and update an accurate location from any number of applications.  Then the user is able to decide to which location gobbling services that location is shared and more importantly to which degree of accuracy is exposed.  In fact Google Latitude does this fine:coarse sharing but to a far lesser degree.

From a single metre accurate location update to Fire Eagle it would be possible to see one location service getting your locale (as opposed to location) being at a City level when another service gets it down to the street.

That then brings me on to the notion of time-shifting or delayed location.  It would be entirely possible to build a service that sits as a layer on top of Fire Eagle (with permissions for fine grained access probably) and allows one to add delay (or even decay) to the outgoing location sharing.

However to me it would seem a feature so valuable (not in monetary terms but in usability) that it would be far better baked straight in to Fire Eagle.

I’m certain this conversation has been had before however it seems to have sunk back into the murky waters of location based services as they all vie for superiority and control of the user’s data.  To that end I tip my hat and thank you for bringing it up again.