A Community standard is an official position of the OGC endorsing a specification or standard developed external to the OGC. A Community standard is considered to be a normative standard by OGC membership and part of the OGC Standards Baseline. The key consideration for a Community standard is that there must be strong evidence of implementation. OGC does not take over the maintenance of the work, rather a Community standard is a “snapshot” of a mature standard for which the originator has either shared the Intellectual Property Rights with the OGC or granted unlimited free use of the Intellectual Property to all implementers.
Community standards can serve two purposes:
to bring de facto standards from the larger geospatial community to be a stable reference point that can normatively referenced by governments and other organizations; and
to bring new, but implemented, standards to the OGC to form the basis for further refinement and development of interoperability between other OGC standards.
|Document Title (click to view/download)||Version||Doc.#||Editor||Date|
|OGC® 3D Tiles Specification||1.0||18-053r2||Patrick Cozzi, Sean Lilley, Gabby Getz||2017-08-18|
|3D Tiles is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds. It defines a hierarchical data structure and a set of tile formats which deliver renderable content. 3D Tiles does not define explicit rules for visualization of the content; a client may visualize 3D Tiles data however it sees fit.|
|LAS Specification 1.4 OGC Community Standard||1.4||17-030r1||ASPRS||2018-03-01|
The LAS file is intended to contain LIDAR (or other) point cloud data records. The data will generally be put into this format from software (e.g. provided by LIDAR hardware vendors) which combines GPS, IMU, and laser pulse range data to produce X, Y, and Z point data. The intention of the data format is to provide an open format that allows different LIDAR hardware and software tools to output data in a common format.
|OGC® GeoRSS Encoding Standard||1.0||17-002r1||Carl Reed||2017-08-18|
|GeoRSS is designed as a lightweight, community driven way to extend existing RSS feeds with simple geographic information. The GeoRSS standard provides for encoding location in an interoperable manner so that applications can request, aggregate, share and map geographically tag feeds.|
|OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification||1.1||17-014r7||Carl Reed, Tamrat Belayneh||2020-02-08|
A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.
The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types.