Table of Contents
- See Also
- opals::IInfo
Aim of module
Extracts and reports header information of a vector or raster file (ODM, GDAL).
General description
opalsInfo extracts statistic information (number of points/lines/polygons, the bounding box, attribute information, spatial index details, etc..) from a data set input file. Currently, only ODMs are supported. However, the support of vector files, grid and tin file formats is planned for the future. In general, all information provided in the header of the file format is made available through a generic file statistics object.
- See Also
- Module Info
Parameter description
Remarks: mandatory
In the future ODMs, original data files, grid and tin files can be specified as input file. Currently only ODM are supported.
Remarks: output
The result of the file statistic extraction provided as generic object. Specify -outParamFile in order to store these results to an XML file.
Remarks: optional
Possible values: all .............. all possible header feature overviewZ ........ Z-Matrix overview overviewPcount ... Pcount-Matrix overview
Exports internally stored header information to files. This parameter is currently supported with ODMs file only.
Examples
The data used in the following example are located in the $OPALS_ROOT/demo/ directory. The example shows how to use opalsInfo to get an overview about data (including their attributes) within an odm.
Example 1:
As a prerequisite, the ALS point cloud data must be imported into the ODM. To achieve that, change to the demo directory and type:
Now, run the following command
which gives the following output:
After a generic information block the section about the data set attributes is listed. Figure 1 captures the corresponding section from the log file.
fullwave.fwfA special feature of the ODM is the on-the-fly collection of statistical information of all attributes. A useful feature for checking the correctness of imported or processed data. The last five attributes (Id, FileId, LayerId, WinputCode and StructNr) are "virtual" attributes. They exist for internally reason, however, are not made persistent on disk.
With the following command
local planes are estimated within each point of the data set. In the current example the computation succeeds for 67297 points (and fails in 116 cases). Running opalsInfo again
will show the newly added attributes (c.f. Figure 2). The statistics also reflect the number of successful computated plane estimations (For NormalSigma0 even less values have been set, since redundancy is required for its computation).
The last section of the module output covers information of the spatial index (c.f. Figure 3). The spatial index statistics is also reported after importing a data set, since it is crucial for processing the ODM. For further details please refer to section Analysing the index statistics of an ODM.
Example 2:
When running Module Info within a Python script, direct access to the statistics of the dataset is provided via the OPALS Python API. This is exemplified in the sample script $OPALS_ROOT/demo/infoDemo.py:
To run the script, type:
The script imports the dataset strip11.laz and queries the attribute and spatial index statistics. This is achieved by accessing the statistic parameter provided by Module Info. The script uses the access function of the complex Python type opals::DataSetStats to query (and print) the respective values.
- Date
- 23.10.2018
