Points with string values for lat/long behave inconsistently

[waxlamp]

When supplying location data for points as strings, sometimes the geoOn() API picks them up, and sometimes it doesn't.

The trouble here is the inconsistency, since it can be considered a client error to supply non-numeric data in the first place. The solution could be either to coerce all string values to numbers, to present a type error, or to document that non-numeric location data leads to undefined behavior.