Last modified: 2014-04-16 20:19: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 T64867, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62867 - Empty fields instead of 0 in geowiki files
Empty fields instead of 0 in geowiki files
Status: NEW
Product: Analytics
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal minor
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-20 09:11 UTC by christian
Modified: 2014-04-16 20:19 UTC (History)
4 users (show)

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


Attachments

Description christian 2014-03-20 09:11:50 UTC
Instead of listing "0" for fields without any active editor, geowiki csvs
have the field empty.

E.g.: the 2014-03-17 line of
  https://stats.wikimedia.org/geowiki-private/ca_top10.csv
has empty fields. The scheme is (actual numbers modified due to the confidentiality of the data):

  2014/03/17,,3.0,2,6,8,10,5,31,15,9,11,,,5.0,33,,,8,1.0

, while someone might expect

  2014/03/17,0,3.0,2,6,8,10,5,31,15,9,11,0,0,5.0,33,0,0,8,1.0

instead.

I've had a report that the missing 0s make it hard to have google graphs
library understand the csvs.
Comment 1 christian 2014-03-20 09:13:10 UTC
Seems geowiki always produced files that way.
Limn and LibreOffice can consume the CSVs without problems.

Leaving it to Toby to prioritize.

Until a fix is in place, one can always just add 0 to the empty
fields. E.g.:

  sed -e 's/,/,0/g' -e 's/,0\([0-9]\)/,\1/g' ~/ca_top10.csv
Comment 2 Toby Negrin 2014-03-20 23:35:52 UTC
Thanks Christian. I'm not feeling the priority at the moment.

If others feel differently, please say so here.

-Toby
Comment 3 Haitham 2014-03-20 23:41:21 UTC
I could figure out a temporary work around, so this bug is not urgent. But if it's something that is generally beneficial and doesn't require a lot of time to resolve/update the existing data, It would be great to see it resolved.
Comment 4 Bingle 2014-03-24 16:52:18 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/analytics/cards/cards/1489

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


Navigation
Links