The vendor may be aware of the complexity

breckday27@gmai

This is not the first time we have encountered this problem - in Just Open Data we have encountered data of a similar order of magnitude and fortunately a technical solution has been provided that makes it possible to read it in an acceptable way Get data. memory requirements. The export of electronic collections actively prevents such access, the question is what kind of data processing access the vendor has planned for its users. Author: Screenshot, Ondřej Kokeš Another question immediately arises - if processing data is so difficult, is it also difficult to generate it? By perusing the textual representation of these data, we noticed that the format of the individual objects differed from the metadata.


The vendor apparently didn't use any library to serialize the entire data file (which is standard procedure Benin Mobile Number List to ensure data processing) - iteratively listing individual objects, as he himself probably felt the burden of the individual file size. (On the other hand, for small codebooks, the format is consistent throughout the file, and the vendor uses the library correctly there.)  of handling this format, but still decide to shift this burden to the open Data users. Going back to the document on the home page, it says that open data must be "ready to be machine processed as easily as possible by programmers etc.






The structure of electronic collections data directly contradicts this statement (and it is also possible that this data contradicts the legal definition of open data, which details the machine-readable formats that open data must meet). Given this situation, I'd like to know if any party (customer, vendor, or any testers) tried to use this data before publishing. Any user is bound to encounter the issues mentioned here. Meaning Data that should be legally easy to find and easy to machine process is actually an undocumented mix of intractable exports.