OPC 10000-211: Global Positioning
Released 1.0.0
2025-10-09
|
|
|
|
|
|||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||
|
OPC Unified Architecture Part 211: Global Positioning
Release 1.0.0 2025-09-25
|
||||||||||||||||||||||||||||||||||||||||||
|
Specification Type: |
Industry Standard Specification |
Comments: |
|
|
|
|
|
|
|
Doc-Number |
OPC 10000-211 |
|
|
|
Title: |
OPC Unified Architecture Part 211 :Global Positioning |
Date: |
2025-09-25 |
|
|
|
|
|
|
Version: |
Release 1.0.0 |
Software: |
MS-Word |
|
|
|
Source: |
OPC 10000-211 OPC UA for Global Positioning.v1.0.0.docx |
|
|
|
|
|
|
Author: |
OPC Foundation |
Status: |
Release |
|
|
|
|
|
CONTENTS
1Scope 1
2Normative references 2
3Terms, abbreviated terms and conventions 3
3.1Overview 3
3.2OPC UA for Global Positioning terms 3
3.2.1Global Position 3
3.2.2Global Location 3
3.2.3Zone 3
3.2.4SourceId 3
3.2.5Local Coordinate System 3
3.3Abbreviated terms 4
3.4Conventions used in this document 4
3.4.1Conventions for Node descriptions 4
3.4.2NodeIds and BrowseNames 7
3.4.3Common Attributes 8
3.4.4Structures 9
4General information to Global Positioning and OPC UA 11
4.1Introduction to Global Positioning 11
4.2Introduction to OPC Unified Architecture 11
4.2.1What is OPC UA? 11
4.2.2Basics of OPC UA 11
4.2.3Information modelling in OPC UA 12
5Use cases 16
5.1Global Asset Tracking 16
5.2Robotic Navigation and Relative Spatial Localization 16
5.3Remote Monitoring and Field Operations 17
6Global Positioning Information Model overview 17
6.1Overview 17
6.2Global Position 17
6.3Global Location 18
6.4Zones 19
6.5Connecting trackable Assets to global position and location information 21
7OPC UA ObjectTypes 21
7.1ZoneType definition 21
7.1.1Overview 21
7.1.2ObjectType definition 22
8OPC UA VariableTypes 22
8.1GlobalPositionType 22
8.2GlobalLocationType 26
9OPC UA DataTypes 28
9.13DGeographicCoordinateDataType 28
9.2GlobalPositionDataType 28
9.3GlobalLocationDataType 29
9.4GroundControlPointDataType 29
10Instances 30
10.1GlobalLocations 30
11Profiles and Conformance Units 31
12Namespaces 32
12.1Namespace Metadata 32
12.2Handling of OPC UA Namespaces 32
Annex A (normative) Global Positioning Namespace and mappings 34
A.1NodeSet and supplementary files for Global Positioning Information Model 34
A.2Capability Identifier 34
Figures
Figure 1 – The scope of OPC UA within an enterprise 12
Figure 2 – A basic Object in an OPC UA Address Space 13
Figure 3 – The relationship between Type Definitions and Instances 14
Figure 4 – Examples of References between Objects 15
Figure 5 – The OPC UA Information Model notation 15
Figure 6 – GlobalPositionType VariableType 18
Figure 7 – GlobalLocationType VariableType 19
Figure 8 – ZoneType ObjectType 20
Figure 9 – Example of relation between zones and global position and location 21
Tables
Table 1 – Examples of DataTypes 5
Table 2 – Type Definition Table 6
Table 3 – Examples of Other characteristics 6
Table 4 – <some>Type additional References 6
Table 5 – <some>Type additional subcomponents 7
Table 6 – <some>Type Attribute values for child Nodes 7
Table 7 – Common Node Attributes 8
Table 8 – Common Object Attributes 8
Table 9 – Common Variable Attributes 9
Table 10 – Common VariableType Attributes 9
Table 11 – Common Method Attributes 9
Table 12 – Structures without optional fields where none of the fields allow subtypes 10
Table 13 – Structures with optional fields 10
Table 14 – Structures where one or more of the fields allow subtypes 10
Table 15 – ZoneType definition 22
Table 16 – ZoneType Attribute values for child Nodes 22
Table 17 – GlobalPositionType definition 23
Table 18 – GlobalPositionType Attribute values for child Nodes 23
Table 19 – GlobalLocationType definition 27
Table 20 – GlobalLocationType Attribute values for child Nodes 27
Table 21 – 3DGeographicCoordinateDataType Structure 28
Table 22 – 3DGeographicCoordinateDataType definition 28
Table 23 – GlobalPositionDataType Structure 28
Table 24 – GlobalPositionDataType definition 29
Table 25 – GlobalLocationDataType Structure 29
Table 26 – GlobalLocationDataType definition 29
Table 27 – GroundControlPointDataType Structure 29
Table 28 – GroundControlPointDataType definition 30
Table 29 – GlobalLocations definition 30
Table 30 – NamespaceMetadata Object for this document 32
Table 31 – Namespaces used in a Global Positioning Server 32
Table 32 – Namespaces used in this document 33
GPOS Owners
____________
AGREEMENT OF USE
COPYRIGHT RESTRICTIONS
This document is provided "as is" by the GPOS Owners.
Right of use for this specification is restricted to this specification and does not grant rights of use for referred documents.
Right of use for this specification will be granted without cost.
This document may be distributed through computer systems, printed, or copied as long as the content remains unchanged and the document is not modified.
GPOS Owners do not guarantee usability for any purpose and shall not be made liable for any case using the content of this document.
The user of the document agrees to indemnify GPOS Owners and their officers, directors, and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.
The document shall not be used in conjunction with company advertising and shall not be sold or licensed to any party.
The intellectual property and copyright are solely owned by the GPOS Owners.
PATENTS
The attention of adopters is directed to the possibility that compliance with or adoption of GPOS Owners’ specifications may require use of an invention covered by patent rights. GPOS Owners shall not be responsible for identifying patents for which a license may be required by any GPOS Owners’ specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. GPOS Owners specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.
WARRANTY AND LIABILITY DISCLAIMERS
WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE GPOS OWNERS MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE GPOS OWNERS BE NOT LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The entire risk as to the quality and performance of software developed using this specification is borne by you.
RESTRICTED RIGHTS LEGEND
This Specification is provided with Restricted Rights. Use, duplication, or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor/manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830.
COMPLIANCE
The combination of GPOS Owners shall at all times be the sole entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials as specified within this document. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by GPOS Owners. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.
Trademarks
Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.
GENERAL PROVISIONS
Should any provision of this Agreement be held to be void, invalid, unenforceable, or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.
This Agreement shall be governed by and construed under the laws of the Federal Republic of Germany.
This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.