Fix precision handling in GlobeCoordinateFormatter and GeoCoordinateFormatter

This patch does two things:

1) It makes GlobeCoordinbateFormatter pas the precision stored in GlobeCoordinateValues to the GeoCoordinateFormatter, so the precision used is the one stored in the value, not the one defined by the options.

2) It changes the interpretation of "precision" used by the GeoCoordinateFormatter to be fractional degrees, as generated by the GlobeCoordinateParser and thus present in the database, instead of the previous interpretation "number of decimal digits".
Fatal if not instanceof `LatLongValue`