1. Introduction

The Open Geospatial Consortium (OGC) is releasing this Call for Participation (CFP) to solicit proposals for the OGC Federated Marine Spatial Data Infrastructure Pilot 2022 (FMSDI-22).

We currently experience a rapidly changing environment in the Arctic with climate change being an important factor. Coastlines change, sea currents are affected that lead to changing climate on both land and sea and have consequences on marine food chains. Formerly frozen methane deposits in the Arctic Ocean have started to be released, whereas changing ice patterns make large areas of the Arctic accessible and navigable during long periods of the year. Thus, impacts of climate change on the Arctic environment present both challenges and potential opportunities for coastal communities, ecosystems, and economic activities. With more and more data becoming available, the question is: what can we do with all of these data? Do we better understand the status quo, or changes over time? Is it the right data that we find? What do we have and what are we missing? Do the interfaces to these data work? And, do we have the right tools?

banner

Expressed more specifically, we can ask what analytical predictive information products can we extract from the available data? What is the role of EO Frameworks to share multi-temporal, multi-spectral analysis as information products? How can these data streams feed into and streamline regulatory processes?

The goal of this pilot is to explore the current data basis, the accessibility to these data, processing capacities, analytical components, and visualization options that help us to better understand the opportunities and challenges described above. The pilot explores the data integration and analysis layer, but shall demonstrate information products for senior decision makers in particular.

It has been widely recognized that standards play an essential role for data integration and processing. FAIR principles as in Findable, Accessible, Interoperable, and Reusable are key to integrate data from multiple sources and owners into analytical environments. This pilot shall explore how we can combine geospatial data at standardized interfaces with tabular data and live spatial data feeds. These data feeds, e.g. ocean monitoring buoys or weather sensors represent a key dimension of a Digital Arctic. Lots of data in the marine environment have been produced with navigation as the primary goal. Is that data fit for other purposes, such as search & rescue, environment, economics? What are the new purposes and use cases we can build with the data we have available?

This pilot builds on the results from the first Arctic Spatial Data Pilot conducted in 2017 without repeating it. Instead, new use cases and scenarios shall be developed. What is the delta between what we can do today compared to 2017? What new data is available? What role do new technologies play, such as OGC Web APIs and new cataloging mechanisms such as the Spatial Temporal Asset Catalog, STAC? How to sustain catalog(s) after the completion of the Fed. Marine SDI Pilot (i.e., after the life of this initiative). Is there a role for evergreen cataloging methodologies?

This pilot addresses all these questions, challenges, and opportunities using three main pillars. As illustrated in Figure 1, the first pillar is "Demonstration". Here, participants demonstrate Arctic scenarios that integrate data from various sources with emphasis on the land-sea interface. The second pillar explores the value of existing and emerging OGC standards, and the third pillar looks at related standards from the International Hydrographic Organization, IHO.

overview
Figure 1. Overview of the pilot’s three pillars and their respective work items on top together with the envisioned results of the pilot at the bottom; all in context of federated marine spatial data infrastructures

In summary, together with our sponsoring organizations and international bodies such as IHO and UNGGIM, OGC wants to explore the current status of distributed land and marine data services for the Arctic marine and coastal environment. Participants are invited to develop demonstration scenarios that show how data can be discovered, accessed, used and reused, shared, processed, analyzed, and visualized. All scenarios shall be located in the Arctic. Each scenario shall demonstrate what is currently possible and what gaps are experienced with the resources that can be discovered on the Internet. In the context of the scenario developments, the following questions shall be answered by each participant:

  1. What data do I need for my scenario (ideally)?

  2. Do I find all the data I need?

  3. Was sufficient metadata provided that helped during the discovery phase (include metadata for the services as well as for the data as such)?

  4. From what I found, can I access the data directly or are there any obstacles to data access?

  5. Can I access the subset of data that I am interested in?

  6. Can data or analytical service be streamed via a known standard or specification?

  7. Is it possible to process the data online, or do I need to download and process locally?

  8. What standards are used for data discovery, access, and processing interfaces?

  9. What data formats are offered?

  10. How complete is the data, e.g. with regard to spatial or temporal extent?

  11. How difficult is it to integrate the data into an analysis and visualization environment?

  12. What is my overall experience developing the scenario?

  13. How would this be packaged for a senior executive?

  14. How may communities with very low bandwidth participate?

Initially, participants are free to define and execute their own (sub-) scenario. During the course of the pilot, all participants will work together to integrate these individual scenarios into one overarching scenario. Imagine this scenario as a super-scenario with multiple, loosely coupled sub-scenario parts. Ideas and requirements for all scenarios are described below.

All experiences made during the development and implementation phase of the scenario(s) will be captured in a single Engineering Report. OGC staff will edit and serve as primary author of this document. All participants are contributing their text material that includes sub-scenario documentation as well as experiences made and lessons learned during all phases of scenario development. Eventually, all participants together will demonstrate a federation model for Marine Spatial Data Infrastructures as part of the overarching scenario.

The scenario(s) data will be served and processed by a variety of services that may or may not be part of a Marine Spatial Data Infrastructure. This brings up the question how to establish a federated model of these infrastructures or parts thereof. How can we integrate individual data services and Web portals? What common baseline exists or should be developed?

Based on all experiences and lessons learned, recommendations for future enhancements shall be developed. The demonstration scenarios shall put special emphasis on OGC and IHO S-100 standards. How mature are these? What modifications might be required to further enhance these standards? Are there any best practices that can be identified and described?

2. Background

A Marine Spatial Data Infrastructure (MSDI) is a specific type of Spatial Data Infrastructure (SDI) with focus and the marine environment. It is not only a collection of hydrographic products, but an infrastructure that promotes interoperability of data at all levels (e.g., national, regional, international). Like all SDIs, it tries to enhance discoverability, accessibility, and interoperability of marine data. By doing so, it supports a wider, non-traditional user-base of marine data, far beyond what is typically used for navigation.

2.1. International Efforts

The Arctic Regional Marine Spatial Data Infrastructure Data Working Group (ARMSDIWG) of the International Hydrographic Organization (IHO) identifies and assesses the statuses of individual MSDI implementations, considers MSDI policies in related international projects and cooperates specifically with the spatial data infrastructure for the Arctic. Among other tasks, the working group analyzes how maritime authorities can contribute their spatial information and the necessary updates, so information can easily be collated with other information to a current overall picture for the Arctic region. Through association with the OGC Marine DWG, the ARMSDIWG monitors the development of relevant and applicable OGC standards and activities in the context of marine data services for the Arctic.

2.2. Previous Initiatives

This initiative, which is conducted under the OGC Innovation Program, builds directly on what was accomplished earlier in the year through the Federated Marine Spatial Data Infrastructure Pilot 2021. The 2021 pilot again built on the works of prior initiatives, such as the Marine Spatial Data Infrastructure Concept Development Study, the Maritime Limits and Boundaries Pilot, and the Arctic Spatial Data Infrastructure Pilot. The latter plays an important role for this 2022 pilot, because it followed comparable goals and motivations.

The Marine Spatial Data Infrastructure Concept Development Study summarized the efforts and information gathered from a Request for Information which focused on in-depth data requirements, architecture, and standards needs for a Marine Spatial Data Infrastructure. The Maritime Limits and Boundaries Pilot worked to build a detailed implementation for testing S-121 Standard data. The Arctic Spatial Data Infrastructure Pilot aimed to utilize international standards to support a spatial data exchange focusing on the complex issues of Arctic marine space.

3. Master Schedule

Table 1. Master Schedule
Milestone Date  Event

M01

May 22, 2022

Release of Call for Participation

M02

June 24, 2022

Close of Call for Participation

M03

July 5-6, 2022

Kick-off Workshop

M04

August 01, 2022

Engineering Report (ER) Draft

M05

September-November 2022

Start Deliverable Development

M06

October-November 2022

Start Technology Integration Experiment (TIE) Testing

M07

November 15, 2022

Final Engineering Report due

M08

December 2022

Demonstration of results at OGC Member Meeting

M09

January 02, 2023

Public release of Engineering Reports

M10

January 15, 2023

End of initiative

4. Scope

The Federated Marine Spatial Data Infrastructure 2022 Pilot will focus on a couple of aspects all contributing to an overarching scenario that helps better understand both the challenges and potential opportunities for coastal communities, ecosystems, and economic activities in the Arctic region. Bidders are invited to describe ideas for an overarching scenario in their proposals. The final scenario will be mutually agreed by all participants during the execution phase of the pilot.

The sub-scenarios, i.e., those scenarios that are developed by each participant individually, can address any aspect of the changing Arctic landscape. Potential activities may include:

  • Demonstrating interoperability between land and marine data that is necessary to understand coastal erosion (e.g., ocean currents, geology, permafrost characteristics, etc.)

    • Coastal erosion over time, which includes a temporal component (possible study area: Alaska, Canada, Greenland, and Iceland)

    • Defining coastline (highest line) and coastal transition zone (intertidal zone, see Figure 2). The Intertidal Zone is the area of shore between the high-tide and low-tide lines. To do so, it would be necessary to connect with national organisations working on the coastal transition zone. OGC staff and sponsors will help making these connections.

  • General sensitivity to climate change

oceanZonesAndSensitivity
Figure 2. Left: The ocean can be divided into zones based on depth and distance from shore (source: mtchs.org). Right: Sensitivity to Climate Change (source: NRCan)
  • Demonstrating the role of OGC standards to support measurement of impacts of coastal erosion (e.g. infrastructure, food safety, traditional activities, wildlife migration, etc.) on coastal areas in the context of a changing Arctic. For example, mapping coastal sensitivity to climate change and the impacts on local communities.

  • Effects of climate change and a changing Arctic environment on wildlife migration corridors: land-sea ice-island (caribou) and sea (marine mammals)

  • Mapping of coastal sensitivity to climate change and the impacts on local communities. This work could build on previous work by Shaw et al, 1998; and ongoing work that has developed an extensive database to help map sensitivity to inundation, coastal flooding and erosion arising from climate-related changes in sea level, sea ice and storminess. Great examples that address all of Canada’s marine coasts” have been described by Lemmen et. al in From Canada’s Marine Coasts in a Changing Climate2

  • Investigating the role of vector tiles and style sheets across land - sea interface

  • A sea-based, health and safety scenario incorporating the land/sea interface in the Arctic. This scenario would demonstrate the technology and data used with OGC, IHO, and other community standards in response to a grounding event and the evacuation of a cruise ship or research vessel in the Arctic.

    Such a scenario would be able to incorporate, but not be limited to, voyage planning information (e.g. Arctic Voyage Planning Guide, Safety of Navigation products and services, Maritime Safety Information), access to land-based emergency services/resources (e.g., Coast Guard stations, transit times to emergency services or ports, medical facilities and resources, helicopter access), coastal environmental/topographic/hydrographic/maintenance data (e.g., deposition and dredging of seafloor sediment, changes in coastline and bathymetry), and Global Maritime Traffic data use in the Arctic (e.g. to help assess likelihood of other ships in responding to a ship in distress).

4.1. Pilot Execution Process

All bidders are invited to suggest scenario elements or modifications to this overall scenario. At the kick-off meeting, participants together with sponsoring organizations and OGC staff will further refine the high level scenario. During the pilot execution phase, each participant will evaluate the research questions stated above. To do so requires a thorough execution of all phases of data discovery, access, integration, analysis, and visualization. Participants are invited to collaborate as much as possible and support each other with data, processing capacities, and visualization tools. The overarching goal is to learn more about current capabilities and shortcomings of marine data services offered by all Marine Spatial Data Infrastructures, Web portal, and directly accessible cloud native data. The following graphic illustrates the pilot development process.

process

4.2. Data and Services

Participants shall incorporate the ARMSDIWG’s Arctic Voyage Planning Guide (AVPG) organization efforts into the Arctic-focused defined Land/Sea Use Case. Participants shall attempt to utilize multiple data from the below list of themes and content while identifying gaps, and making recommendations to improve the federation of data services required for usability of voyage planning in the Arctic. In addition to the marine sea data, the scenario shall include elements coming from the land side. This is particularly interesting, because often land-sea use cases require the integration of data from multiple organizations, with each organization potentially limiting its view to one side of the land-sea transition. Thus, interoperability of marine data with land/terrestrial geospatial web-based data services, for example, from collaborative partner-based efforts that operate Spatial Data Infrastructures for the Arctic, shall be part of this pilot.

The Arctic Voyage Planning Guide contains the following themes and content:

  • Theme 1 – Carriage Requirements

    • Navigational Warnings Services

    • Radio Aids to Navigation

    • List of Lights and Buoys and Aids to Navigation

    • Nautical Charts and Publications services

  • Theme 2 – Regulatory Requirements

    • Acts and Regulations specific to marine navigation (similar to S-49 E.3.2)

    • IMO Guidelines for Operating in Polar Waters

  • Theme 3 – Arctic Environment Considerations

    • Communities and Populated Areas Information

    • Weather Station Locations and Services Available (similar to S-49 E.4.2 and U.4))

    • Airports and Hospitals

    • Resource Development Significant Locations

  • Theme 4 – Route Planning

    • Traditional Traffic Routes (similar to S-49 E.3.2)

    • Controlled Navigational Areas including Vessel Traffic Services Zones

    • Limiting Depth For Constricted Waterways

    • Tide, Current and Water Level information (similar to S-49 U.6.1)

    • Environment Protected Areas

    • Major Aids to Navigations (similar to S-49 E.1.2 and U.1.2)

    • Places of refuge or Pilot Boarding Stations (similar to S-49 E.1.5)

    • Calling-in Points (similar to S-49 E.4.1)

  • Theme 5 – Reporting and Communicating

    • Areas of Legislative Importance to Navigation

    • Marine Communication Services (similar calling-in info to S-49 E.4.1)

  • Theme 6 – Marine Services

    • Ice Breaking Support Services

    • Search and Rescue Support Services

    • Ice Services Information (similar to S-49 U.6.4)

  • Theme 7 – Nautical Charts and Publication

    • Nautical Chart Catalogue and Coverage

    • Publication Catalogue and Coverage

4.3. Report Topics

The following list provides a first overview what topics shall be part of the scenario description and evaluation report:

  • Experiences and lessons learned with respect to the data research questions stated above.

  • What role do standards play?

  • Which standards have been used? What is missing?

  • How did the integration/federation work?

  • What model for future federations can we envision?

  • What efforts are recommended to further enhance the user experiences for the various elements in the scenario?

5. Deliverables

Each deliverable defines a sub-scenario package. This package includes the definition and implementation of the sub-scenario; the role it plays as part of the overarching scenario, and the documentation of all results, experiences made, and lessons learned as stated above. The documentation is delivered as a contribution to the initiative results Engineering Report.

Each participant is free to choose the type of software used for data integration, analysis, and visualization. No software will be delivered. Instead, delivery is provided in the form of live demonstrations of the scenario during video conferences that will be recorded and used for future outreach activities.

In total, this pilot is expected to fund a total of six organizations. Each participant shall demonstrate a sub-scenario and contribute a dedicated component to the overarching scenario. This is, each participant either provides a client and loads this client with data and analytics as provided by other participants, or a service component to make data available in a standards-compliant format.

deliverables
Figure 3. Overview of the Pilot Deliverables

Bidders proposing a client implementation shall use this client to include data used in other sub-scenarios or identified by other participants. The clients serve as integration points for all elements that are part of the overarching scenario.

Bidders proposing a server component shall support loading data to the service instance to make it available in a format supported by the client instances. Alternatively, the server instances may proxy existing, non-standard compliant data services to provide a standards-based API.

In summary, each bidder shall demonstrate a complete sub-scenario and contribute either a client or server instance to the overarching scenario. Bidders are invited to include either a client or server instance or both in their proposals. Each participant demonstrates their sub-scenario with their own client. The dedicated client applications D100-102 will be used in the umbrella scenario.

D100 - Client instance: Sub-scenario package and dedicated client instance to be used in both the sub-scenario as well as the overarching scenario. The client instance will be delivered in the form of a live demonstration that illustrates all elements of the different scenarios. Ideally, the client shall make use of the server instances D103-105.

D101 - Client instance: Similar to D100.

D102 - Client instance: Similar to D100.

D103 - Server instance: Sub-scenario package and dedicated server instance to be used in both the sub-scenario as well as the overarching scenario. The server instance will be delivered by making it available to clients D100-102 during the demonstration scenario(s). The server shall provide a OGC compliant API that supports discovery and access to marine or land data in an Arctic scenario.

D104 - Server instance: Similar to D103.

D105 - Server instance: Similar to D103.

6. Guidelines and Cost-share

6.1. Submission Guidelines

  • Proposals must be submitted by 11:59pm EST in accordance with the Master Schedule, M02, Close of Close of Call for Participation.

  • Proposals from non-members or individual members will be considered provided OGC Membership (or a letter of intent) is provided with Proposal Submission

  • Each selected proposing organization will be required to enter into a Participant Agreement (PA) contract with OGC, regardless of receipt of cost-share funds

  • Proposals should be submitted in PDF format and should contain an overview of planned implementations, desired cost-share, and in-kind contributions (if any)

  • It should be clear how each planned deliverable relates to the core scope

6.2. Cost-share

  • Cost-share of funds are to be negotiated upon receipt of the proposal if the proposal is chosen

  • Funding is determined based upon the work outlined in the proposal

  • Complexity of the deliverable and what is outlined within the proposal are taken into account when determining funding

6.3. How to Submit

Email the PDF Proposal prior to the submission deadline to innovation@ogc.org. Technical Proposal Template and Cost Proposal Template are accessible here.

6.4. Participation Requirements

  • Each Participant agrees to provide a detailed description and planned implementation of the assigned deliverables and to coordinate with other initiative Participants at the Kickoff Workshop ("Kickoff").

  • The Initiative will be conducted within the framework of OGC’s Bylaws and Intellectual Property Rights Policy ("IPR Policy"), as agreed to in the Participant’s 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.

  • Remote Teleconference Meetings: Regular telecons will be conducted to accelerate understanding and action, particularly the status of any risks (or issues) that might block (or are blocking) progress toward timely delivery of work item results.

  • Each Participant agrees to provide at least one Technical Point of Contact (POC) to attend both regularly scheduled and ad hoc telecons that involve an assigned deliverable.

6.5. Correspondence and Collaboration

Each Participant agrees to utilize the following correspondence and collaboration tools:

  • Participate in telecons using the GoToMeeting tool;

  • Edit Engineering Report source files in the Asciidoc format using the OGC Engineering Report template (to be provided);

  • Upload Engineering Report source files to the designated GitHub or Gitlab repository;

  • Use the designated GitHub/Gitlab repository for communication and reporting;

  • Utilize the OGC Web Portal, with modules for calendaring, contact lists, file storage, timeline, action items, and meeting scheduling; and

  • Send and receive emails to/from Initiative email broadcast list(s).

6.6. Reporting

Each Participant agrees to report the status of deliverables weekly to the initiative architect (Technical Status Reports) and monthly in business status reports.

Technical Status Reports: Each Participant agrees to use Github/Gitlab issues to report the status on each assigned deliverable on a weekly basis. These short reports shall include the following information:

  • Deliverable ID and Name,

  • Health: G, Y, R (green, yellow, red),

  • %complete (0%-100%),

  • Work accomplished in reporting period (last week),

  • Work anticipated in reporting period+1 (next week),

  • Any known risks or issues,

  • Response to mitigate the risk or remedy the issue.

Monthly Business Status Reports: Each Participant agrees to email monthly business status reports no later than the 3rd of each second month (or the first workday after if the 3rd is not a workday). This report should include the period and cumulative hours and cost expended for each assigned deliverable.

( end of document )