Converting Quanvert data files into UNICOM Intelligence data files
QVtoDF creates a UNICOM Intelligence data (.ddf) and .mdd file from a Quanvert .pkd file or project folder.
To use QVtoDF
1 Navigate to:
[INSTALL_FOLDER]\IBM\SPSS\DataCollection\<version>\Accessories
2 At the command prompt, type:
qvtodf "/q<qv_parameters>" "/d<dd_parameters>" [ /r<cases>] [/s<stop_cases>]
Parameters
<qv_parameters>
A list of parameters (separated by commas or semicolons) specifying how the Quanvert files are to be processed:
location = <name>
The name of the Quanvert project folder or .pkd file. You must specify this parameter.
\ in pathnames must be entered as \\. The .pkd extension is required when entering a file name.
mddfile = <filename>
The name of the .mdd file that describes the data. If you omit this parameter, a .mdd file will be created with the same name as the project folder or .pkd file.
mergex = <value>
Whether to include Ex variables in the conversion process. If <value> is non-zero, Ex variables are merged into the .ddf file; if value is zero they are not. The default is mergex=0.
<dd_parameters>
A comma-separated or semicolon-separated list of parameters specifying how the .ddf file is to be created.
<cases>
The reporting frequency: that is, display a report of processing time after every <cases> number of records have been processed. In hierarchical data, <cases> refers to the number of top-level records, not to the total number of records read so far. The default value is 0, meaning that there will be no reporting. If <cases> is greater than the number of top-level records, the report shows only the time at which QVtoDF started and the total running time.
The number of seconds reported in the intermediate reporting is the time since the last report, not the time since the start. The “Total time” at the end of the report is the total since the start, including the two initialization times. In the following example, the timing for 10000 records is the running time from 5000 to 10000 records, not 1 to 10000 records.
<stop_cases>
The number of top-level records that must be transferred before QvtoDF can stop: that is, stop once 1000 records have been processed. A value of 0 or a value that is greater than the total number of top-level records in the file means that all cases are transferred.
Examples
In the following example, qvtodf reads the Quanvert data and variable definitions from the CustSat.pkd file and creates CustSat.mdd and CustSat.ddf. Since there are no other parameters, Ex variables are ignored and there is no reporting as cases are processed.
qvtodf "/qlocation=C:\\WorkDir\\CustSat.pkd" "/dlocation=C:\\WorkDir\\CustSat\\custsat.ddf"
The following command reads Quanvert files from C:\WorkDir\Travel. The .mdd file that describes the data is travel.mdd in the same folder. The mergex=1 parameter indicates that any Ex variables in the project folder must be merged into the data as it is written out. The command has been split over two lines for ease of reading. It should be typed all on one line.
qvtodf "/qlocation=C:\\WorkDir\\Travel, mddfile=C:\\WorkDir\\Travel\\travel.mdd, mergex=1"
"/dlocation=C:\\WorkDir\\Travel\\travel.ddf,maxmult=0" /r100
The .ddf file will be created in C:\WorkDir\Traveland. It will be called travel.ddf. The maxmult=1 parameter causes all categorical data to be created as text columns in the .ddf file.The conversion process reports the status every 100 records.
The command does not define pagesize or utf16, so the default page size of 32767 is used with UTF-8 encoding.
See also
