Method and devices for utilizing data in data formats that cannot be directly processed

p0001The invention relates to a geodetic system according to claim 20, a computer program product according to claim 10, a computer data product according to claim 10, a computer program product according to claim 10, A signal according to claim 11 and a reference or data directory according to claims 12 and 13, respectively.

p0002In many geodetic applications and systems, the need for frequent or continuous transfer of data between different devices exists. In this case, data are transmitted with temporal or spatial reference, which may include parameters of the measurement, measured values ​​or general communication, such as messages via errors. Examples of such data are the current time, the location of a measuring device together with possible reference points, as well as direction, distance and angle to measurement points. The transmission can take place in this case by a multiplicity of suitable wire-bound or wireless communication means, for example via a direct cable connection as well as directional or non-directional data transmission.

p0003Without limiting the general applicability of the method according to the invention and the devices according to the invention, the application for a differential global navigation satellite system (D-GNSS), such as the Global Positioning System (GPS), is intended as an illustrative example. The data types and data formats shown purely by way of example also relate to this, which however, with a similar design, can be used in many further applications.

p0004In the case of the differential GNSS, the position determination of a mobile unit, the so-called rover, takes place by data reception and data measurement to satellites, as well as the data reception of data measurements from at least one reference station. Since the position of the reference station is known and also receives the identical signals from the satellites, this inaccuracies and errors can be eliminated by this differential correction method. This method allows a higher accuracy than is possible with a rover without a reference station. Such a station continuously transmits data from the received satellite signals to the rover. Depending on the embodiment, this can be raw data or already processed data.

p0005In practice, however, reference stations are usually not installed for each measuring operation, but are supported on a whole network of permanently installed reference stations, which can also be used simultaneously by different users. In addition to satellite-related data and time, these stations now also transmit specific information about themselves, such as their own reference station no. In addition, it is necessary to transmit technical data, such as antenna parameters, or correction parameters. Examples of such a correction parameter are atmospheric or geometric corrections which have been determined, for example, in a network of permanent reference stations and an associated network evaluation software and can now be used to correct rover measurements as a function of the distance from the participating reference stations.

p0006Since the use of the data of a reference station for different rovers is to be possible, the transmission of the signals is omnidirectional. However, this results in the requirement that the communication must also be possible with the various systems in the transmission range of a reference station so that a form of standardization of transmitted data formats is necessary.

p0007A standard for vendor-independent data formats used for such data transmission is set by the Radio Technical Commission for Maritime Services (RTCM) in Alexandria, Virginia, USA. The term data format describes a closed information unit for transmission between geodetic devices. The exchange of information takes place by means of identical or different data formats at identical or different data frequencies. The term data field describes a completed, defined data content with a specified value range. For example, data formats are composed of an initial identifier, different data fields, and a final identifier with a possible checksum for data checking on reception. The term data type describes the possible expression, such as length, unsigned or signed, of an information unit. Data types are used to describe data fields.

p0008The previously valid standard RTCM V2.x consists of one or more headers with data fields as basic information, to which optional additions can be attached. The occurrence of such additions in a data format is indicated by so-called flags as indicators. This means that each transmitted message has, according to its input part, a sequence which indicates to the receiver whether or not further additions follow. From this information, the receiver knows how to interpret and process the data stream.

p0009However, this prior art solution has the drawbacks that the number of possible permutations in the number of flags used is relatively low, but not every manufacturer has taken into account all possible permutations and the processing of the associated data in his devices.

p0010One solution known in the art for the restricted number of flags is to define data formats, eg as selected permutations, and to provide progressive coding. From this number transmitted at the beginning of the message, a device can derive the data format as a sequence of different data fields from data types and thus evaluate the data fields.

p0011Although the address space and therefore the number of usable message variations can be significantly extended compared to the flag alternative, there is the problem that all the variants to be transmitted must be pre-stored in the firmware of the devices. If a device receives a message or data format with unknown coding, direct processing can no longer take place, although in the sequence of data fields, data fields with usable and processable data which can be evaluated in principle are also contained in the sequence of data fields.

p0012Such a solution will inevitably require the creation of a new firmware variant by all manufacturers if the available messages are changed by adding new data formats or changing existing data formats. In addition, this new variant has to be recorded on all devices after it has been created, which requires a high coordination effort.

p0013This problem, illustrated in the example of the differential GNSS, can also occur in the communication between other geodetic devices. For example, a theodolite can exchange data with a further theodolite and / or intelligent reflector systems, whereby a similar problem occurs, since devices of different manufacturers and different developmental levels must also communicate and interact.

p0014SUMMARY OF THE INVENTION The object of the present invention is to provide a method and / or associated devices and data-technical elements which allow a continuous change of a set of data formats.

p0015In particular, it should be ensured that a permanent adaptation of the firmware present on the geodetic devices is omitted due to a revision or redesign of the standard.

p0016A further object is to effect an automated processing of the processability of non-directly processable data formats.

p0017A further object is to make processing of older data formats possible.

p0018A further object is to enable an expansion of the usable data fields or data formats by introducing new data types.

p0019These objects are achieved according to the invention by the characterizing features of claims 1, 14 and 16 as well as by the characterizing features of the dependent claims.

p0020The present invention relates to a method, geodetic devices, a geodetic system, a computer program product, a computer data signal and a reference or data directory.

p0021The messages to be transmitted according to the invention are transmitted in a data format consisting of a sequence of at least two data fields. A data field has a basically arbitrary length so that the data fields can have a different length within a data format. The information in each data field is stored in a defined data type. Data fields can be repeated within a data format, for example, when the same data are transmitted in succession, or the same information is stored in a plurality of data fields of different data types, for example in transmitting the time in different display forms. Also, multiple indicators may be included in a message, such as flags or parity bits. These are also subsumed under the term "data field".

p0022The data format of each message can be unambiguously determined by means of a coding which preferably takes place numerically or alphanumerically. In each geodetic device according to the invention designed to receive the messages there are means for processing usable data which can evaluate a set of data fields known from this device. In addition, the device has the knowledge of a certain number of data formats, ie both the data fields included and the sequence thereof are known to the device and can be based on the processing, for example, on the basis of the coding of a message. These data formats thus represent a set of directly processable data formats which have exclusively evaluable data fields. The term "evaluable" here refers to the fact that the device or the firmware located thereon can be used to recognize and evaluate the data stored in this data field. This does not require that the respective data is subsequently processed for a particular purpose. The term "evaluable" thus refers to the potential usability of the data in the respective data field.

p0023In this context, the term "geodetic device" is generally intended to be understood to mean devices which serve or are arranged for measuring or checking data with spatial reference. In particular, this relates to the measurement of location, distance and / or direction or angles to one or more reference or measurement points. This applies not only to terrestrial systems but also to those which use components for satellite-based location determination (eg GPS or GLONASS). In particular, such geodetic devices are, for example, stationary, mobile reference stations or moving stations, so-called rovers, but also smaller, mobile devices such as theodolites and so-called total stations as tachymeters with electronic angle measurement and electrooptical distance meters. Likewise, the invention is suitable for use in specialized devices with similar functionality, for example, in military gauges or in industrial construction or process monitoring; These systems are also covered by the term "geodetic device".

p0024If the existing data formats are supplemented by the addition of new data formats, these new data formats can not be processed directly since the device is not aware of the structure. An adaptation and supplementation of data fields may, for example, be necessary for an increased resolution or a modified range of values. Since an optimal data throughput and an optimal communication must also be taken into account, a replacement of the existing data format with new defined data formats is advantageous. The new data formats can consist of a permutation of the data fields of a known data format or else a new sequence of data fields. If necessary, these data formats also contain new types of data fields which can neither be detected nor used by the device. These data fields can thus not be evaluated.

p0025This means that the new, non-directly processable data formats consist of a sequence of evaluable and / or non-evaluable data fields.

p0026In order to nevertheless allow the use of the non-directly processable data formats, the device must be able to identify or localize the evaluable data fields. According to the invention, in the case of bi-directional communication, the transmission of a reference directory preferably takes place in connection with the establishment of a communication link between the participating devices, while for unidirectional connections parts of the reference directory can also be distributed over a certain period of time and with repetitions by means of data formats to be defined. Further occasions for the automated or manually triggered transmission of the reference directory can, however, also be external processes, such as the signaling of a receiving device which can not process a message, or internal processes in the sending device, such as the expiration of a counter or reaching it A time mark, whereby in particular also a periodical transmission of the directory can be effected.

p0027The reference directory contains the order and the types of data formats used for each encoded data format. Thus, one or more evaluable data fields can also be used within a completely new, non-directly processable data format. Thus, an indirect processability of the new data formats is made possible.

p0028Alternatively, a different notation can be used instead of directly specifying the sequence of data fields. For example, new, non-directly processable data formats can also be derived from the known data formats by specifying the changes. Particularly in the case of new data formats, which can only be represented as juxtaposition of shorter, known data formats, this notation is suitable since the reference list can be kept smaller. The specification of the change is also advantageous if a large stock of comparatively short data formats is already available, which can describe quasi-modularly more complex data formats. To this extent, these short data formats represent meta data fields for superordinate, longer data formats.

p0029If the device or the firmware located thereon is designed in such a way that it can also use new types of data fields or new data types on the basis of at least one transmitted data directory, it is also possible to make full use of data formats with new data fields. This data directory can basically be designed and handled analogously to the reference directory and can be used to define new data fields or data types. If necessary, the definition of data fields and data types can also be made in parallel in a common directory. New data fields can be introduced as extended descriptions of old data fields. This allows, for example, a range expansion or an adaptation of the information resolution.

p0030The sequence of the data fields, which can now be known and evaluable or new and can not be evaluated, follows from the transferred reference directory. While the evaluable data fields can already be localized and evaluated on the basis of this sequence information, their definition can be taken from the data directory for the non-evaluable data fields, so that the data fields which have not yet been evaluable can also be used. In principle, it is possible to combine both types of directories in one directory, as well as to allow the introduction of further levels of the data description and definition, and to store them in further directories to be transmitted. According to the invention, the reference or data directory can be transmitted both as a file within an operation or else in a piecewise distributed manner over a period or several operations. The use is then carried out on the basis of the piecewise transferred shares or only after the entire directory has been completely received. In particular, in the case of unidirectional communication, a periodic transmission of short parts of the reference and / or data directory can also take place, this process being able to be repeated continuously, possibly with interruptions, after the complete transmission of a directory. The transmission of the directory thus gains a quasi-continuous character. In this way, it is possible for a receiving device to remove all parts of the respective directory from the transmitted messages after a certain period of time and to reassemble it into the complete directory.

p0031The method according to the invention and associated devices or directories are described in more detail below purely by way of example with reference to exemplary embodiments shown schematically in the drawing. Show in detail<dl id="dl0001"><dt>FIG</dt><dd>A realization form of data formats with flags according to the prior art; </dd><dt>FIG</dt><dd>A further embodiment of data formats with a numerical coding according to the prior art;</dd><dt>FIG</dt><dd>Two sets of data formats, one of directly processable data formats, the other of non-directly processable data formats;</dd><dt>FIG</dt><dd>A first possibility for using evaluable data fields in non-directly processable data formats;</dd><dt>FIG</dt><dd>A second possibility for using evaluable data fields in non-directly processable data formats;</dd><dt>Fig</dt><dd>A third possibility for using evaluable data fields in non-directly processable data formats;</dd><dt>FIG</dt><dd>4 is a schematic representation of a reference list according to the invention with direct indication of the sequence of data fields;</dd><dt>FIG</dt><dd>Two further groups of data formats, one of directly processable data formats, the other of non-directly processable data formats;</dd><dt>FIG</dt><dd>7 is a schematic representation of a reference list according to the invention with an indirect indication of the sequence of data fields; </dd><dt>FIG</dt><dd>A schematic representation of the handling of non-evaluable data fields with and without the use of a data directory;</dd><dt>FIG</dt><dd>4 shows a schematic representation of a data directory according to the invention for the definition of data types;</dd><dt>FIG</dt><dd>4 is a schematic representation of a data directory according to the invention for defining data fields;</dd><dt>FIG</dt><dd>A schematic representation of the relationships of data types, data fields and data formats;</dd><dt>Fix.14</dt><dd>4 shows a schematic representation of a data directory according to the invention for the definition of non-evaluable data fields, wherein useable data fields are used;</dd><dt>FIG</dt><dd>5 shows a schematic representation of the transmission of the reference list by a method according to the invention;</dd><dt>FIG</dt><dd>A schematic representation of the reception and the evaluation of data transmitted in non-directly processable data formats by means of a method according to the invention; and</dd><dt>FIG</dt><dd>4 shows a schematic representation of a theodolite with further devices than the system according to the invention.</dd></dl> In <figref idrefs="f0001">FIG</figref> The structure of a geodetic data format of the prior art with flags is schematically illustrated. An example of such a realization form is the RTCM standard V2.3. Following a starting part A which is identical for all data formats, a first flag bit 1, a second flag bit 2 and a third flag bit 3 are followed by setting a Of the flag bits, ie by assigning the binary value "one" for the respective bit, a corresponding appended supplementary part is signaled to the evaluating program. In the top example of the code format, all three flag bits 1,2 and 3 are set to "zero" so that a program processes the beginning of a message in this format and then no longer reads out any further data from this message. The underlying data format has a first flag bit 1 set to "one", which indicates that a supplementary part B1 follows. If the first flag bit 1 and the second flag bit 2 are set to "one", as shown in the middle example, two supplementary parts B1 and B2 follow, the part B1 always following B2. The sequence of the supplementary parts is also preserved when a supplementary part is omitted, as shown in the two most minute examples. The use of the flag bits thus can be used to derive a number of different data formats from in each case a common initial part and a set of additional supplementary parts corresponding to the number of flag bits, whereby the supplementary parts can basically also comprise a plurality of data fields in a fixedly defined sequence.

p0032<figref idrefs="f0001">FIG</figref> 10 shows another embodiment of data formats of the prior art. This example is similar to the design provided for the RTCM 3.0 standard. Each data format now has an initialized encoding 4 which represents an initial part of the data format. This coding 4 is followed by a plurality of data fields C1, C2 and C3, the number and sequence of which may vary for each data format. In particular, some data fields may also be repeated, eg when the same data sets of different satellites are transmitted by a reference station at the differential GNSS.

p0033In <figref idrefs="f0002">FIG</figref> Are two sets of data formats identified by their coding 4. The versions 0001, 0002 and 0003 of these data formats are known and thus directly processable, the data formats 0004 and 0005 are newly introduced and thus not directly processable for older devices which do not take account of these data formats in their software. However, in this particular case, the non-directly processable data formats 0004 and 0005 consist of data fields which can basically be evaluated by the device or the existing software. However, the respective sequence of the data fields is not known, so that no identification and evaluation can take place.

p0034<figref idrefs="f0002">FIG</figref> Shows a first possibility for the use of evaluable data fields in the non-directly processable data formats <figref idrefs="f0002">FIG</figref>. If the device has the knowledge of the sequences of data fields, the non-directly processable data format 0004 can be processed as the known data format 0001 by omitting or hiding the data following the data field C1.

p0035The <figref idrefs="f0002">FIG</figref> Illustrates a second possibility for using evaluable data fields in non-directly processable data formats. The non-directly processable data format 0005 can be regrouped after omission of the data field C3, which corresponds to the directly processable data format 0002. If the sequence of the data fields is now known in the non-directly processable data format 0005, the evaluable data fields can be temporarily stored in memory means and then read out from the memory means in the order of the directly-processable data format 0002 when the data format is received. The directly processable data format 0002 then appears opposite the processing software.

p0036In <figref idrefs="f0003">Fig</figref> Will be shown in Fig <figref idrefs="f0002">FIG</figref> Like third possibility for the use of evaluable data fields in non-directly processable data formats is shown in which, however, no blanking of data fields takes place but the non-directly processable data format 0005 can be completely utilized after a rearrangement into a directly processable data format 0003. Thus, different directly processable data formats 0002 or 0003 can be derived from the same non-directly processable data format 0005.

p0037<figref idrefs="f0003">FIG</figref> 11 shows an example of a reference list according to the invention, with a direct indication of the sequence of data fields for the in FIG <figref idrefs="f0002">FIG</figref> Data formats introduced by way of example. The data formats are described line by line. The first field of a line is the encoding of the data format, which is represented here by a four-digit number. This is followed by a continuous indication of the data fields in their sequence within the data format. Alternatively, with the knowledge of the bit structure of the known data fields, an assignment to firmware-internal memory areas can be provided. Data fields that are not present or the end of the data format reached with this is indicated by the data field "00". The chosen representation of the<figref idrefs="f0003">FIG</figref> Is made for the sake of clarity and does not necessarily define the format of a reference list to be transmitted in reality. During the transmission of such a reference directory, it is recommended, for reasons of the data volume to be transmitted, to carry out a compression of the data volume by reducing unused lines or columns. For example, after each complete description of a data format, a corresponding indicator signal (stop sequence) can be sent for the end of the line. Alternatively, however, other suitable methods for compressing or transmitting the reference list may also be used.

p0038<figref idrefs="f0004">FIG</figref> Shows a first group of directly processable data formats 0001-0004 and a second group of non-directly processable data formats 0005 and 0006.

p0039In <figref idrefs="f0004">FIG</figref> Is used for the <figref idrefs="f0004">FIG</figref> Represent a reference list according to the invention with an indirect indication of the sequence of data fields. The description of the non-directly processable data formats 0005 and 0006 is made on the basis of the changes to known and directly processable data formats. In the first line the coding "0005" of the respective data format is specified in the first field. The following two fields of this line indicate that the sequence of the data fields in this data format corresponds to the successive sequences of the directly processable data formats 0004 and 0002, but a data field C1 still has to be removed again at the end of the sequence thus formed from known data formats. This requirement is indicated by the entry "01" in the last field of the line. In this example, the specification of the constituting known and directly processable data formats takes place after coding in a sequence starting from the left, while the data fields still to be removed are indicated beginning at the end of the line from the right. In the second line, a similar indication is given for the data format 0006. Here, the non-directly processable data format is obtained entirely from the combination of the two directly-processable data formats 0002 and 0001.

p0040In addition to evaluable data fields, data fields that are not directly processable can also contain new and thus non-evaluable data fields. In<figref idrefs="f0004">FIG</figref> A schematic representation of the handling of non-evaluable data fields with and without the use of a data directory is provided. A further non-directly processable data format 0007 is shown. The upper variant denoted by A includes the hiding of the unknown and non-evaluable data field by the device. When the message is received, the sequence of the data fields is extracted from the reference directory and the fourth data field C4 is read out or not read out of the memory means during the reception or during the subsequent evaluation so that the sequence of the data fields no longer contains the non-evaluable data field C4 . Such a sequence then corresponds to the directly processable data format 0002. The lower variant labeled B shows the use of a non-evaluable data field C4 by using a data directory 6. In this data directory 6, the information is stored which make it possible for the device, Evaluable data field.

p0041<figref idrefs="f0005">FIG</figref> 12 shows a schematic representation of such a data directory according to the invention for the definition of data types. The data directory contains a line-by-line definition of data types. Here, for example, a data type "BIT" is defined in the first line. The description is given in the first field. The second field contains the number of bits, the third field the smallest and the fourth field the largest possible value of the data type. In this case, "BIT" represents a purely binary data type with a length of one bit and the possible expressions "0" and "1". Such a data type can, for example, be used as a flag. For example, in the next line, the data type "UINT16" is set. This is a data type with the length of 16 bits, which has a value range of "0" to "65535". In the third and fourth rows, the data types "INT16" and "INT17" are defined, which also contain negative value ranges. Unused fields in the data directory are displayed in analogy to<figref idrefs="f0003">FIG</figref> and <figref idrefs="f0004">FIG</figref> With the value "00".

p0042A schematic representation of a further data directory according to the invention for defining data fields is shown <figref idrefs="f0005">FIG</figref>. A data field is defined in each line, whereby in this example,<figref idrefs="f0005">FIG</figref> Defined data types. The data field "01" is defined in the first line. This is of the data type "BIT". The following field describes the interpretation of the following fields. If there is a "0" as a flag, then fields with all possible values ​​of the value range of this data type follow. A "1" as a flag indicates that the smallest and the largest permissible value of the data type is specified in the following two fields. In this first line, all possible expressions, which only contain "0" and "1" due to the data type, follow. In the fields, these values ​​are assigned to the variable "CODE". For this example, this means that the variable "CODE" existing in the device can read out the possible values ​​"0" and "1" from a data format which is used here for the two different code forms "C / A Code" or "P Y) code "of a GNSS satellite. As a further example of a similar data field with indicator effect, the GNSS system used can also be specified. Then the GPS system, by means of which "1" could be called the GLONASS system and by "2" the GALILEO system, could be designated by a data type with three permitted values ​​by means of the "0". The data field "02" is defined in the second line. This is of the data type "UINT10" and due to the "1" in the third field it is recognizable that in the fourth field the smallest and the fifth field is the largest permissible value of the data field. In this example, these values ​​are assigned to the variable "ANT", which corresponds to the technical parameter of the antenna height.

p0043Such a data directory can now be used, for example, to make older devices which only have two GNSS systems and a rough subdivision of the antenna height usable for data with more than two systems and a finer division of the antenna height. In case the number of systems is the old device to the new data type and the new data field by the data directory mi tgeteilt. If a generally accepted variable identifier exists for the usable systems, such as "GNSS", the old device can see from the data list that the GNSS systems that can be processed by it are indexed by the first two permitted values ​​of the value range of the data type or data field will.

p0044In the case of the antenna height, the situation can arise that the resolution used is increased and not only 1024 values ​​are sent as a subdivision of the antenna height but 4096. From the data of the data directory, the lower and upper limits of the value range can now be taken out, Assignment of the new, finer values ​​to the coarser, old subdivision becomes possible. In this example, it is assumed that the old range of values ​​ranges from "0" to "1023" and a subdivision into 1024 values. The new data field has a value range of "0" to "2047" and uses a data type with 12 bits and thus a subdivision into 4095 values. This allows the old program to continue processing when the upper half of the value range is evaluated in the evaluation because these values ​​go beyond the original range. For the lower half, it must now be taken into account that two values ​​of the new scale correspond to a value of the old scale. This means that the device must interpret two related values ​​as an old value. For example, the values ​​"0" and "1" in the new data field would be interpreted as "0" by the device in both cases. The value "2843" transmitted in the new data field could not be processed and would lead to a fault message or the use of the maximum permissible value "1023" permissible in the device. The prerequisite for such an applicability of a data directory according to the invention is a corresponding consideration of such a functionality in the development of the old software.

p0045In principle, there is also the possibility to define the data types and data fields in an analogous manner to the data formats by specifying the change of known and evaluable data fields or data types.

p0046<figref idrefs="f0005">FIG</figref> Shows a schematic representation of the relationships of data types, data fields and data formats. The data types are defined in the data directory 7 ', while the data fields 7 define the data fields. A data field 05 occurring in the data format 0008 can be found in the data directory 7, where it is defined as the data type UINT10. The specification of this data type can be found in data directory 7 '.

p0047Furthermore, data fields and their contents can also be provided with abstract markings, for example a code sequence and then a continuous numbering. New data fields with a newly assigned sequence can be stored in a data directory as in<figref idrefs="f0006">FIG</figref> Can be stored. In this data directory, the new, non-evaluable data fields 67 and 68 are determined on the basis of the evaluable data fields 28 and 29. In the first line, the non-evaluable data field 67, which is based on the evaluable data field 28, but for which a new value range with the values ​​between 0 and 2400,000, as well as a resolution of 0.002, is established, is newly introduced. The definition of the data content and the subsequent data processing are taken over by the definition of the data field 28. The next line defines a possible change in the value range and the resolution for the data field 29 by specifying the new non-evaluable data field 68 and the corresponding value range or the resolution.

p0048<figref idrefs="f0006">FIG</figref> Includes a schematic representation of an example of the transmission of a reference list 10 with a method according to the invention. A DGNSS reference station 8 as the first device transmits the reference list 10 to a rover 9 and a theodolite 9 'as the second device located within the transmission range when the communication is established.

p0049Alternatively or additionally, however, a periodic broadcasting of a current reference or data directory can also take place in broadcast mode, so that all stations located within the reception area can receive the directory. The method presented here merely represents an exemplary possibility of the transmission in the bi-directional mode according to the invention. An application for a unidirectional method is also possible according to the invention.

p0050The software of the rover 9 is designed such that it can process only one data format M9 directly, whereas the theodolite 9 'is exclusively for the data format M9'. In the next step, the<figref idrefs="f0007">FIG</figref> A data transmission in the format M8 is transmitted from the DGNSS reference station 8 to the second devices 9 and 9 '. These receive the non-directly processable data format M8 and can identify or localize evaluable data fields with the help of the reference directory 10. This allows the directly processable data formats M9 or M9 'to be derived and thus the transmitted data can be used - at least partially.

p0051<figref idrefs="f0007">FIG</figref> Shows the schematic representation of a first theodolite 11 with further devices as an example of a system according to the invention. The first theodolite 11 and at least one intelligent reflector 15, as second devices together with a further theodolite 11 'as the first device, form part of a system according to the invention in which communication is effected between all the components. For this purpose, the first theodolite 11 has communication means 12, which are integrated in the first theodolites 11 in conjunction with a computer as means for processing the usable data 13 and storage means 14. At the beginning of the communication connection, the further theodolite 11 'transmits a reference list to all the second devices. This reference list is received in the first theodolite 11 by the communication means 12 and stored in the storage means 14. Data formats which are subsequently transmitted between the devices can then be used to localize data formats which can be evaluated based on the reference directory, possibly with the aid of data directories also transmitted, and to use the data contained therein. In the theodolite 11, the data for this are received by the communication means 12 and evaluated by the means for processing the usable data 13. For this purpose, the means for processing the usable data 13 access the reference directory stored in the storage means 14. In this connection, no distinction should be made with regard to the realization of evaluation and data processing means. The method according to the invention relates to all computer-assisted implementations, regardless of the specific embodiment of the program sequence in the form of a circuit, firmware or playable software.

p0052The illustrated embodiments are only examples of implementations according to the invention and are therefore not intended to be exhaustive and restrictive. In addition, the person skilled in the art can derive further embodiments according to the invention, for example using alternative forms of data storage and data processing. In particular, alternative configurations of directories can be used, whereby, in particular, summaries of data and reference directories can also be implemented in one or more aggregated directories.