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.

Figure 1: The architecture of the various Pilot capabilities is shown with connecting arrows indicating request flow. Each client has a built-in Globe model that provides a base coordinate system for all additional data.

Arrows show the potential paths of requests from the clients; data flow is in the reverse direction. The connecting lines indicate conceptual requests and data flows. The actual connections may be distributed across several physical devices. More-detailed component descriptions are provided after Figure 2.

Figure 2: Pilot data architecture illustrating access to datasets for two North American cities (Montreal and New York). The architecture supporting New York City is shown in detail.

The Pilot API resource architecture is shown in Figure 2. It illustrates access to datasets for two North American cities, New York and Montreal with the detailed structure only shown for New York City. The illustration is not meant to be a complete collection of all possible or existing data sets.

Here are more-detailed component descriptions to accompany Figure 1.

The Pilot built on previous work from other OGC initiatives and Standards Program efforts. These documents also serve as foundational references for this Sprint. The document titles and links are listed here, along with links to the OpenAPI and glTF specs. Full descriptions are provided in Previous Work.

Here’s a summary of items to be provided in support of Sprint activities (grouped by providing organization):

Kickoff: The Kickoff is a virtual meeting (using GoToMeeting) and is mandatory for at least one technical point of contact for each participant. The Initiative Architect will lead a review of the final version of the draft spec. Detailed instructions for sprint-week activities will also be provided. The Kickoff is scheduled to take place 09:30-12:30 EDT on September 1, 2020.

Sprint Week: All participants are required to attend and participate for the entirety of the Sprint Week. The Sprint Week will be a full virtual event (no physical meeting). The event is scheduled to take place September 21-25, 2020.

All participants will be required to be available for teleconferences for communication with other team members. These are tentatively scheduled for 10:00-16:00 EDT during each day of Sprint Week.

Development of Document Deliverables: Development of Sprint Reports (SRs) and other document deliverables will commence immediately following Kickoff. SRs should be authored in AsciiDoc format (see the AsciiDoc User Guide and the AsciiDoc Cheat Sheet). Exceptions such as Google Docs or Microsoft Word might be permitted on a case-by-case basis.

This initiative will be conducted within the policy framework of OGC’s Bylaws and Intellectual Property Rights Policy ("IPR Policy"), as agreed to in the OGC Membership Agreement, and in accordance with the OGC Innovation Program Policies and Procedures and the OGC Principles of Conduct, the latter governing all related personal and public interactions.

Several key requirements are summarized below for ready reference:

The Innovation Program Team (IP Team) for this initiative will include an Initiative Director and an Initiative Architect. Unless otherwise stated, the Initiative Director will serve as the primary point of contact (POC) for the OGC. The Initiative Architect will work with Participants to ensure that initiative activities and deliverables are properly assigned and performed.

Ongoing CFP updates and answers to questions can be tracked by monitoring this CFP. Bidders may submit questions by email to the OGC Technology Desk (techdesk@opengeospatial.org). Question submitters will remain anonymous, and answers will be regularly compiled and published in the Corrigenda and Clarifications.

Any updates to this CFP (including questions and clarifications) will be posted to the original URL of this CFP.