Should we really be expecting numbers here instead of strings? I didn't alter the behavior of the existing algorithm, in case there were some side-effects in the Google Maps API or something. If that makes more sense, I can update the spec and toss in some `parseFloat()`s.