The property parserfunction needs to support geocoordinates.
Version: master
Severity: normal
Description
Description
Details
Details
- Reference
- bz49387
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T51387 property parser function needs to support geocoordinate datatype | |||
| Resolved | None | T52277 Implement value formatter for geo data type | |||
| Resolved | None | T51265 Spec out registry/factory for formatters and parsers in the backend | |||
| Open | None | T51385 cardinal directions in geocoordinate datatype are not localized | |||
| Resolved | None | T51386 apostrophe issue in geocoordinate UI |
Event Timeline
Comment Actions
neil wrote:
We should also allow for the coordinate reference system to be specified in all
cases.
WGS84 has become almost universal for informal geocoordinates, thanks to GPS,
and Wikipedia's mapping tools all assume WGS84 is used, so it's probably
reasonable to assume that as a default, but there's lots of high-resolution
geodata out there with different coordinate reference systems, for which
discarding the CRS will result in significant errors.
Comment Actions
Moving to high as this is getting more important with Wikivoyage getting access to this data.