Last modified: 2014-07-16 10:43:46 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 T66887, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 64887 - display globecoordinate also when precision does not match predefined precisions
display globecoordinate also when precision does not match predefined precisions
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
master
All All
: High critical (vote)
: ---
Assigned To: Wikidata bugs
u=dev c=frontend p=8 s=2014-05-20
:
: 62105 (view as bug list)
Depends on:
Blocks: 65535
  Show dependency tree / graph
 
Reported: 2014-05-05 12:46 UTC by Thiemo Mättig
Modified: 2014-07-16 10:43 UTC (History)
8 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thiemo Mättig 2014-05-05 12:46:38 UTC 
The value does not comply with the property's definition.
The value's data value type "ununserializable" does not match the property's data type's data value type "globecoordinate".

https://www.wikidata.org/wiki/Q16511076
https://www.wikidata.org/wiki/Property:P625
Comment 1 Thiemo Mättig 2014-05-05 12:49:31 UTC 
Additional info:

Language is set to en.

It's a JavaScript issue. PHP displays: 47°12'36.72"N, 1°33'53.208"W

Not a browser issue. Can reproduce in all browsers.
Comment 2 Thiemo Mättig 2014-05-06 14:29:30 UTC 
On other random encounter:

Der Wert entspricht nicht der Eigenschaftsdefinition.
Der Wertedatenwertetyp „ununserializable” stimmt nicht mit dem Datentypdatenwertetyp „globecoordinate” der Eigenschaft überein.

https://www.wikidata.org/wiki/Q4331849
Comment 3 Henning 2014-05-13 12:05:03 UTC 
That might be related to the detected precision being invalid / not one of the defined, fixed precisions; See isValidPrecision() and GlobeCoordinate.PRECISIONS in globeCoordinate.GlobeCoordinate.js of DataValuesJavaScript. The related question is whether to allow any kind of precision in general (which was not the original intention).
Comment 4 Lydia Pintscher 2014-05-13 12:30:57 UTC 
*** Bug 62105 has been marked as a duplicate of this bug. ***
Comment 5 Maarten Dammers 2014-05-16 15:58:04 UTC 
We talked about this on the hackathon. These fixed fields probably got in because these are used in the javascript interface to select the precision. This precision is in degrees. The data I'm importing is using dimension (in meters) converted to precision (in degrees).

Maybe the slider can be changed that it offers both in the same sequence? You have to calculate it on the fly based on the coordinates, but that shouldn't be too hard.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links