This is a known issue that occurred after deployment
regarding
coordinate data values with null precision parameter. This issue is now
fixed.
Good, but the "bad" value type still is used in the live database. I
will later make a list of all cases in the 2013-08-27 database dump. It
will take some hours before I am ready as I am currently inserting the
data into my local database.
Regards,
- Byrial
See
https://bugzilla.wikimedia.org/53520 for details about the issue.
A related issue is
https://bugzilla.wikimedia.org/53521 for coordinate
data values with null globe parameter.
Cheers,
Katie
On Thu, Aug 29, 2013 at 7:55 AM, Byrial Jensen <byrial(a)vip.cybercity.dk
<mailto:byrial@vip.cybercity.dk>> wrote:
Den 27-08-2013 00 <tel:27-08-2013%2000>:05, Lydia Pintscher skrev:
We've also just updated the software here. This brings a number
of bug
fixes and other improvements. The ones that are probably most
important for you:
* API: Precision and globe parameters are now required for
geocoordinate data.
It seems that you at the same time have introduced a new data value
type called "bad" for the existing geocoordinate data without
precision or globe.
It looks like this for Q30209 in the 2013-08-27 database dump with
extra whitespace inserted by me:
{
"m":
[
"value",
625,
"bad",
{
"latitude":12.186111,
"longitude":-68.989444,
"altitude":null,
"globe":null,
"precision":1.0e-5
}
],
"q":[],
"g":"q30209$A38B8E00-97D5-__412D-9903-EE5F867D08B2",
"rank":1,
"refs":[[["value",143,"__wikibase-entityid",{"entity-__type":"item","numeric-id":__10000}]]]
}
And like this in the API:
https://www.wikidata.org/w/__api.php?action=wbgetclaims&__format=json&a…
<https://www.wikidata.org/w/api.php?action=wbgetclaims&format=json&entity=Q30209&property=P625&format=xml>
Regards
- Byrial