The selected file should have an extension of ‘.ini’. This file allows you to set up a consistent set of coded targets for such things as scale bars, rotations, or check distances, and with one import, automatically set up projects. Note that if Units are not specified, the values in the file are assumed to be in the units of the project which it is being imported into.
The file is divided into sections, each section starting with a line like this: [Section]. The file should have at least one of these sections. Section order is not important. Blank lines are ignored. File can be commented (comment lines begin with ; (semi-colon)).
Note that the "Units" settings are indexed as follows: 0-km, 1-m, 2-cm, 3-mm, 4-mi, 5-yd, 6-ft, 7-in, 8-sf (survey feet). These indices correspond to units selection drop down controls in various PhotoModeler dialogs and tools.
Below, where ‘Point ID’ is referred to, this is the ID number of a coded target (see Coded Targets). For example, if you had two scale bars of length 2.0m and 1.0m, with coded targets 10,11 and 12,13 at each end, your file might look like this:
[Units]
Units=1
[Scale1]
PointID1=10
PointID2=11
Distance=2.0
[Scale2]
PointID1=12
PointID2=13
Distance=1.0
Another example for control points with precision (2 control points shown but typically this would be a larger number of points):
[Units]
Units=1
[Control]
Name=survey 2
Name1=hydrant top
PointID1=1
X1=10.1
Y1=15.0
Z1=29.15
PrecisionX1=0.1
PrecisionY1=0.2
PrecisionZ1=0.34
Name2=fence post
PointID2=2
X2=12.0
Y2=13.3
Z2=16.0
PrecisionX2=0.15
PrecisionY2=0.5
PrecisionZ2=0.5
This shows an example of a project's rotation defined, where the Front-Back axis (Front+Back=Horizontal Y) is defined by coded targets #1 and #2. The Left-Right axis is defined by coded targets #3 and #4 (Left+Right=Horizontal X). The Bottom-Top axis (Bottom+Top=Vertical Z) is not defined in this example as only 2 of the 3 axis need to be defined.
[Rotate]
Front=1
Back=2
Left=3
Right=4
Bottom=
Top=
This examples shows the translate (using 0,0,0 origin) defined by Point #557:
[Translate]
PointID=557
X=0
Y=0
Z=0
If a translate, scale or rotate cannot be found in the file it will look for a multi-point transform (see setting multi-point transform) defined as shown in the following example with two points defined:
[Multipoint]
PointID1=1
X1=10.1
Y1=15.0
Z1=29.15
PointID2=2
X2=12.0
Y2=13.3
Z2=16.0
...
If no translate, scale, rotate or multi-point transform can be found in the file it will look for control points (see below for control point syntax).
Additionally check distances can be created with the following fields:
[CheckDistances]
Point1ID1=10
Point2ID1=11
Distance1=2.0
Point1ID2=12
Point2ID2=13
Distance2=1.0
...
Finally check points may be created using the following fields:
[CheckPoints]
PointID1=1
X1=10.1
Y1=15.0
Z1=29.15
Name1=CheckPoint1_Name
PointID2=2
X2=12.0
Y2=13.3
Z2=16.0
Name2=CheckPoint2_Name
...
Here’s an example of a script for 2 control points with precisions:
[Control]
Name1=Name for Point 1
PointID1=1
X1=10.1
Y1=15.0
Z1=29.15
PrecisionX1=0.1
PrecisionY1=0.1
PrecisionZ1=0.1
Name2=Name for Point 2
PointID2=2
X2=12.0
Y2=13.3
Z2=16.0
PrecisionX2=0.1
PrecisionY2=0.1
PrecisionZ2=0.1
If no precision fields are defined the point is assumed to be fixed.