Last modified: 2013-11-20 15:59:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T51387, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49387 - property parser function needs to support geocoordinate datatype
property parser function needs to support geocoordinate datatype
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataClient (Other open bugs)
master
All All
: High normal with 2 votes (vote)
: ---
Assigned To: Wikidata bugs
:
: 52598 (view as bug list)
Depends on: 49385 49386 50277
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-10 10:18 UTC by Lydia Pintscher
Modified: 2013-11-20 15:59 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Lydia Pintscher 2013-06-10 10:18:12 UTC
The property parserfunction needs to support geocoordinates.
Comment 1 Neil Harris 2013-06-10 21:32:56 UTC
Adding what I believe are bugs which may act as blockers for this
Comment 2 Neil Harris 2013-06-12 22:00:27 UTC
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 3 Lydia Pintscher 2013-08-16 12:52:15 UTC
Moving to high as this is getting more important with Wikivoyage getting access to this data.
Comment 4 Lydia Pintscher 2013-10-09 14:51:04 UTC
*** Bug 52598 has been marked as a duplicate of this bug. ***
Comment 5 Lydia Pintscher 2013-10-09 14:57:07 UTC
This should be fixed now. We need to test it after next week's deployment.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links