# Swiss cadastral XML file setup

To use cadastral tolerance checking in Trimble Access, modify the sample CadastralTolerances.xml file to meet your requirements.

Download the sample CadastralTolerances.xml file from the Configuration files page of the Trimble Access Help Portal.

The sample XML file uses a combination of the Survey class and Classification to determine the tolerance value that the point must be checked against.

The Classification name defines the type of point being measured or staked: Topo, Boundary, and Control. The Survey class name defines the tolerance level required for the location of the point, for example urban versus rural.

In the case of Switzerland there are five tolerance levels for points:

- Level 1 is used in the center of larger cities.

- Level 2 is used in residential zones outside the city centers and in villages.

- Level 3 and Level 4 are used for rural areas such as agricultural land.

- Level 5 is used in the mountains.

You cannot change element names and attribute names. Note these are case sensitive.

- The element names are: CadastralTolerances, SurveyClasses, Class, Classifications, Classification, Tolerances, Codes and Code.

- The attribute names are: name, id, hzTol, vtTol, description and classification.

#### Survey class

The sample XML file defines a survey class for each level:

> <SurveyClasses>

> <Class name="TS1" id="Class1"/>

> <Class name="TS2" id="Class2"/>

> <Class name="TS3" id="Class3"/>

> <Class name="TS4" id="Class4"/>

> <Class name="TS5" id="Class5"/>

> </SurveyClasses>

To enable cadastral tolerance checking in the job, you must specify the Survey class for each job. To do this, enter the survey class name (for example, TS2) in the Notes field in the Job properties screen in Trimble Access. All points within the job will have the same class.

#### Tolerance values

The sample XML file uses classifications to define the tolerance values for each Survey class, per point type. For example, points with a boundary classification may have the following tolerance values, depending on the Survey class specified for the job:

> <Classification name="Boundary1">

> <Tolerances id="Class1" hzTol="0.035" vtTol=""/> <!-- Horizontal at least as good as Class2 -->

> <Tolerances id="Class2" hzTol="0.035" vtTol=""/>

> <Tolerances id="Class3" hzTol="0.070" vtTol=""/>

> <Tolerances id="Class4" hzTol="0.150" vtTol=""/>

> <Tolerances id="Class5" hzTol="0.350" vtTol=""/>

> </Classification>

> <Classification name="Boundary2">

> <Tolerances id="Class1" hzTol="0.200" vtTol=""/> <!-- Horizontal at least as good as Class2 -->

> <Tolerances id="Class2" hzTol="0.200" vtTol=""/>

> <Tolerances id="Class3" hzTol="0.350" vtTol=""/>

> <Tolerances id="Class4" hzTol="0.750" vtTol=""/>

> <Tolerances id="Class5" hzTol="1.000" vtTol=""/>

> </Classification>

#### Feature codes

The sample XML file also defines feature codes so that you can easily specify the classification for cadastral points when staking and measuring in the job. For example, points with a boundary classification can have any of the following feature codes:

> <Codes>

> <Code name="1" description="Boundary Point Stone" classification="Boundary1"/>

> <Code name="2" description="Boundary Point Bolt" classification="Boundary1"/>

> <Code name="3" description="Boundary Point Cross" classification="Boundary1"/>

> <Code name="4" description="Boundary Point plastic sign" classification="Boundary1"/>

> <Code name="5" description="Boundary Point uninsured" classification="Boundary2"/>

For a job where the Notes field is set to TS2, if you code a point as “1” the point will have a description of "Boundary Point Stone", and a classification of "Boundary1". This means the point must meet a horizontal tolerance of 35mm, because the CadastralTolerances.xml file specifies that "Boundary 1" points in "Class 2" jobs must have hzTol="0.035".

As noted above, you cannot rename element names and attribute names. However:

- You can rename the Class names (for example, "TS1"), Classification names (for example, "Boundary1") and Code names (for example, "1"). If you rename them, make sure you rename all instances.

- You can create additional Class names and Classification names. Simply follow the pattern in the XML file to create more.