TwitterVision handles it by parsing out the l: Location String - or could just do a more natural language parsing "getting off the airplane in Heathrow" "dinner at La Traviatia's in Austin, TX"
Or even just re-aggregrating location in services that are using GeoRSS already.