Showing posts with label gps. Show all posts
Showing posts with label gps. Show all posts

Wednesday, February 4, 2009

Synchronize your watches

Remember all those WW2 commando epics, and right before the big mission they all synchronize their watches? Well, I dare you to do that in a digital world. The machine era guys tried to make things easy to work. Watches were great. Assuming you wound it up and kept it attached to your wrist, it's a snap. Setting it is the easiest thing in the world. Find the approximate time. Pull the dial out and twist everything to the right time. Push in when Captain Mallory says "mark." The BBC World Service even still has their tones for setting your watch at the top and bottom of every hour. "Bip,bip, bip, bip, bip, bip, BEEP" and push in the knob. You are on to the second.
There is, however, no way to do this in the digital era. Just among devices I have at hand:
  • Entry into edit modes:
  • Changing the time could be forward-only, or forward and backwards; it could go on its own speed (maybe with two speeds) or each increment is a button push; the whole time could be as one, or hours and minutes could each have their own buttons; most have key repeat, but how much and how fast?
But none of them have an explicit exit mode. They time out, eventually, sometime. When does the time entered take effect? It depends. And you can't tell. So there's no good way to set time to the second. This makes me sad.

Tuesday, February 5, 2008

Computer chips will - as always - solve all of our problems

Check out this article on GPS nav units, and other electronics, being stolen from cars as they are left installed, in plain sight. How to fix this? Easy!
GPS manufacturers could solve the theft problem easily by installing computer chips to track them — but of course, that would make the devices cost more.
Um... a "computer chip"? GPS is a receiver. A chip does not have a radio. How would the data get back to... anywhere. Of course it costs more when its got a transmitter inside it. And how does it know its been stolen anyway? There is mention of registration of devices, I suppose. Do they want to allow on signed devices to work on the network (like US DBS services)? Because that's not how GPS is set up, at all. Anyway, this is not the first time I have heard such stuff, and it won't be the last.

Thursday, November 29, 2007

Am I the only one disappointed with My Location?

Oops: I had somehow gotten the impression this was an iPhone-only service (I blame the iPhone hoopla, its not /my/ fault!). Since it works across platforms and networks, that is more interesting; I guess Google didn't want to mess with getting the rights from each carrier to be a certified-for-LBS appliation. Which means I go back to being mad at every carrier for restricting this information. Oh, and My Location doesn't work (yes, I have the latest version) on my S60 phone. So, that makes me sad. Actually, to be more clear, I am bored with Google's "new" My Location product. I am disappointed with the numerous, generally fawning reactions to it. Its not that I have anything against having location in the iPhone. In fact, it tops my list of things that disappoint me about it. Instead, its because location is not just GPS. GPS phones can generally step down from telemetry sending to triangulation, then sector, then cell, to give some location sense to the application. This has been available for at least five years (I worked on UI for it at least that long ago). So, to me, non-GPS location is table stakes. This technology should have been included with iPhone from day one. Being not familiar with the AT&T network, maybe they never installed the triangulation software, but that just means the whole network is behind the curve. It may be marginally interesting how Google implemented this (is it really just for them, or did AT&T really just install it on the network and every service can, theoretically, get to it?) but I suspect not. For example, I am hearing reports of it not working sometimes. The network always knows which tower you are on, so if its not falling back, maybe I am in fact disappointed in Google. Or maybe AT&T; google is making users map the towers? I don't get it. (For the record, I was already disappointed with Nokia and/or AT&T for not including similar LBS with the GPS-less N75. No one gets a free ride from me).

Thursday, November 15, 2007

Location, proximity, mapping... for dogs

Its interesting from a conceptual point of view, though in specific its built for a very niche market. The Garmin Astro is a system: a GPS-60 with an extra antenna, and a big orange box that straps onto your dog. Its designed for hunters with dogs, i.e. bird hunting. I guess the dogs can range relatively far afield, and always have shock collars, so if they ignore that, you can just go get them with the GPS tattletale. The unit on the dog (or dogs, up to 10) is a GPS itself. Since dogs don't have thumbs, there is no readout. The giant antennas link the devices over MURS mostly around 151mhz in VHF. MURS is specifically authorized for data transmission, so that makes it easy, though sadly any retrans is specifically forbidden so I presume its pure simplex, with CTCSS or something to ID the units (and reduce audible data streams). I'd love a swarm mentality, with multiple dog-side transceivers working in tandem to relay the data, like if one is out of range of the base unit. Myself, I'd like to see something like this without the cumbersomeness, and expense, of the custom radio link. Our dog likes to run away, but practically everywhere I am has some mobile coverage, so a cheap GPS and cellular link would be enough for me. And in general this is the sort of out of box thinking that I like to see. Gives me new hope for exciting location services in mobiles, hopefully soon. Edit: And I thought I had discovered this neat product in a corner. Two hours after I post this, the wife points out an article on Garmin in the latest Newsweek that specifically mentions the Astro. At least, if the mythology is true, I like the genesis of the product; an exec around a campfire while his buddies say "couldn't your company fix this?"

Friday, October 12, 2007

Location is not (just) maps

This entry is also posted at the Little Springs company blog. If you feel compelled to comment, I'd do it over there as its quite a bit better read. A year ago (almost to the day) Barbara was mentioning that all mashups seem to be about maps, and I feel not much has changed since then. Instead of using all the neat and ever more common location technologies to simply display maps with more info and prettier visualizations, I'd like to see everyone start thinking about making the whole phone more contextually sensitive. Location services should be one of the primary methods of being aware of the user and what they are doing.

Appropriate behavior

As phones continue to grow in ubiquity and power, I believe admonitions to turn them off will fade (or simply be more and more ignored, as is already happening in many places). While I might well have scanned a poster in the lobby of a theater, and be searching about something on a pre-movie slideshow, the device should be able to use its location awareness to not loudly beep at me. Better yet would be an awareness (maybe based on linking up payment schemes) that I am in a particular movie. Push advertising — or a response to my query — about a related product should just simply wait till the film I am in is done.

Appropriate information

Here, even more than above, "appropriate" means "relevant." Information presented should always be contextually relevant, and the phone should have enough information to present this information instead of always offering the average, lowest-common-denominator guess. Lets say by combining location, bluetooth gazing and audible cues, the phone detects I am in a bookstore, not walking down the street outside anymore. Now when I take a photo of a book or poster (or if we must, the associated 2D barcode) the info presented should be where they are in the store, how many are in stock, and maybe a sales guy gets paged to come find me. A link to buy from Amazon or a map to the nearest bookstore is just going to annoy me, besides offering zero value.

More appropriate maps

Maps have an implies contextual nature simply because we all can be placed within them. Therefore interactive maps are still generally fascinating and relevant-looking. But why do I have to launch one tool to get weather, one to get traffic, another to get directions and so on? Someday every user is going to figure this out, and demand more from their phones. Why can't the device can use context information of time of day, messaging, calls in progress, location and maybe bluetooth (depending on the car) to determine that not only am I in the car, but probably heading home from work? After I drive this a few times, it can recall how I normally go home without my ever actually entering in a route. And what does it do with that? Tell me about traffic conditions, or weather. Remind me about the changing season, so I will be driving directly into the sun most of the way. If you need to monetize it more, tell me about the best prices on gas, or the sale at the grocery store I often stop at on the way home. There are dozens more ways I can think of now that location and other awareness modes can increase the ways your phone can behave more appropriately. Offer up your own ideas below. Or just go off, and build them.

Friday, October 5, 2007

One more small step for location enabling

This entry is also posted at the Little Springs company blog. If you feel compelled to comment, I'd do it over there as its quite a bit better read. The WAP Review blog sums up what I was just saying the other week about LBS.
From a purely technical perspective, finding the user is as easy as it gets in terms of LBS technology. The government's E911 mandate means the carriers already have this technology in place. However the business, privacy and political barriers to being able share this data on a mobile network is another story.
But follows up with this news that:
One of those barriers has fallen. For the first time a US carrier has given users the ability to share their location with a third party mobile web site. Granted, the third party is Microsoft, but it's a start, ...
Note that the press release refer to GPS, as always, even though its pretty obviously (and seamlessly) using lower-precision methods when the satellites aren't visible. Its not the ubiquitous context-enabling technology I'd like to see, but it certainly sounds reasonably easy and better than you'd expect. Now, if Sprint would just open up like they claim they will for the WiMax product, and offer the same service without giant strategic partnerships, we'd all be better off. But its proof the carriers can do it anytime they want to. As long I'm on location technologies again, I wanted to mention Nokia's Point and Find. There's a useful video of this that I embedded on the work blog. It involved installing players as its an FLV, and I haven't gotten around to doing that stuff on the home server yet. They talk a lot about it essentially replacing QR codes (good!) but I like the part where its a location service: point at a building, and look for ATMs near "here." While this is clearly pretty new and edgy — and building a useful searchbase outside of the bay area will take forever — its good to see the principle applied of using whatever technology and information there is on the device, and in the environment to provide a better and more relevant experience. I'd also like to see services like this (and yes, I know there are others working on it also), like Akoo, and Shazam investigate always-scanning modes. I'll bet everyone will be paranoid about the technology, but if the device could be listening or looking and decide you are in a restaurant, vs. on the busy street 10 feet away, it could react much more appropriately in many ways.

Friday, September 21, 2007

Location is not GPS

This entry is also posted at the Little Springs company blog. If you feel compelled to comment, I'd do it over there as its quite a bit better read.
Precision in LBS
I find two things about location based services these days to be annoying. First, that its new and can now be done due to the technology getting there, and second that its synonymous with GPS. Literally. “Use your GPS-enabled phone to...” This is annoying because location technology has been about for years. I (and others I work with) worked on this stuff in '99-'00. Back then, GPS was not yet in phones, but certainly was on the horizon. Instead, we used:
  • Cell
  • Sector
  • Triangulation
The phone knows some of this stuff, and the network can easily work out the rest. Precision is variable, and pretty large, but pretty reasonable when you are talking about a weather application, or pre-populating a list of cities to choose from, or pre-centering a map with a selection of local restaurants. Sector is at least 800 meter precision, and can be better. Triangulation can be under 100 meters. That's close enough to surmise you are on a particular city block. GPS can give accuracy down to a few feet, but it cannot always or reliably do this. Lots of things get in the way of getting high precision from a constellation of moving satellites when outdoors, not to mention in buildings or driving through cities with many underpasses. Suggesting additional precision, like in the photo above, can get you or your users into trouble. Other networks can present challenges, and opportunities. While WiFi (and WiMax when it comes out) will be more challenging, location can be solved and exploited in interesting ways. Bluetooth can determine relative proximity to known devices, but network awareness without pairing could be used to infer locale based on fixed systems (like mobile payment stations). So, to guide our design and development of location services, remember that:
  1. Every phone is location enabled. As long as its on a proprietary network, all this data is available for at least some location finding.
  2. All the available location technologies must be addressed when designing your application or service. Precision and accuracy must be understood by designers, and correctly exploited by the product.
  3. If you work for a carrier, exploiting the network like this should be a snap. If not, your devices or software may or may not be able to be talk to the phone enough, and you might need to negotiate with the carrier.
  4. As in many other areas of your customer's lives, privacy concerns will continue to rise. There are actual regulations around this, but you also need to look useful without acting creepy. No one wants their app to be the next “stalker-ware.”

Wednesday, June 27, 2007

Off Scale High

I've finished the overwhelming stack of magazines I was behind on, and now I'm into the overwhelming pile of books I am behind on reading. Right now, its Inviting Disaster. I love disaster books. Especially when they get into engineering or design failures. Why Buildings Fall Down is a must read if this appeals to you also.

Anyway, its covering the usual. Challenger O-rings, the Ocean Ranger capsize, etc. Well, I just finished the TMI2 part. There are plenty of lessons about procedure, training, usability, human behavior, control room design, etc. (the best of course being a light to indicate you asked a valve to close, not whether its actually closed!) But there was one I didn't recall before.

When the morning shift arrived, someone noticed the overflow cooling tank temperature was high. They see something like this:


Which means its 280°, which is not too bad. Too hot, so they start figuring out its a loss-of-coolant accident, instead of a danger of going-solid accident, but no one noticed before because its not all /that/ hot.

Well, that's because the water is not really 280°. Seems some programmer decided that all values over 280 should be discarded, so the top of the scale is...280. No standard way to know that on a digital readout, though. And certainly it was not indicated on the meter, or in any obvious place in the

Consider if that gauge was displayed like this:


Not necessarily bad that someone makes the decision no reading over 280 is important, but the classic dial gives us other information. Lots of it, really. But here, you can detect the top end, and understand that the reading is not a specific value, but an unknown above a certain value, off scale high.


This is something I particularly hate about digital display of anything. My GPS (actually, all of them) is similar. It will happily give your position down to at least 1 meter. But if you look somewhere else, it will also inform you that it only knows its position within a certain accuracy, usually between 11 and 70 feet. There's even a handy circle around your location marker if you look at the map; somewhere in this circle is where you actually are.

I have warned about this but I still think there is a fundamental design flaw in most of these sorts of display mechanisms. Excessive implied precision, and implied accuracy. Everyone I work with seems to understand its true, yet hardly anything seems to actually happen about it.

In the disaster book, Chiles talks about how the control room is oddly isolated from the boiler functions, much more so than any boiler operator from a century before would let himself be. Not just in proximity, so he can observe it, but in the type and value of his instruments. Those instruments were developed carefully, over time, to meet specific needs and avoid dangers. Since digital display is not going anywhere, I wonder when will universal digital standards start to emerge to prevent these sorts of issues?