no, the problems is that in one utility (Yahoo! Weather) the location is defined by an ASCII string, and on the other (Forecast.io), by a tuple of coordinates; that's why I'm telling that the API definition is incomplete, because this is no obvious; we must say what utility expects.