Point data structure improvement

This issue is about considering the usage of two distinct fields for the latitude and the longitude of the Point class. This way may be useful in particular for doing more easily geographical calculations such as: what are all points that are located below a given longitude? Other frameworks such as GeoDjango seem to store this information in dedicated fields as well. I'm adding a question mark to this issue title until we possibly confirm the decision.