-
Notifications
You must be signed in to change notification settings - Fork 15
Minutes
- Hackathon objectives
- OGC API Coverages - https://github.com/opengeospatial/ogc_api_coverages
- AOB
Amy, Chris, Michael, Eugene, Paul, Peter, Stephan
- Chris informs that the Met-Office is going to be at the hackathon and will provide/bring multidimensional data and service
- Known participants are
- Met-Office
- National Weather Service
- Ordnance survey
- OpenEO
- Sinergise
- Jacobs University/rasdaman
- EOX
- There is space for a maximum of 70 participants and twice as much are on the waiting list
- Chris raises the question how success is defined for the hackathon.
-
Michael emphasized to define a mission like Chris Holmes did for WFS and STAC.
-
Chris: Indication if WFS 3 is going the right direction. Build suite of APIs that are consistent. Met-Ocean hackathon in December in Washington based on WFS. Coverages are only for GeoSpatial experts.
-
Stephan: This is a first hackathon in a series with focus on Common. Personal objective to make it way easier for client implementers.
-
Chris: UK Gov OpenAPI initiative API guidance is that they all should be based on OpenAPI 3.0 - https://github.com/alphagov/open-standards/issues/31#issuecomment-493437352
-
The groups common understanding of the main objectives is to get consensus that OpenAPI is the right way to go for the next generation of OGC standards and to factor out commonalities in OGC API Common which all groups agree to use.
-
- Michael introduces his view on OGC Next Generation APIs. He will put the diagram on GitHub.
- Peter suggests a break-out session to harmonize by looking at overlap, commonalities between building blocks, i.e., coverages, features, and common.
- Stephan: Send mail to Gobe to ask about objectives and invite to next week's meeting
- Michael: Put shown diagram on GitHub
- All: Review and contribute issues and requirements
- OGC API Coverages - https://github.com/opengeospatial/ogc_api_coverages
- AOB
Chuck, Eugene, Jürgen, Peter, Stephan S.
- We only had a brief general discussion mainly about API Common and usage of IDs
- Chuck: Check definition for IDs #19. Do we break OpenAPI when using IRIs as defined in RFC3987?
- All: Review and contribute issues and requirements
- OGC API Coverages - https://github.com/opengeospatial/ogc_api_coverages
- Weekly meeting time slot
Chuck, Eugene, Joan, Peter, Stephan S., Stephan M.
- Weekly meeting time slot moved to Wednesday 10am EDT / 4pm CEST
- Stephan introduces new wiki page capturing minutes
- We reviewed some issues and try to close them
- All: Review and contribute issues and requirements
- OGC API Coverages - https://github.com/opengeospatial/ogc_api_coverages
Amy, Chuck, Eugene, Paul, Peter, Stephan
- Chuck presents changes made to the GitHub repository
- got rid of distracting stuff, e.g. removed OAPI-Common directory
- requirements directory
- is the only normative part
- they are included in clause 7
- examples directory
- are important to see how the requirements are actually implemented
- again included in clause 7
- for the hackathon clause 7 is the most important one
- anything not specific to coverages should probably be in common
- don't waste time on it
- tie back to common via requirements class
- everything needed for functional complete implementation should go in core, everything else in extensions
- pattern for extensions
- top level directory for each along OAPI-Coverages
- naming convention will be in mail from Clemens soon, following ISO nomenclature
- focus on getting requirements written
- Stephan introduces new wiki page capturing decisions
- We review some issues and try to close them
- Chuck: Write some notes about structure and next steps up in the wiki
- All: Review and contribute issues and requirements