mapstraction/mxn — pull request #89 by J0s3f (2011-10-29 02:16:46+00:00)
Title: Force lat/lon to be numerical

I found a problem in combination with the ovi API.
If the given lat/lon values are valid, but are strings and not floats internally, instead of automaticaly converting them like expected the OVI API throws an Exception.
With this change values are converted to numbers on creation of a new mxn.LatLonPoint

Please check if this has to be done in other places too. (I guess everywhere someone can set a position with giving numbers as input, not a LatLonPoint. Maybe moving the map or creating a point? I found nothing but didn't look very long)

Ovi also expects values to be: (see http://api.maps.ovi.com/apireference/symbols/ovi.mapsapi.geo.Coordinate.html)
Latitude in degrees. -90 <= latitude <= 90
Longitude in degrees. -180 <= longitude <= 180

I have not implemented this, because I am not sure where this normalisation should be done. When converting a Point to Ovi format, or in the mxn.core?