DOCSLIB.ORG

SAP HANA Search Developer Guide Content

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SAP HANA Search Developer Guide Content PUBLIC SAP HANA Platform 2.0 SPS 01 Document Version: 1.0 – 2017-04-12 SAP HANA Search Developer Guide Content 1 SAP HANA Search Developer Guide..............................................4 2 Defining the Persistency and Indexing............................................6 2.1 Creating Full-Text Indexes Using CDS Annotations..................................... 7 2.2 Creating Full-Text Indexes Using SQL..............................................10 Full-Text Index Types.......................................................11 Synchronization...........................................................15 Text Analysis.............................................................18 Dropping Full-Text Indexes...................................................19 Altering Full-Text Index Parameters.............................................19 Full-Text Index Parameters.................................................. 20 3 Creating Search Models......................................................27 3.1 Transformation Rules for CDS Views.............................................. 27 3.2 Modeling with CDS Annotations (XS Advanced)...................................... 28 Annotation Search.........................................................29 Annotation EnterpriseSearch .................................................34 Annotation EnterpriseSearchHana.............................................42 Annotation Hierarchy.......................................................46 Annotation Semantics......................................................47 CDSTypes.............................................................. 50 Creating a Term Mapping Table via CDS.........................................50 Example: Defining Search Configurations.........................................51 3.3 Modeling with CDS Annotations (XS Classic).........................................55 Annotation Search (XS Classic)............................................... 55 Annotation EnterpriseSearch (XS Classic)........................................57 Example: Defining Search Configurations (XS Classic)...............................60 3.4 Modeling with Built-In Procedure sys.esh_config().....................................61 Interface of sys.esh_config()..................................................61 Creating a Configuration with Method 'POST' .....................................64 Updating or Creating a Configuration with Method 'PUT'..............................66 Deleting a Configuration with Method 'DELETE'....................................66 Privileges...............................................................67 Annotations for sys.esh_config()...............................................67 3.5 Modeling With Attribute Views...................................................81 4 Accessing Data Using Full-Text Search.......................................... 83 4.1 Full-Text Search with OData.................................................... 83 SAP HANA Search Developer Guide 2 PUBLIC Content Custom Query Option 'search'................................................84 Custom Query Option 'facets'.................................................85 Custom Query Option 'facetlimit'.............................................. 85 Custom Query Option 'estimate'...............................................86 Custom Query Option 'wherefound'............................................ 86 OData Features and Limitations...............................................87 4.2 Federated Full-Text Search with Built-In Procedure sys.esh_search().......................88 Interface of sys.esh_search().................................................88 Method 'GET' - $metadata Call................................................90 Supported SQL Types......................................................98 Row Operator............................................................101 Separation of User Input and Other Filter Conditions................................102 Search in a Single View.....................................................103 Federated Search Request over Multiple Views....................................103 Query Options Supported by Federated Search................................... 104 Limit Search to one Schema.................................................105 Response of a Federated Search..............................................105 Privileges Needed to Call sys.esh_search().......................................119 Supported OData System Query Options........................................120 OData Custom Query Options for Search........................................123 OData Custom Functions for Search........................................... 125 Search Query Language....................................................126 Annotations in the Search Response........................................... 131 @com.sap.vocabularies.Search.v1.Ranking.......................................131 Dynamic Search Configurations.............................................. 132 Definition of the User Language...............................................136 Writing the Search Response to a Table.........................................137 4.3 Full-Text Search with SQL.....................................................138 Search Queries with CONTAINS.............................................. 139 EXACT Search...........................................................143 LINGUISTIC Search.......................................................144 FUZZY Search...........................................................149 5 Creating Search UIs With SAPUI5............................................. 296 6 SAP File Processing for SAP HANA.............................................297 7 SAP HANA File Loader......................................................298 SAP HANA Search Developer Guide Content PUBLIC 3 1 SAP HANA Search Developer Guide With the SAP HANA platform, your users can search tables and views much like they would when searching for information on the Internet. In SAP HANA, you can either query data using OData service definitions, directly with SQL queries, or via the built-in procedure sys.esh_search(). You build your UIs using SAPUI5. Prerequisites Before enabling search, note the following prerequisites: ● Your SAP HANA database must contain column-oriented tables. ● A valid data type must be assigned to each column. The data types of the columns determine how you can query your data. Context In SAP HANA, you can search on single or multiple columns of almost any visible data type. In addition to standard string search, SAP HANA also supports full-text search. During a full-text search, the SAP HANA search engine examines both structured text, such as author and date attributes, and unstructured text, such as body text. Unlike a string search, the sequence of words and characters used for a text search is not critical for finding matches. A full-text index enables this functionality by analyzing and preprocessing the available text semantically. This includes normalization, tokenization, word stemming, and part of speech tagging. Procedure To enable search in SAP HANA, proceed as follows: 1. Define the persistency and indexing. 2. Create your search models. 3. Access your data using full-text search. 4. Create your search UI. Related Information Defining the Persistency and Indexing [page 6] SAP HANA Search Developer Guide 4 PUBLIC SAP HANA Search Developer Guide Creating Search Models [page 27] Accessing Data Using Full-Text Search [page 83] Creating Search UIs With SAPUI5 [page 296] SAP HANA Search Developer Guide SAP HANA Search Developer Guide PUBLIC 5 2 Defining the Persistency and Indexing The first task when developing a search application is to define the persistency of your data before you can index the data for a search. Context There are two ways to define database tables, views and indexes, and search-related settings. ● Programming model A You can use Core Data Services (CDS) with its annotations syntax. ● Programming model B You can use the SQL syntax. Note We recommend using programming model A: CDS search annotations. Procedure 1. Define the persistency for your data. Create database tables, which store the data that you want to search for. Create views to model your data. Views are also needed for the OData service definitions in the CDS programming model. 2. Define indexes and choose the columns which you want to search in. Use a powerful set of properties to set up all search related functions you want to use, for example the search mode FUZZY or text analysis. Related Information Creating Full-Text Indexes Using CDS Annotations [page 7] Creating Full-Text Indexes Using SQL [page 10] SAP HANA Search Developer Guide 6 PUBLIC Defining the Persistency and Indexing 2.1 Creating Full-Text Indexes Using CDS Annotations CDS uses a SQL-like syntax to define full-text indexes and fuzzy search indexes in the technical configuration part of an entity definition. Procedure 1. You use the technical configuration part of the entity definition (in an .hdbcds or .hdbdd file) to create full-text indexes and fuzzy search indexes. CDS entities are used to define database tables. The elements of an entity describe the columns of the table. For more information, see SAP HANA Developer Guide For SAP HANA XS Advanced Model and SAP HANA Core Data Services CDS Reference. 2. Add a technical configuration part to the entity definition. 3. Define the full-text index or fuzzy search index
Load more

Recommended publications
  • Standards and Guidelines for Cadastral Surveys Using GPS
    Table of Contents Foreword ........................................................................................................................................ 3 Part One: Standards for Positional Accuracy ................................................................................ 4 Part Two: GPS Survey Guidelines ................................................................................................ 5 Section One: Field Data Acquisition Methods Section Two: Field Survey Operations and Procedures Cadastral Project Control Cadastral Measurements Section Three: Data Processing and Analysis Section Four: Project Documentation Appendix A: Definitions ............................................................................................................. 16 Appendix B: Computation of Accuracies ................................................................................... 18 Appendix C: References ............................................................................................................. 19 Attachment 1-2 Foreword These Standards and Guidelines provide guidance to the Government cadastral surveyor and other land surveyors in the use of Global Positioning System (GPS) technology to perform Public Land Survey System (PLSS) surveys of the Public Lands of the United States of America. Many sources were consulted during the preparation of this document. These sources included other GPS survey standards and guidelines, technical reports and manuals. Opinions and reviews were also sought from public and
    [Show full text]
  • National Spatial Reference System: "Positioning Changes for 2022"
    National Spatial Reference System “Positioning Changes for 2022” Civil GPS Service Interface Committee Meeting Miami, Florida September 24, 2018 Denis Riordan, PSM NOAA, National Geodetic Survey [email protected] U.S. Department of Commerce National Oceanic & Atmospheric Administration National Geodetic Survey Mission: To define, maintain & provide access to the National Spatial Reference System (NSRS) to meet our Nation’s economic, social & environmental needs National Spatial Reference System * Latitude * Scale * Longitude * Gravity * Height * Orientation & their variations in time U. S. Geometric Datums in 2022 National Spatial Reference System (NSRS) Improvements in the Horizontal Datums TIME NETWORK METHOD NETWORK SPAN ACCURACY OF REFERENCE NAD 27 1927-1986 10 meter (1 part in 100,000) TRAVERSE & TRIANGULATION - GROUND MARKS USED FOR NAD83(86) 1986-1990 1 meter REFERENCING (1 part THE in 100,000) NSRS. NAD83(199x)* 1990-2007 0.1 meter GPS B- orderBECOMES (1 part THE in MEANS 1 million) OF POSITIONING – STILL GRND MARKS. HARN A-order (1 part in 10 million) NAD83(2007) 2007 - 2011 0.01 meter 0.01 meter GPS – CORS STATIONS ARE MEANS (CORS) OF REFERENCE FOR THE NSRS. NAD83(2011) 2011 - 2022 0.01 meter 0.01 meter (CORS) NSRS Reference Basis Old Method - Ground Current Method - GNSS Stations Marks (Terrestrial) (CORS) Why Replace NAD83? • Datum based on best known information about the earth’s size and shape from the early 1980’s (45 years old), and the terrestrial survey data of the time. • NAD83 is NON-geocentric & hence inconsistent w/GNSS . • Necessary for agreement with future ubiquitous positioning of GNSS capability. Future Geometric (3-D) Reference Frame Blueprint for 2022: Part 1 – Geometric Datum • Replace NAD83 with new geometric reference frame – by 2022.
    [Show full text]
  • DOTD Standards for GPS Data Collection Accuracy
    Louisiana Transportation Research Center Final Report 539 DOTD Standards for GPS Data Collection Accuracy by Joshua D. Kent Clifford Mugnier J. Anthony Cavell Larry Dunaway Louisiana State University 4101 Gourrier Avenue | Baton Rouge, Louisiana 70808 (225) 767-9131 | (225) 767-9108 fax | www.ltrc.lsu.edu TECHNICAL STANDARD PAGE 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. FHWA/LA.539 4. Title and Subtitle 5. Report Date DOTD Standards for GPS Data Collection Accuracy September 2015 6. Performing Organization Code 127-15-4158 7. Author(s) 8. Performing Organization Report No. Kent, J. D., Mugnier, C., Cavell, J. A., & Dunaway, L. Louisiana State University Center for GeoInformatics 9. Performing Organization Name and Address 10. Work Unit No. Center for Geoinformatics Department of Civil and Environmental Engineering 11. Contract or Grant No. Louisiana State University LTRC Project Number: 13-6GT Baton Rouge, LA 70803 State Project Number: 30001520 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered Louisiana Department of Transportation and Final Report Development 6/30/2014 P.O. Box 94245 Baton Rouge, LA 70804-9245 14. Sponsoring Agency Code 15. Supplementary Notes Conducted in Cooperation with the U.S. Department of Transportation, Federal Highway Administration 16. Abstract The Center for GeoInformatics at Louisiana State University conducted a three-part study addressing accurate, precise, and consistent positional control for the Louisiana Department of Transportation and Development. First, this study focused on Departmental standards of practice when utilizing Global Navigational Satellite Systems technology for mapping-grade applications. Second, the recent enhancements to the nationwide horizontal and vertical spatial reference framework (i.e., datums) is summarized in order to support consistent and accurate access to the National Spatial Reference System.
    [Show full text]
  • UNIT-II GPS Systems:NAVSTAR-GLONAAS-Beidou-QZSS-IRNSS-GPS Receivers Based On: Data Type and Yield-Realization of Channels-Signal
    UNIT-II GPS systems:NAVSTAR-GLONAAS-Beidou-QZSS-IRNSS-GPS receivers based on: Data type and yield-Realization of channels-Signal structure:Course Acquisition(code)-Carrier ranging and Navigational message Global Positioning System (GPS), originally Navstar GPS,[1] is a satellite-based radionavigation system owned by the United States government and operated by the United States Space Force.[2] It is one of the global navigation satellite systems (GNSS) that provides geolocation and time information to a GPS receiver anywhere on or near the Earth where there is an unobstructed line of sight to four or more GPS satellites.[3] Obstacles such as mountains and buildings block the relatively weak GPS signals. The GPS does not require the user to transmit any data, and it operates independently of any telephonic or internet reception, though these technologies can enhance the usefulness of the GPS positioning information. The GPS provides critical positioning capabilities to military, civil, and commercial users around the world. The United States government created the system, maintains it, and makes it freely accessible to anyone with a GPS receiver.[4][better source needed] The GPS project was started by the U.S. Department of Defense in 1973, with the first prototype spacecraft launched in 1978 and the full constellation of 24 satellites operational in 1993. Originally limited to use by the United States military, civilian use was allowed from the 1980s following an executive order from President Ronald Reagan.[5] Advances in technology and new demands on the existing system have now led to efforts to modernize the GPS and implement the next generation of GPS Block IIIA satellites and Next Generation Operational Control System (OCX).[6] Announcements from Vice President Al Gore and the Clinton Administration in 1998 initiated these changes, which were authorized by the U.S.
    [Show full text]
  • Gis Sections Proposal
    COORDINATING WORKING PARTY ON FISHERY STATISTICS Sixth Meeting of the Aquaculture Subject Group (AS) and Twenty-seventh meeting of the Fisheries Subject Group (FS) GIS TECHNICAL WORKING GROUP FOR THE CWP HANDBOOK - GIS SECTIONS PROPOSAL Emmanuel Blondel (FAO) – [email protected] 1 CWP – AS 6th Session and FS 27th Session Rome, Italy – 15-16 May 2019 GIS Section Overview Title Definition / Scope Target Spatial reference systems Standards to use for handling a spatial reference system CWP Handbook (SRS) used with fisheries dataset. GIS Section Definitions; rationale; equivalent terminologies; recommended standard format & notations; use of Spatial Reference Identifiers (SRIDs); SRS use cases Geographic coordinates Standards for handling properly geographic coordinates CWP Handbook for reference shapes and fisheries datasets. GIS Section Definitions; rationale; recommended standard formats; Geographic coordinates use cases. Geographic classification Geographic classification and coding systems used for CWP Handbook and coding systems fisheries data. GIS Section General; Types of geographic classification systems (Irregular areas, grid reporting systems, Others); Main geographic Water main areas classification systems (FAO Major Fishing areas, Breakdown of major fishing areas; Geographic coding systems; Geographic information Standards format for data and metadata, and related CWP Data sharing formats & protocols standard protocols. and protocols/ Data formats and protocols; Metadata formats and protocols; Geospatial Section Geographic information Geographic information list of resources of interest for CWP Website resources of interest for CWP the CWP. Geographic information reference web-catalogues; GIS datasets of primary interest; 2 CWP – AS 6th Session and FS 27th Session Rome, Italy – 15-16 May 2019 GIS Section Overview • Handbook GIS Section proposal • Title: Geographic Dimension • Structure 1.
    [Show full text]
  • Mind the Gap! a New Positioning Reference
    A new positioning reference Why is the United States adopting NATRF2022? What are we doing about this in Canada? We want to hear from you! • The Canadian Geodetic Survey and the United States • Improved compatibility with Global Navigation • The Canadian Geodetic Survey is working closely National Geodetic Survey have collaborated for Satellite Systems (GNSS), such as GPS, is driving this with the United States National Geodetic Survey in • Send us your comments, the challenges you over a century to provide the fundamental reference change. The geometric reference frames currently defining reference frames to ensure they will also foresee, and any concerns to help inform our path Mind the gap! systems for latitude, longitude and height for their used in Canada and the United States, although be suitable for Canada. forward to either of these organizations: respective countries. compatible with each other, are offset by 2.2 m from • Geodetic agencies from across Canada are A new positioning reference the Earth’s geocentre, whereas GNSS are geocentric. - Canadian Geodetic Survey: nrcan. • Together our reference systems have evolved collaborating on reference system improvements geodeticinformation-informationgeodesique. to meet today’s world of GPS and geographical • Real-time decimetre-level accuracies directly from through the Canadian Geodetic Reference System [email protected] NATRF2022 information systems, while supporting legacy datums GNSS satellites are expected to be available soon. Committee, a working committee of the Canadian
    [Show full text]
  • OMB Circular No. A-16 Revised
    OMB Circular No. A-16 Revised M-11-03, Issuance of OMB Circular A-16 Supplemental Guidance (November 10, 2010) (34 pages, 530 kb) August 19, 2002 TO THE HEADS OF EXECUTIVE DEPARTMENTS AND ESTABLISHMENTS SUBJECT: Coordination of Geographic Information and Related Spatial Data Activities This Circular provides direction for federal agencies that produce, maintain or use spatial data either directly or indirectly in the fulfillment of their mission. This Circular establishes a coordinated approach to electronically develop the National Spatial Data Infrastructure and establishes the Federal Geographic Data Committee (FGDC). The Circular has been revised from the 1990 version to reflect changes in technology, further describe the components of the National Spatial Data Infrastructure (NSDI), and assign agency roles and responsibilities for development of the NSDI. The revised Circular names the Deputy Director for Management of OMB as Vice-Chair of the Federal Geographic Data Committee. TABLE OF CONTENTS BACKGROUND 1. What is the purpose of this Circular? 2. What is the National Spatial Data Infrastructure (NSDI)? a. What is the vision of the NSDI? b. What are the components of the NSDI? (1) What is a data theme? (2) What are metadata? (3) What is the National Spatial Data Clearinghouse? (4) What is a standard? (5) How are NSDI standards developed? (6) What is the importance of collaborative partnerships? (7) What are the federal activities and technologies that support the NSDI? 3. What are the benefits of the NSDI? 4. What is the Federal Geographic Data Committee (FGDC)? a. What is the FGDC structure and membership? b. What are the FGDC procedures? POLICY 5.
    [Show full text]
  • Web-Based Visualization of 3D Geospatial Data Using Java3d
    Exploring Geovisualization Web-Based Visualization of 3D Geospatial Data Gobe Hobona, Philip James, and David Fairbairn Using Java3D University of Newcastle upon Tyne eb-based visualization of 3D geospatial tion for Standardization (ISO), which has adopted the Wdata has long been an area of research Simple Features model as the ISO19125 specification.4 within the geospatial information community. It’s a We’ve developed GeoDOVE, a Java3D-based prototype proven reliable and effective method for integrating het- system that retrieves geospatial data from conventional erogeneous data sets from different application domains spatial database servers, allows modification of the visu- and communicating the contents to the user. Early alization during runtime, and lets users remotely modi- research used the Virtual Reality Modeling Language fy attributes using the Structured Query Language (SQL). (VRML) for creating 2.5D and 3D virtual worlds. Since then, however, researchers have made significant GeoDOVE system architecture advances in geospatial information technology that could The current version of VRML⎯VRML97⎯offers two potentially help improve Web-based 3D geographic infor- approaches for linking a 3D model to external programs mation systems (GISs). For example, the geospatial infor- and data sources: mation community has standardized relational models for holding 3D spa- ■ script nodes and Spatial database servers allow tial data. Researchers have also made ■ the Java external authoring interface (EAI). for the storage and access of significant advances in the develop- 3D geospatial data using Open ment of spatial database engines Although the EAI provides a more flexible approach Geospatial Consortium such as MySQL (see http://www. to linking a VRML model to external programs than the standards.
    [Show full text]
  • Oracle Spatial 11G Technical Overview
    <Insert Picture Here> Oracle Spatial 11g Dr. Siva Ravada New in Oracle Spatial 11g • 3D Support • Spatial Web Services • Network Data Model • GeoRaster • Performance Improvements 3D Applications • Location-based services • Augmented reality • GIS Analytical Modeling • Terrain (2.5D) and 3D objects • City Planning/Administration • Infrastructure Design • Accurate descriptions of objects 3D Mash-ups GIS Analytical Modeling & Simulation Flood Plain Analysis Petroleum Exploration CAD Infrastructure Design Courtesy Parsons Brinckerhoff Simulation, Gaming, and VR Customer Requirements • Enterprise-class RDBMS to manage ALL geospatial types • 2D, 3D, Rasters, Networks, Topology, Attributes • Native type support, indexing, and analysis • Support for coordinate systems • Standards based: SQL, Java, .NET • Addresses range of 3D application domains • GIS, CAD/CAM • City Modeling, environmental analysis • Building City models (Collada, CityGML) • Real Estate, asset management • Personal navigation • VR, gaming, simulation • Geo-engineering (CAD) • Addresses large volumes of 3D point data • Laser scanning (LIDAR, sonar) • Surfaces (TINS, DEMS) Technology Trends in 3D • Massive new sensor hardware capabilities • Automated Data Capture with millions of points • Increased productivity in 3D data management workflow • Automatic and semi-automatic extraction of features from raw data • Improve performance and scalability of existing workflows • Bridging gap between GIS and CAD • Bring 3D to Mainstream Business Applications • Current applications do navigation
    [Show full text]
  • Geographic Information — Geography Markup Language (GML)
    AS/NZS ISO 19136.1:2020 ISO 19136-1:2020 Australian/New Zealand Standard™ Geographic information — Geography Markup Language (GML) Part 1: Fundamentals AS/NZS ISO 19136.1:2020 This Joint Australian/New Zealand Standard™ was prepared by Joint Technical Committee IT-004, Geographical Information/Geomatics. It was approved on behalf of the Council of Standards Australia on 8 July 2020 and by the New Zealand Standards Approval Board on 5 August 2020. This Standard was published on 28 August 2020. The following are represented on Committee IT-004: ANZLIC — The Spatial Information Council Australian Antarctic Division Australian Bureau of Meteorology Australian Maritime Safety Authority CSIRO Curtin University of Technology Department of Agriculture, Water and the Environment Department of Defence (Australian Government) Geoscience Australia Science New Zealand Services Australia (Australian Government) Spatial Industries Business Association University of Melbourne This Standard was issued in draft form for comment as DR AS/NZS ISO 19136.1:2020. Keeping Standards up-to-date Ensure you have the latest versions of our publications and keep up-to-date about Amendments, Rulings, Withdrawals, and new projects by visiting: www.standards.org.au www.standards.govt.nz ISBN 978 1 76072 962 2 AS/NZS ISO 19136.1:2020 ISO 19136-1:2020 Australian/New Zealand Standard™ Geographic information — Geography Markup Language (GML) Part 1: Fundamentals Originated as AS/NZS ISO 19136:2008. Jointly revised and redesignated as AS/NZS ISO 19136.1:2020. COPYRIGHT © ISO 2020 — All rights reserved © Standards Australia Limited/the Crown in right of New Zealand, administered by the New Zealand Standards Executive 2020 All rights are reserved.
    [Show full text]
  • FDM 9-20 Spatial Reference Systems
    Facilities Development Manual Wisconsin Department of Transportation Chapter 9 Surveying and Mapping Section 20 Spatial Reference Systems FDM 9-20-1 General February 28, 2001 The discipline of surveying consists of determining or establishing relative positions of points above, on, or beneath the surface of the earth. In Wisconsin, there are two primary spatial reference systems for defining the location of a point: - The U.S. Public Land Survey System (PLSS). - The National Spatial Reference System (NSRS). The PLSS is based on a system of townships, ranges, and sections (see FDM 9-20-5). The PLSS provides the basis for almost all legal descriptions of land. The NSRS, which includes the former National Geodetic Reference System (NGRS), is a mathematical reference system (see FDM 9-20-10). The NSRS consists of precisely measured networks of geodetic control that support accurate mapping over large areas. To understand the roles of these reference systems, it is important to recognize that the PLSS was designed for land ownership purposes but not for accurate mapping, and the NSRS was designed for geodetic surveying and mapping but not for land ownership documentation. Since accurate property maps are becoming essential with digital-based ownership documents, it is important that there be a substantial link between the two reference systems. Methods are needed to utilize the spatial characteristics of the NSRS when addressing the location of landmarks. Fortunately, recent technological developments such as the Global Positioning System (GPS), electronic total station survey instruments, and computer aided drafting (CAD) now make the task of using the PLSS and NSRS together more efficient, economical, and practical.
    [Show full text]
  • GML in JPEG 2000 for Geographic Imagery (GMLJP2) Encoding Specification
    Open Geospatial Consortium Inc. Date: 2006-01-20 Reference number of this OGC® document: OGC 05-047r3 Version: 1.0.0 Category: OpenGIS® Encoding Specification Editors: Martin Kyle, David Burggraf, Sean Forde, Ron Lake GML in JPEG 2000 for Geographic Imagery (GMLJP2) Encoding Specification Copyright © 2006. Open Geospatial Consortium, Inc. All Rights Reserved. To obtain additional rights of use, visit http://www.opengeospatial.org/legal Document type: OpenGIS® Encoding Specification Document subtype: (none) Document stage: Approved Document language: English OGC 05-047r3 This page left intentionally blank. ii Copyright © 2006. Open Geospatial Consortium, Inc. All Rights Reserved. OGC 05-047r3 Contents Page 1 Scope ............................................................................................................................1 2 Conformance................................................................................................................1 3 Normative references...................................................................................................1 4 Terms and definitions..................................................................................................2 5 Conventions..................................................................................................................5 5.1 Abbreviated terms........................................................................................................5 5.2 Document terms and definitions.................................................................................6
    [Show full text]