2020 06 04

2020-06-04 Environmental Data Retrieval SWG Meeting 14

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 https://www4.gotomeeting.com/join/427053653

Agenda:

1. Agree Agenda and IPR Call

2. Minutes/Notes of previous meetings

3. Current Candidate EDR API Specification

   Outstanding Issues

   Outstanding Pull Requests

4. Progress on API coordination, Collections, etc.

5. Way forward

6. Any Other Business

7. Next Meeting

Minutes:

Attending:

• Chris Little
• Dave Blodgett
• Peng Yue
• Mingda Zhang
• Shane Mill
• Pavol Novotny
• Mark Burgoyne
• Steve Olson
• Lei Hu
• Boyi Shangguan

1. Agree Agenda and IPR Call
   Done

2. Minutes/Notes of previous meetings
   Agreed

3. Current Candidate EDR API Specification

4. Chris made a june-draft branch to clean up our requirements classes. https://github.com/opengeospatial/Environmental-Data-Retrieval-API/tree/June-Draft

5. Outstanding Issues
   1. #38 and #68 -- discussed and generally agreed to the strategy in #140. Action on dblodgett-usgs
   2. #67 can close
   3. #66 not quite unanimous but we are generally ok allowing WKT time or a parameter for a single time. Outcome clear in conversation. See actions.
   4. #61 Seems like this is an enhancement. We need more specific data formats and analysis of corridor axes. Initial spec should support vertical as vertical. Enhancement will support orthoganal.

6. Outstanding Pull Requests

7. Progress on API coordination, Collections, etc

8. See #38 and #68

9. Way forward

10. Any Other Business

11. Pete T. has some ESRI code that should be open-sourced if all agree.

12. Next Meeting

13. next week

Decisions:

Actions:

1. dblodgett-usgs will add a final summary comment to #38 and #68 and close. Will open new issues for follow up.
2. Mark will implement a fix for #66
3. Pavol will summarize the fix for #66 in the issue.
4. Chris will comment on the #61 issue, create an enhancement, and Mark will make sure it gets in the spec.