The GeoBI Ad Hoc has been renamed to GeoBI DWG upon approval during the December 2011 TC/PC meetings.
Business intelligence (BI) aims to support better business decision-making using computer-based techniques used for identifying, extracting and analyzing business data. Geospatial Business Intelligence (GeoBI) adds geospatial technology to BI.
1 WFS/FES SWG
1. RESTful Service Policy Standards Working Group
1. ARML 2.0 Standards Working Group
ARML (Augmented Reality Markup Language) 1.0 is a descriptive, XML based data format, specifically targeted for mobile Augmented Reality (AR) applications. ARML focuses on mapping georeferenced Points of Interest (POIs) and their metadata, as well as mapping data for the POI content providers publishing the POIs to the AR application. ARML was defined in late 2009 by the creators of the Wikitude World Browser to enable developers to create content for Augmented Reality Browsers.
The work of the REST Sub Committee of the OGC Standards Program is to define a set of best practices and potentially rules for use in creating REST serializations/instances of existing or furture OGC web services standards.
Chair: Josh Lieberman
This SWG is focused on processing the OGC GeoServices REST 1.0 candidate standard.
This OGC GeoServices REST Candidate Standard Version 1.0 standard is derived from the “Esri GeoServices REST Specification Version 1.0” which was developed to provide interoperability between ArcGIS Server and the broader information technology community. The candidate standard is designed to be implemented without the use of Esri products. The OGC version differs from the Esri version in that it is presented in a vendor neutral fashion appropriate for an OGC standard. For example the names of the types have been changed. The specification currently provides a JSON encoding, but does not limit alternate JSON representations (such as GeoJSON ).
On 2 February 2012, the OGC began the OGC Web Services, Phase 9 (OWS-9) Testbed process with a Request for Quotations/Call for Participation (RFQ/CFP) to solicit proposals in response to requirements. 10 sponsors provided requirements, a testbed plan was developed, and 45 technology provider participants worked together for 8 months developing and testing interoperability solutions to meet those requirements.