Closed stringfellow closed 10 years ago
From hcpick...@googlemail.com on March 15, 2014 08:13:38
The current tool is taking the value as bytes and dividing by 1,000 which provides an incorrect value for Kb (eg. 1.45 MB (1,523,441 bytes)which reports 1523 in the .xml file). In addition there is need for a discussion with the GIS group abut whther we want to be reporting the file sizes in Kb or Mb in the map catalogue.
1 megabits(informal notation: kilobyte = 1024 bytes) bytes = 131072 kilobits = 1024 kilobytes = 128 megabytes = 0.125 gigabytes = 0.0001220703125 http://www.matisse.net/bitcalc/
Status: Accepted
From matt.si...@googlemail.com on May 29, 2014 14:48:34
As long as the xml generates the file size as bytes, then the map catalog calculate and will then show in Kb, Mb, etc.
From nick...@gmail.com on June 24, 2014 10:33:03
Rather than being a SDG task, could it be solved by Bathcomms changing "KB" to "MB"? Seems like it should be an easy one to fix.
From gv1...@gmail.com on August 08, 2014 00:36:30
I've removed the divide by 1000 clause. My assumption is that the xml should now have the raw number of bytes & that is what the MA map catalogue expects? Testing required with MA website.
Status: Fixed
From ClaireBy...@gmail.com on August 16, 2014 08:54:43
Version with fix of removing the divide by 1000 clause tested on MapAction Map Catalog. XML shows raw bytes, map catalog list of maps shows correct KB or MB as appropriate. http://www.mapaction.org/map-catalogue/mapdetail/3450.html http://www.mapaction.org/map-catalogue/mapdetail/3448.html
Status: Verified
From matt.si...@googlemail.com on February 07, 2014 13:58:35
The export tool is generating the xml with the wrong file sizes they are out by 1000 - or at least when uploaded to map catalogue are then wrongly shown.
The fields in the xml are and .
Using an the xml for the south sudan map ma025, the xml had the following entries: