CLI Import Control Points - Invalid or Corrupted Input Data

Development Asset Creation
1

What’s up RC community,

I wrote a batch file to process several image sets but I want to have them all be the right scale. The scan technicians didn’t have the foresight to set up ground control points so I’m trying to do it using two tie points that are the same across the entire image set.

When I export the points I get a proper csv file which appears to be correct. However, when I re-import it using the batch script I get the message that the input data is corrupt.

Any thoughts?

control points file (path is simplified here):
“C:\Project Images\I04.jpg”, point 0, 1440.38, 959.42
“C:\Project Images\K05.jpg”, point 0, 5222.44, 1849.74
“C:\Project Images\I04.jpg”, point 1, 1044.08, 2121.74
“C:\Project Images\K05.jpg”, point 1, 5070.83, 229.18

Does the space cause a problem? I added quotes but it didn’t make a difference.

Thanks!

2

Hello,

please check that the file with control points has the right paths.
Also use param.xml file with the right settings (format of inputs found in control points’ file).

You don’t need quotes around paths and those spaces shouldn’t be a problem.

Regards.

3

Hi, 

I have a similar process setup for my instance of RC and the same issue. I’ve been running batch files for the last 5 months without any issue but since we updated to version 1.1 I keep getting the Invalid or corrupt input data error when importing the GCPs.

The CP file for the images is correctly formatted as far as I can tell and I think the issue is a missing setting in the params.xml for telling RC what the file format is but I can’t find how to write this in the params file (I didn’t write the original batch workflow my colleague did). 

Any ideas? Thanks!

4

Hello Kirsty,

with the latest version there have been some improvements made to the file importer. Due to this, there is a need to generate parametric files for import of flight log, control points and ground dcontrol points via CLI from the latest version. We have announced this in the newslettter as well as in the change log for the latest version:
https://support.capturingreality.com/hc/en-us/articles/360015460960-Version-1-1-0-12901-Blaze-Release-

Please let us know if using newly generated parametric files helped.

5

Hi,

Thanks for the quick reply, I thought this would be the case. How exactly do I generate the new parametric file? I can’t find what command to run.

Thanks.

 

6

There is no command for this, you can save it via GUI from the Import control points dialog once you choose proper parameters.

For the settings above the file looks like this:

<Configuration id=“{E80BAEB3-7A87-4889-B150-0CF6486D7089}”>
<entry key=“icpsAcc” value=“4.0”/>
<entry key=“csvCPMSep” value=“2”/>
<entry key=“icpsTmode” value=“1”/>
<entry key=“csvCPMIgn” value=“false”/>
</Configuration>

Key “csvCPMSep” defines the separator with values:

0 - comma
1 - semicolon
2 - space
3 - tab

7

Ah thank you very much! I hadn’t realised that was an export button for the parameters!

Thats all working now, thanks for the fix!