See https://bugzilla.wikimedia.org/show_bug.cgi?id=64820 and https://bugzilla.wikimedia.org/show_bug.cgi?id=66653
Version: unspecified
Severity: normal
Whiteboard: u=dev c=backend p=5 s=2014-09-23
Description
Description
Details
Details
- Reference
- bz70934
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T75613 [Bug] Rounding errors lead to 60 mins/secs in Geo formatters | |||
| Invalid | None | T66820 coordinate precision issue | |||
| Resolved | None | T68653 GeoCoordinateFormatter interprets precision as number of decimal places | |||
| Resolved | None | T72934 Investigate issues with globe coordinate precision |
Event Timeline
Comment Actions
result of the investigation:
The GlobeCoordinateFormatter does not pass the precision stored in the GlobeCoordinateValue to the GeoCoordinateFormatter. The GeoCoordinateFormatter interprets the precision as the number of decimal places to show (in whatever the target format is). However, GlobeCoordinateParser generates precision values as fractions of a degree.
To fix this, we have to:
- change GeoCoordinateFormatter to interpret the precision option as a fraction of a degree.
- change GlobeCoordinateFormatter to pass precision from the the GlobeCoordinateValue to the GeoCoordinateFormatter.
- write round trip tests to assert parser and formatter are compatible.