OpenCV
5.0.0-pre
Open Source Computer Vision
|
Prev Tutorial: Discrete Fourier Transform
Next Tutorial: How to use the OpenCV parallel_for_ to parallelize your code
Original author | Bernát Gábor |
Compatibility | OpenCV >= 3.0 |
You'll find answers to the following questions:
Here we talk only about XML, YAML and JSON file inputs. Your output (and its respective input) file may have only one of these extensions and the structure coming from this. They are two kinds of data structures you may serialize: mappings (like the STL map and the Python dictionary) and element sequence (like the STL vector). The difference between these is that in a map every element has a unique name through what you may access it. For sequences you need to go through them to query a specific item.
XML/YAML/JSON File Open and Close. Before you write any content to such file you need to open it and at the end to close it. The XML/YAML/JSON data structure in OpenCV is cv::FileStorage . To specify that this structure to which file binds on your hard drive you can use either its constructor or the open() function of this:
Either one of this you use the second argument is a constant specifying the type of operations you'll be able to on them: WRITE, READ or APPEND. The extension specified in the file name also determinates the output format that will be used. The output may be even compressed if you specify an extension such as *.xml.gz*.
The file automatically closes when the cv::FileStorage objects is destroyed. However, you may explicitly call for this by using the release function:
Input/Output of vectors (arrays) and associative maps. As I mentioned beforehand, we can output maps and sequences (array, vector) too. Again we first print the name of the variable and then we have to specify if our output is either a sequence or map.
For sequence before the first element print the "[" character and after the last one the "]" character. With Python, call FileStorage.startWriteStruct(structure_name, struct_type)
, where struct_type
is cv2.FileNode_MAP
or cv2.FileNode_SEQ
to start writing the structure. Call FileStorage.endWriteStruct()
to finish the structure:
For maps the drill is the same however now we use the "{" and "}" delimiter characters:
To read from these we use the cv::FileNode and the cv::FileNodeIterator data structures. The [] operator of the cv::FileStorage class (or the getNode() function in Python) returns a cv::FileNode data type. If the node is sequential we can use the cv::FileNodeIterator to iterate through the items. In Python, the at() function can be used to address elements of the sequence and the size() function returns the length of the sequence:
For maps you can use the [] operator (at() function in Python) again to access the given item (or the >> operator too):
Read and write your own data structures. Suppose you have a data structure such as:
In C++, it's possible to serialize this through the OpenCV I/O XML/YAML interface (just as in case of the OpenCV data structures) by adding a read and a write function inside and outside of your class. In Python, you can get close to this by implementing a read and write function inside the class. For the inside part:
Here you can observe that in the read section we defined what happens if the user tries to read a non-existing node. In this case we just return the default initialization value, however a more verbose solution would be to return for instance a minus one value for an object ID.
Once you added these four functions use the >> operator for write and the << operator for read (or the defined input/output functions for Python):
Or to try out reading a non-existing read:
Well mostly we just print out the defined numbers. On the screen of your console you could see:
Nevertheless, it's much more interesting what you may see in the output xml file:
Or the YAML file:
You may observe a runtime instance of this on the YouTube here .