2020 04 30

2020-04-30 Environmental Data Retrieval SWG Meeting 10

13:00 UTC (07:00 MDT, 09:00 EDT, 14:00 BST, 15:00 CEST, 21:00 CST, 23:00 AEST)

gotomeeting in OGC Portal

Agenda:

0. Agree Agenda and IPR Call

1. Minutes/Notes of previous meetings

2. Final Report of EDR API Virtual Sprint

   Proposal to release Sprint Report

   Convert into Engineering Report OGC20-032 using ER template

3. Current Candidate EDR API Specification
   Outstanding Issues from SWG

   Outstanding Pull Requests

   Way forward

4. Any Other Business

   Mavy/June Webinar

5. Next Meeting

   Next week Thursday 7th May 2020, same time?

Minutes:

Attending:

Chris Little

Dave Blodgett

Boyi Shangguan

Igor Andruski

Lei Hu

Frederic Guillaud

Mark Burgoyne

Mingda Shang

Paul Hershberg

Pavol Novotny

Roope Tervo

Shane Mill

Steve Olson

Pete Treveylan

0. Agree Agenda and IPR Call
   Agreed.

1. Minutes/Notes of previous meetings
   NOTUC

2. Final Report of EDR API Virtual Sprint

• All issues have been settled.
• Have an OGC document number: 20-032
• Will create an ER so we have a record in the OGC portal/web page.
• Wuhan University volunteered to put it in the OGC document template.
• Will the SWG publish the ER or will it come from a DWG? Chris happy to have the SWG vote on it.
• Plan to release sprint blog is moving late this week.
• Reviewed outcomes and notified that review period will close in 24 hours.

3. Current Candidate Spec Chris generally interested in getting review from others in OGC soon! Labels for "enhancement" have been added to indicate out of scope for near term standardization.

• Issue #55: polygon timeseries at one vertical or over a vertical range. enhancement
• Issue #53: If trajectories are not parallel with a dimension, a sampling step isn't clear.
  • Need to be careful with interpolation here.
  • Discussion is ongoing -- resolution is pending.
  • Note there is a difference between way-points (points of interest) and segments (more finely spaced samples along a path).
• Issue #52: Named levels. (maybe enhancement)
  • In some places we use WKT for Z in others we don't.
  • Need to get some consistency on this point.
  • This is separate from the "named-location" mechanism.
• Issue #51: Corridor bounded by the earth's surface: enhancement
• Issue #50: 3d/4D corridors enhancement
  • Q: how is resolution handled? explained in a recent PR.
• Issue #45: Still need to debate trajectory vs vertical profile.
  • Getting to agreement that we can use the "position query" for profiles.
• Issue #44/#40: How to link out to more detailed metadata is important.
  • Have a prototype from Tom K. in issue #40. General agreement on the proposal here.
• Issue #38: Looking for maximum compatibility with OGC API-Features. We need to continue this discussion.
  • Need further discussion on the complexity that we are introducing by overloading the collection endpoint.
  • Grouping has a lot of different purposes -- the semantics of a collection of items in OGC is not settled.
• Issue #35: Still in plan. Still open questions about how to test payloads -- json schema is likely.
• Issue #28: Agreed to close.
• Issue #26: Can close as will be handled elsewhere.
• Issue #16: Will go with what Clemense suggested.
• Issue #9: Security aspects will be part of common etc. enhancement
• PR #49: Agreed.
• EDR-Sprint branch

4. Any Other Business

5. Next Meeting

Decisions:

Actions:

• WHU will work on getting formatting of the sprint report handled.
• Can publish API doc