Table 1: The list of changes to this CFP after publication date

The following table identifies all clarifications that have been provided in response to questions received from organizations interested in this CFP.

Table 2: The list of questions and clarifications that have been issued after publication date

The Pilot project was built upon work from Testbeds 13 through 15, Vector Tiles Pilots, 3D Tiles, and I3S; combined with the introduction of resource-oriented APIs built on the OpenAPI framework. These provide the foundation for the draft specification that is the test subject for this Sprint.

Multiple OGC members participated in the Pilot along with the OGC, The Khronos Group, and an initiative sponsor to develop the draft spec. This spec allows 2D assets (maps, vector graphics), building data, and 3D assets (glTF models, OGC building models, digital elevations) to be used together to produce a synoptic view of the region in question.

The Sprint will provide an opportunity for solution providers to collaborate and suggest revisions to the draft spec in the context of a hands-on engineering experience. Participation will raise the visibility of all participants, who will come together in an agile way to contribute to the maturity of the growing set of OGC APIs.

Up to six organizations will be selected for funded participation, with each selected participant receiving a stipend of $15,000 to use as they see fit.

This section provides the DRAFT technical architecture and identifies all requirements and corresponding work items. It references the OGC Standards Baseline, i.e., the complete set of member approved Abstract Specifications, Standards, and Community Standards.

The goal of the Pilot was to explore an integrated suite of draft specifications for 3D tiled geospatial resources and compatibility with existing OGC 3D delivery standards such as the 3D Portrayal Service OGC Implementation Standard as well as the 3D Tiles and I3S Community Standards. Related OGC 3D standards were also referenced, including CDB and CityGML.

This suite supports smooth transitions between 2D and 3D environments; allows applications working with 2D tiled resources to retrieve 3D tiled resources; and enables 3D tile bounding volumes to support multiple data containers. Pilot work products, as well as the implementation and community standards described above, will serve as baselines that may be adopted with or without changes for use in the Sprint.

Pilot Engineering Reports (ERs) are available at the links in Table 4. Note that these ERs will not become final until later in July 2020. Pre-release versions are being provided for convenience.

Table 4: Pilot Engineering Reports

The Pilot architecture is illustrated in the following two figures (and accompanying descriptions). Note that these artifacts will not become final until later in July 2020. Pre-release versions of these documents are being provided for convenience.